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.
16 e.g. A > B = C > D = E = F
20 ## Public mailing list
22 Make sure you are subscribed to debian-ctte@lists.debian.org, the public
23 mailing list where all public matters are discussed.
27 We have a private alias which you'll get subscribed to:
28 debian-ctte-private@debian.org which we should be making use of when needed. By
29 default we should work publically, but for all sensitive things, keep the
30 private list in explicit CC. It's good for the parties we're privately talking
31 to for them to know that the rest of the TC is in the loop, as well for our
34 ## tech-ctte pseudo-bug
36 Beware of list-vs-bug mails; we try to have all issues separated in bug
37 reports, which get to the list; so for non-meta discussions, we should always
38 only write to the bug.
40 ## Regular IRC meetings
42 The TC holds regular IRC meetings in #debian-ctte, logged using
43 http://meetbot.debian.net, on an approximate monthly schedule.
47 The committee's git repository is at:
49 https://anonscm.debian.org/git/collab-maint/debian-ctte.git
53 The git repository contains a meetings.ics calendar file to list the future
54 meetings, both IRC and IRL.
58 ## Transparency to each other
60 We want to provide more transparency to each other in our processes, don't feel
61 that a "I agree to your long mail" mail would be superfluous, it's definitely
67 For the rest, apply your very sane judgment, and please state your
68 disagreements when you have them!