1
Historical version of the Constitution for the Debian Project (v1.2)
3
Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1
4
ratified on June 21st, 2003, which itself supersedes Version 1.0
5
ratified on December 2nd, 1998. Superseded by version 1.3, ratified on
6
September 24th, 2006. That was superceded by the current version, 1.4
7
ratified on October 7th, 2007.
11
The Debian Project is an association of individuals who have made
12
common cause to create a free operating system.
14
This document describes the organisational structure for formal
15
decision-making in the Project. It does not describe the goals of the
16
Project or how it achieves them, or contain any policies except those
17
directly related to the decision-making process.
19
2. Decision-making bodies and individuals
21
Each decision in the Project is made by one or more of the following:
22
1. The Developers, by way of General Resolution or an election;
23
2. The Project Leader;
24
3. The Technical Committee and/or its Chairman;
25
4. The individual Developer working on a particular task;
26
5. Delegates appointed by the Project Leader for specific tasks;
27
6. The Project Secretary.
29
Most of the remainder of this document will outline the powers of these
30
bodies, their composition and appointment, and the procedure for their
31
decision-making. The powers of a person or body may be subject to
32
review and/or limitation by others; in this case the reviewing body or
33
person's entry will state this. In the list above, a person or body is
34
usually listed before any people or bodies whose decisions they can
35
overrule or who they (help) appoint - but not everyone listed earlier
36
can overrule everyone listed later.
40
1. Nothing in this constitution imposes an obligation on anyone to do
41
work for the Project. A person who does not want to do a task which
42
has been delegated or assigned to them does not need to do it.
43
However, they must not actively work against these rules and
44
decisions properly made under them.
45
2. A person may hold several posts, except that the Project Leader,
46
Project Secretary and the Chairman of the Technical Committee must
47
be distinct, and that the Leader cannot appoint themselves as their
49
3. A person may leave the Project or resign from a particular post
50
they hold, at any time, by stating so publicly.
52
3. Individual Developers
56
An individual Developer may
57
1. make any technical or nontechnical decision with regard to their
59
2. propose or sponsor draft General Resolutions;
60
3. propose themselves as a Project Leader candidate in elections;
61
4. vote on General Resolutions and in Leadership elections.
63
3.2. Composition and appointment
65
1. Developers are volunteers who agree to further the aims of the
66
Project insofar as they participate in it, and who maintain
67
package(s) for the Project or do other work which the Project
68
Leader's Delegate(s) consider worthwhile.
69
2. The Project Leader's Delegate(s) may choose not to admit new
70
Developers, or expel existing Developers. If the Developers feel
71
that the Delegates are abusing their authority they can of course
72
override the decision by way of General Resolution - see �4.1(3),
77
Developers may make these decisions as they see fit.
79
4. The Developers by way of General Resolution or election
83
Together, the Developers may:
84
1. Appoint or recall the Project Leader.
85
2. Amend this constitution, provided they agree with a 3:1 majority.
86
3. Override any decision by the Project Leader or a Delegate.
87
4. Override any decision by the Technical Committee, provided they
88
agree with a 2:1 majority.
89
5. Issue, supersede and withdraw nontechnical policy documents and
91
These include documents describing the goals of the project, its
92
relationship with other free software entities, and nontechnical
93
policies such as the free software licence terms that Debian
95
They may also include position statements about issues of the day.
96
1. A Foundation Document is a document or statement regarded as
97
critical to the Project's mission and purposes.
98
2. The Foundation Documents are the works entitled "Debian Social
99
Contract" and "Debian Free Software Guidelines".
100
3. A Foundation Document requires a 3:1 majority for its
101
supersession. New Foundation Documents are issued and existing
102
ones withdrawn by amending the list of Foundation Documents in
104
6. Together with the Project Leader and SPI, make decisions about
105
property held in trust for purposes related to Debian. (See �9.1.)
109
1. The Developers follow the Standard Resolution Procedure, below. A
110
resolution or amendment is introduced if proposed by any Developer
111
and sponsored by at least K other Developers, or if proposed by the
112
Project Leader or the Technical Committee.
113
2. Delaying a decision by the Project Leader or their Delegate:
114
1. If the Project Leader or their Delegate, or the Technical
115
Committee, has made a decision, then Developers can override
116
them by passing a resolution to do so; see �4.1(3).
117
2. If such a resolution is sponsored by at least 2K Developers,
118
or if it is proposed by the Technical Committee, the
119
resolution puts the decision immediately on hold (provided
120
that resolution itself says so).
121
3. If the original decision was to change a discussion period or
122
a voting period, or the resolution is to override the
123
Technical Committee, then only K Developers need to sponsor
124
the resolution to be able to put the decision immediately on
126
4. If the decision is put on hold, an immediate vote is held to
127
determine whether the decision will stand until the full vote
128
on the decision is made or whether the implementation of the
129
original decision will be delayed until then. There is no
130
quorum for this immediate procedural vote.
131
5. If the Project Leader (or the Delegate) withdraws the original
132
decision, the vote becomes moot, and is no longer conducted.
133
3. Votes are taken by the Project Secretary. Votes, tallies, and
134
results are not revealed during the voting period; after the vote
135
the Project Secretary lists all the votes cast. The voting period
136
is 2 weeks, but may be varied by up to 1 week by the Project
138
4. The minimum discussion period is 2 weeks, but may be varied by up
139
to 1 week by the Project Leader. The Project Leader has a casting
140
vote. There is a quorum of 3Q.
141
5. Proposals, sponsors, amendments, calls for votes and other formal
142
actions are made by announcement on a publicly-readable electronic
143
mailing list designated by the Project Leader's Delegate(s); any
144
Developer may post there.
145
6. Votes are cast by email in a manner suitable to the Secretary. The
146
Secretary determines for each poll whether voters can change their
148
7. Q is half of the square root of the number of current Developers. K
149
is Q or 5, whichever is the smaller. Q and K need not be integers
156
The Project Leader may:
157
1. Appoint Delegates or delegate decisions to the Technical Committee.
158
The Leader may define an area of ongoing responsibility or a
159
specific decision and hand it over to another Developer or to the
161
Once a particular decision has been delegated and made the Project
162
Leader may not withdraw that delegation; however, they may withdraw
163
an ongoing delegation of particular area of responsibility.
164
2. Lend authority to other Developers.
165
The Project Leader may make statements of support for points of
166
view or for other members of the project, when asked or otherwise;
167
these statements have force if and only if the Leader would be
168
empowered to make the decision in question.
169
3. Make any decision which requires urgent action.
170
This does not apply to decisions which have only become gradually
171
urgent through lack of relevant action, unless there is a fixed
173
4. Make any decision for whom noone else has responsibility.
174
5. Propose draft General Resolutions and amendments.
175
6. Together with the Technical Committee, appoint new members to the
176
Committee. (See �6.2.)
177
7. Use a casting vote when Developers vote.
178
The Project Leader also has a normal vote in such ballots.
179
8. Vary the discussion period for Developers' votes (as above).
180
9. Lead discussions amongst Developers.
181
The Project Leader should attempt to participate in discussions
182
amongst the Developers in a helpful way which seeks to bring the
183
discussion to bear on the key issues at hand. The Project Leader
184
should not use the Leadership position to promote their own
186
10. Together with SPI, make decisions affecting property held in trust
187
for purposes related to Debian. (See �9.1.)
191
1. The Project Leader is elected by the Developers.
192
2. The election begins nine weeks before the leadership post becomes
193
vacant, or (if it is too late already) immediately.
194
3. For the following three weeks any Developer may nominate themselves
195
as a candidate Project Leader.
196
4. For three weeks after that no more candidates may be nominated;
197
candidates should use this time for campaigning (to make their
198
identities and positions known). If there are no candidates at the
199
end of the nomination period then the nomination period is extended
200
for three further weeks, repeatedly if necessary.
201
5. The next three weeks are the polling period during which Developers
202
may cast their votes. Votes in leadership elections are kept
203
secret, even after the election is finished.
204
6. The options on the ballot will be those candidates who have
205
nominated themselves and have not yet withdrawn, plus None Of The
206
Above. If None Of The Above wins the election then the election
207
procedure is repeated, many times if necessary.
208
7. The decision will be made using the method specified in section
209
�A.6 of the Standard Resolution Procedure. The quorum is the same
210
as for a General Resolution (�4.2) and the default option is "None
212
8. The Project Leader serves for one year from their election.
216
The Project Leader should attempt to make decisions which are
217
consistent with the consensus of the opinions of the Developers.
219
Where practical the Project Leader should informally solicit the views
222
The Project Leader should avoid overemphasizing their own point of view
223
when making decisions in their capacity as Leader.
225
6. Technical committee
229
The Technical Committee may:
230
1. Decide on any matter of technical policy.
231
This includes the contents of the technical policy manuals,
232
developers' reference materials, example packages and the behaviour
233
of non-experimental package building tools. (In each case the usual
234
maintainer of the relevant software or documentation makes
235
decisions initially, however; see 6.3(5).)
236
2. Decide any technical matter where Developers' jurisdictions
238
In cases where Developers need to implement compatible technical
239
policies or stances (for example, if they disagree about the
240
priorities of conflicting packages, or about ownership of a command
241
name, or about which package is responsible for a bug that both
242
maintainers agree is a bug, or about who should be the maintainer
243
for a package) the technical committee may decide the matter.
244
3. Make a decision when asked to do so.
245
Any person or body may delegate a decision of their own to the
246
Technical Committee, or seek advice from it.
247
4. Overrule a Developer (requires a 3:1 majority).
248
The Technical Committee may ask a Developer to take a particular
249
technical course of action even if the Developer does not wish to;
250
this requires a 3:1 majority. For example, the Committee may
251
determine that a complaint made by the submitter of a bug is
252
justified and that the submitter's proposed solution should be
255
The Technical Committee may make formal announcements about its
256
views on any matter. Individual members may of course make informal
257
statements about their views and about the likely views of the
259
6. Together with the Project Leader, appoint new members to itself or
260
remove existing members. (See �6.2.)
261
7. Appoint the Chairman of the Technical Committee.
262
The Chairman is elected by the Committee from its members. All
263
members of the committee are automatically nominated; the committee
264
votes starting one week before the post will become vacant (or
265
immediately, if it is already too late). The members may vote by
266
public acclamation for any fellow committee member, including
267
themselves; there is no default option. The vote finishes when all
268
the members have voted, or when the voting period has ended. The
269
result is determined using the method specified in section A.6 of
270
the Standard Resolution Procedure.
271
8. The Chairman can stand in for the Leader, together with the
273
As detailed in �7.1(2), the Chairman of the Technical Committee and
274
the Project Secretary may together stand in for the Leader if there
279
1. The Technical Committee consists of up to 8 Developers, and should
280
usually have at least 4 members.
281
2. When there are fewer than 8 members the Technical Committee may
282
recommend new member(s) to the Project Leader, who may choose
283
(individually) to appoint them or not.
284
3. When there are 5 members or fewer the Technical Committee may
285
appoint new member(s) until the number of members reaches 6.
286
4. When there have been 5 members or fewer for at least one week the
287
Project Leader may appoint new member(s) until the number of
288
members reaches 6, at intervals of at least one week per
290
5. If the Technical Committee and the Project Leader agree they may
291
remove or replace an existing member of the Technical Committee.
295
1. The Technical Committee uses the Standard Resolution Procedure.
296
A draft resolution or amendment may be proposed by any member of
297
the Technical Committee. There is no minimum discussion period; the
298
voting period lasts for up to one week, or until the outcome is no
299
longer in doubt. Members may change their votes. There is a quorum
301
2. Details regarding voting
302
The Chairman has a casting vote. When the Technical Committee votes
303
whether to override a Developer who also happens to be a member of
304
the Committee, that member may not vote (unless they are the
305
Chairman, in which case they may use only their casting vote).
306
3. Public discussion and decision-making.
307
Discussion, draft resolutions and amendments, and votes by members
308
of the committee, are made public on the Technical Committee public
309
discussion list. There is no separate secretary for the Committee.
310
4. Confidentiality of appointments.
311
The Technical Committee may hold confidential discussions via
312
private email or a private mailing list or other means to discuss
313
appointments to the Committee. However, votes on appointments must
315
5. No detailed design work.
316
The Technical Committee does not engage in design of new proposals
317
and policies. Such design work should be carried out by individuals
318
privately or together and discussed in ordinary technical policy
320
The Technical Committee restricts itself to choosing from or
321
adopting compromises between solutions and decisions which have
322
been proposed and reasonably thoroughly discussed elsewhere.
323
Individual members of the technical committee may of course
324
participate on their own behalf in any aspect of design and policy
326
6. Technical Committee makes decisions only as last resort.
327
The Technical Committee does not make a technical decision until
328
efforts to resolve it via consensus have been tried and failed,
329
unless it has been asked to make a decision by the person or body
330
who would normally be responsible for it.
332
7. The Project Secretary
337
1. Takes votes amongst the Developers, and determines the number and
338
identity of Developers, whenever this is required by the
340
2. Can stand in for the Leader, together with the Chairman of the
342
If there is no Project Leader then the Chairman of the Technical
343
Committee and the Project Secretary may by joint agreement make
344
decisions if they consider it imperative to do so.
345
3. Adjudicates any disputes about interpretation of the constitution.
346
4. May delegate part or all of their authority to someone else, or
347
withdraw such a delegation at any time.
351
The Project Secretary is appointed by the Project Leader and the
352
current Project Secretary.
354
If the Project Leader and the current Project Secretary cannot agree on
355
a new appointment they must ask the board of SPI (see �9.1.) to appoint
358
If there is no Project Secretary or the current Secretary is
359
unavailable and has not delegated authority for a decision then the
360
decision may be made or delegated by the Chairman of the Technical
361
Committee, as Acting Secretary.
363
The Project Secretary's term of office is 1 year, at which point they
364
or another Secretary must be (re)appointed.
368
The Project Secretary should make decisions which are fair and
369
reasonable, and preferably consistent with the consensus of the
372
When acting together to stand in for an absent Project Leader the
373
Chairman of the Technical Committee and the Project Secretary should
374
make decisions only when absolutely necessary and only when consistent
375
with the consensus of the Developers.
377
8. The Project Leader's Delegates
381
The Project Leader's Delegates:
382
1. have powers delegated to them by the Project Leader;
383
2. may make certain decisions which the Leader may not make directly,
384
including approving or expelling Developers or designating people
385
as Developers who do not maintain packages. This is to avoid
386
concentration of power, particularly over membership as a
387
Developer, in the hands of the Project Leader.
391
The Delegates are appointed by the Project Leader and may be replaced
392
by the Leader at the Leader's discretion. The Project Leader may not
393
make the position as a Delegate conditional on particular decisions by
394
the Delegate, nor may they override a decision made by a Delegate once
399
Delegates may make decisions as they see fit, but should attempt to
400
implement good technical decisions and/or follow consensus opinion.
402
9. Software in the Public Interest
404
SPI and Debian are separate organisations who share some goals. Debian
405
is grateful for the legal support framework offered by SPI. Debian's
406
Developers are currently members of SPI by virtue of their status as
411
1. SPI has no authority regarding Debian's technical or nontechnical
412
decisions, except that no decision by Debian with respect to any
413
property held by SPI shall require SPI to act outside its legal
414
authority, and that Debian's constitution may occasionally use SPI
415
as a decision body of last resort.
416
2. Debian claims no authority over SPI other than that over the use of
417
certain of SPI's property, as described below, though Debian
418
Developers may be granted authority within SPI by SPI's rules.
419
3. Debian Developers are not agents or employees of SPI, or of each
420
other or of persons in authority in the Debian Project. A person
421
acting as a Developer does so as an individual, on their own
424
9.2. Management of property for purposes related to Debian
426
Since Debian has no authority to hold money or property, any donations
427
for the Debian Project must be made to SPI, which manages such affairs.
429
SPI have made the following undertakings:
430
1. SPI will hold money, trademarks and other tangible and intangible
431
property and manage other affairs for purposes related to Debian.
432
2. Such property will be accounted for separately and held in trust
433
for those purposes, decided on by Debian and SPI according to this
435
3. SPI will not dispose of or use property held in trust for Debian
436
without approval from Debian, which may be granted by the Project
437
Leader or by General Resolution of the Developers.
438
4. SPI will consider using or disposing of property held in trust for
439
Debian when asked to do so by the Project Leader.
440
5. SPI will use or dispose of property held in trust for Debian when
441
asked to do so by a General Resolution of the Developers, provided
442
that this is compatible with SPI's legal authority.
443
6. SPI will notify the Developers by electronic mail to a Debian
444
Project mailing list when it uses or disposes of property held in
447
A. Standard Resolution Procedure
449
These rules apply to communal decision-making by committees and
450
plebiscites, where stated above.
454
The formal procedure begins when a draft resolution is proposed and
455
sponsored, as required.
457
A.1. Discussion and Amendment
459
1. Following the proposal, the resolution may be discussed. Amendments
460
may be made formal by being proposed and sponsored according to the
461
requirements for a new resolution, or directly by the proposer of
462
the original resolution.
463
2. A formal amendment may be accepted by the resolution's proposer, in
464
which case the formal resolution draft is immediately changed to
466
3. If a formal amendment is not accepted, or one of the sponsors of
467
the resolution does not agree with the acceptance by the proposer
468
of a formal amendment, the amendment remains as an amendment and
470
4. If an amendment accepted by the original proposer is not to the
471
liking of others, they may propose another amendment to reverse the
472
earlier change (again, they must meet the requirements for proposer
474
5. The proposer of a resolution may suggest changes to the wordings of
475
amendments; these take effect if the proposer of the amendment
476
agrees and none of the sponsors object. In this case the changed
477
amendments will be voted on instead of the originals.
478
6. The proposer of a resolution may make changes to correct minor
479
errors (for example, typographical errors or inconsistencies) or
480
changes which do not alter the meaning, providing noone objects
481
within 24 hours. In this case the minimum discussion period is not
484
A.2. Calling for a vote
486
1. The proposer or a sponsor of a motion or an amendment may call for
487
a vote, providing that the minimum discussion period (if any) has
489
2. The proposer or any sponsor of a resolution may call for a vote on
490
that resolution and all related amendments.
491
3. The person who calls for a vote states what they believe the
492
wordings of the resolution and any relevant amendments are, and
493
consequently what form the ballot should take. However, the final
494
decision on the form of ballot(s) is the Secretary's - see 7.1(1),
496
4. The minimum discussion period is counted from the time the last
497
formal amendment was accepted, or since the whole resolution was
498
proposed if no amendments have been proposed and accepted.
500
A.3. Voting procedure
502
1. Each resolution and its related amendments is voted on in a single
503
ballot that includes an option for the original resolution, each
504
amendment, and the default option (where applicable).
505
2. The default option must not have any supermajority requirements.
506
Options which do not have an explicit supermajority requirement
507
have a 1:1 majority requirement.
508
3. The votes are counted according to the rules in A.6. The default
509
option is "Further Discussion", unless specified otherwise.
510
4. In cases of doubt the Project Secretary shall decide on matters of
513
A.4. Withdrawing resolutions or unaccepted amendments
515
The proposer of a resolution or unaccepted amendment may withdraw it.
516
In this case new proposers may come forward keep it alive, in which
517
case the first person to do so becomes the new proposer and any others
518
become sponsors if they aren't sponsors already.
520
A sponsor of a resolution or amendment (unless it has been accepted)
523
If the withdrawal of the proposer and/or sponsors means that a
524
resolution has no proposer or not enough sponsors it will not be voted
525
on unless this is rectified before the resolution expires.
529
If a proposed resolution has not been discussed, amended, voted on or
530
otherwise dealt with for 4 weeks the secretary may issue a statement
531
that the issue is being withdrawn. If none of the sponsors of any of
532
the proposals object within a week, the issue is withdrawn.
534
The secretary may also include suggestions on how to proceed, if
539
1. Each voter's ballot ranks the options being voted on. Not all
540
options need be ranked. Ranked options are considered preferred to
541
all unranked options. Voters may rank options equally. Unranked
542
options are considered to be ranked equally with one another.
543
Details of how ballots may be filled out will be included in the
545
2. If the ballot has a quorum requirement R any options other than the
546
default option which do not receive at least R votes ranking that
547
option above the default option are dropped from consideration.
548
3. Any (non-default) option which does not defeat the default option
549
by its required majority ratio is dropped from consideration.
550
1. Given two options A and B, V(A,B) is the number of voters who
551
prefer option A over option B.
552
2. An option A defeats the default option D by a majority ratio
553
N, if V(A,D) is strictly greater than N * V(D,A).
554
3. If a supermajority of S:1 is required for A, its majority
555
ratio is S; otherwise, its majority ratio is 1.
556
4. From the list of undropped options, we generate a list of pairwise
558
1. An option A defeats an option B, if V(A,B) is strictly greater
560
5. From the list of [undropped] pairwise defeats, we generate a set of
562
1. An option A transitively defeats an option C if A defeats C or
563
if there is some other option B where A defeats B AND B
564
transitively defeats C.
565
6. We construct the Schwartz set from the set of transitive defeats.
566
1. An option A is in the Schwartz set if for all options B,
567
either A transitively defeats B, or B does not transitively
569
7. If there are defeats between options in the Schwartz set, we drop
570
the weakest such defeats from the list of pairwise defeats, and
572
1. A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less
573
than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is
574
equal to V(B,Y) and V(X,A) is greater than V(Y,B).
575
2. A weakest defeat is a defeat that has no other defeat weaker
576
than it. There may be more than one such defeat.
577
8. If there are no defeats within the Schwartz set, then the winner is
578
chosen from the options in the Schwartz set. If there is only one
579
such option, it is the winner. If there are multiple options, the
580
elector with the casting vote chooses which of those options wins.
582
Note: Options which the voters rank above the default option are
583
options they find acceptable. Options ranked below the default options
584
are options they find unacceptable.
586
When the Standard Resolution Procedure is to be used, the text which
587
refers to it must specify what is sufficient to have a draft resolution
588
proposed and/or sponsored, what the minimum discussion period is, and
589
what the voting period is. It must also specify any supermajority
590
and/or the quorum (and default option) to be used.
592
B. Use of language and typography
594
The present indicative ("is", for example) means that the statement is
595
a rule in this constitution. "ay" or "can" indicates that the person or
596
body has discretion. "Should" means that it would be considered a good
597
thing if the sentence were obeyed, but it is not binding. Text marked
598
as a citation, such as this, is rationale and does not form part of the
599
constitution. It may be used only to aid interpretation in cases of
added
removed
includes/lenny/common/doc/constitution.txt
