1 Intro Sheet for new Technical Committee Members
2 ===============================================
8 §6 from the constitution is our bible for how we're supposed to work publicly
10 ## Standard Resolution Procedure (§6.3.1)
12 We use the standard resolution procedure (§6.3.1) using Don's pocket-devotee
13 script, which allows us to get condorcet voting in shell. Please use the `><=`
14 format for expressing your votes.
23 ## Public mailing list
25 Make sure you are subscribed to debian-ctte@lists.debian.org, the public
26 mailing list where all public matters are discussed.
30 We have a private alias which you'll get subscribed to:
31 debian-ctte-private@debian.org which we should be making use of when needed. By
32 default we should work publically, but for all sensitive things, keep the
33 private list in explicit CC. It's good for the parties we're privately talking
34 to for them to know that the rest of the TC is in the loop, as well for our
37 ## tech-ctte pseudo-bug
39 Beware of list-vs-bug mails; we try to have all issues separated in bug
40 reports, which get to the list; so for non-meta discussions, we should always
41 only write to the bug.
43 ## Regular IRC meetings
45 The TC holds regular IRC meetings in #debian-ctte, logged using
46 http://meetbot.debian.net, on an approximate monthly schedule.
50 The committee's git repository is at:
52 https://anonscm.debian.org/git/collab-maint/debian-ctte.git
56 The git repository contains a meetings.ics calendar file to list the future
57 meetings, both IRC and IRL.
61 ## Transparency to each other
63 We want to provide more transparency to each other in our processes, don't feel
64 that a "I agree to your long mail" mail would be superfluous, it's definitely
70 For the rest, apply your very sane judgment, and please state your
71 disagreements when you have them!