General Resolution: Lenny and resolving DFSG violations
- Time Line
- Proposal A Proposer
- Proposal A Seconds
- Proposal A
- Proposal B Proposer
- Proposal B Seconds
- Proposal B
- Proposal C Proposer
- Proposal C Seconds
- Proposal C
- Proposal D Proposer
- Proposal D Seconds
- Proposal D
- Proposal E Proposer
- Proposal E Seconds
- Proposal E
- Proposal F Proposer
- Proposal F Seconds
- Proposal F
- Minimum Discussion
- Quorum
- Data and Statistics
- Majority Requirement
- Outcome
Time Line
Proposal and amendment | Friday, 24 Oct 2008 | Friday, 14 Nov 2008 |
---|---|---|
Discussion Period: | Friday, 14 Nov 2008 | Wednesday, 10 Dec 2008 |
Voting Period | 00:00:01 UTC on Sunday, 14 Dec 2008 | 23:59:59 UTC on Saturday, 27 Dec 2008 |
Proposal A Proposer
Robert Millan [[email protected]]
Proposal A Seconds
- Bas Wijnen [[email protected]]
- Manoj Srivastava [[email protected]]
- Holger Levsen [[email protected]]
- Peter Samuelson [[email protected]]
- Hubert Chan [[email protected]]
- Rémi Vanicat [[email protected]]
Proposal A
Choice 1.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Reaffirm the Social Contract
-
We affirm that our Priorities are our users and the free software community (Social Contract #4);
-
We acknowledge that we promised to deliver a 100% free operating system (Social Contract #1);
-
Given that we have known for two previous releases that we have non-free bits in various parts of Debian, and a lot of progress has been made, and we are almost to the point where we can provide a free version of the Debian operating system, we will delay the release of Lenny until such point that the work to free the operating system is complete (to the best of our knowledge as of 1 November 2008).
Proposal B Proposer
Robert Millan [[email protected]]
Proposal B Seconds
- Manoj Srivastava [[email protected]]
- Holger Levsen [[email protected]]
- Peter Samuelson [[email protected]]
- Hubert Chan [[email protected]]
- Rémi Vanicat [[email protected]]
- Frans Pop [[email protected]]
Proposal B
Choice 2.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Allow Lenny to release with proprietary firmware
-
We affirm that our Priorities are our users and the free software community (Social Contract #4);
-
We acknowledge that there is a lot of progress in the kernel firmware issue; most of the issues that were outstanding at the time of the last stable release have been sorted out. However, new issues in the kernel sources have cropped up fairly recently, and these new issues have not yet been addressed;
-
We assure the community that there will be no regressions in the progress made for freedom in the kernel distributed by Debian relative to the Etch release in Lenny (to the best of our knowledge as of 1 November 2008);
-
We give priority to the timely release of Lenny over sorting every bit out; for this reason, we will treat removal of sourceless firmware as a best-effort process, and deliver firmware as part of Debian Lenny as long as we are legally allowed to do so.
Proposal C Proposer
Robert Millan [[email protected]]
Proposal C Seconds
- Holger Levsen [[email protected]]
- Peter Samuelson [[email protected]]
- Hubert Chan [[email protected]]
- Rémi Vanicat [[email protected]]
- Frans Pop [[email protected]]
Proposal C
Choice 3.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Allow Lenny to release with DFSG violations
-
We affirm that our Priorities are our users and the free software community (Social Contract #4);
-
We acknowledge that there is a lot of progress in the kernel firmware issue; however, they are not yet finally sorted out;
-
We assure the community that there will be no regressions in the progress made for freedom in the kernel distributed by Debian relative to the Etch release in Lenny (to the best of our knowledge as of 1 November 2008);
-
We give priority to the timely release of Lenny over sorting every bit out; for this reason, we will treat removal of sourceless firmware as a best-effort process.
Proposal D Proposer
Andreas Barth [[email protected]]
Proposal D Seconds
- Holger Levsen [[email protected]]
- Rémi Vanicat [[email protected]]
- Alexander Reichle-Schmehl [[email protected]]
- Reinhard Tartler [[email protected]]
- Bernd Zeimetz [[email protected]]
- Neil McGovern [[email protected]]
Proposal D
Choice 4.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Empower the release team to decide about allowing DFSG violations
-
Debian's priorities are our users and free software. We don't trade them against each other. However, while getting a release out of the door, decisions need to be made about how to get a rock-stable release of the high quality Debian is known for, release more or less on time, and to minimize the usage of problematic software. We acknowledge that there is more than just one minefield our core developers and the release team are working on.
-
We as Developers at large continue to trust our release team to follow all these goals, and therefore encourage them to continue making case-by-case decisions as they consider fit, and if necessary we authorize these decisions.
Proposal E Proposer
Manoj Srivastava [[email protected]]
Proposal E Seconds
- Robert Millan [[email protected]]
- Bernd Zeimetz [[email protected]]
- Neil McGovern [[email protected]]
- John H. Robinson, IV [[email protected]]
- Lars Wirzenius [[email protected]]
- Damyan Ivanov [[email protected]]
- Colin Tuckley [[email protected]]
- Pierre Habouzit [[email protected]]
- Gunnar Wolf [[email protected]]
Proposal E
Choice 5.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Assume blobs comply with GPL unless proven otherwise
-
We affirm that our Priorities are our users and the free software community (Social Contract #4);
-
We acknowledge that there is a lot of progress in the kernel firmware issue; most of the issues that were outstanding at the time of the last stable release have been sorted out. However, new issues in the kernel sources have cropped up fairly recently, and these new issues have not yet been addressed;
-
We assure the community that there will be no regressions in the progress made for freedom in the kernel distributed by Debian relative to the Etch release in Lenny (to the best of our knowledge as of 1 November 2008);
-
We give priority to the timely release of Lenny over sorting every bit out; for this reason, we will treat removal of sourceless firmware as a best-effort process, and deliver firmware as part of Debian Lenny as long as we are legally allowed to do so, and the firmware is distributed upstream under a license that complies with the DFSG.
Proposal F Proposer
Peter Palfrader [[email protected]]
Proposal F Seconds
- Holger Levsen [[email protected]]
- Alexander Reichle-Schmehl [[email protected]]
- Bernd Zeimetz [[email protected]]
- Frans Pop [[email protected]]
- Colin Tuckley [[email protected]]
- Russ Allbery [[email protected]]
- Martin Michlmayr [[email protected]]
- Steve McIntyre [[email protected]]
- Mark Hymers [[email protected]]
- Moritz Muehlenhoff [[email protected]]
- Ben Pfaff [[email protected]]
- Cyril Brulebois [[email protected]]
- Stephen Gran [[email protected]]
- Andreas Barth [[email protected]]
- Loïc Minier [[email protected]]
- Patrick Schoenfeld [[email protected]]
- Philipp Kern [[email protected]]
Proposal F
Choice 6.
The actual text of the resolution is as follows. Please note
that this does not include preludes, prologues, any preambles to
the resolution, post-ambles to the resolution, abstracts,
fore-words, after-words, rationales, supporting documents,
opinion polls, arguments for and against, and any of the other
important material you will find on the mailing list
archives. Please read the debian-vote mailing list archives for
details.
Exclude source requirements for firmware (defined)
Firmware is data such as microcode or lookup tables that is loaded into hardware components in order to make the component function properly. It is not code that is run on the host CPU.
Unfortunately such firmware often is distributed as so-called blobs, with no source or further documentation that lets us learn how it works or interacts with the hardware in question. By excluding such firmware from Debian we exclude users that require such devices from installing our operating system, or make it unnecessarily hard for them.
-
firmware in Debian does not have to come with source. While we do prefer firmware that comes with source and documentation we will not require it,
-
we however do require all other freedoms that the DFSG mandate from components of our operating system, and
-
such firmware can and should be part of our official installation media.
Minimum Discussion
As per the request from the Debian Project Leader, the voting and minimum discussion periods are one week long.
Quorum
With the current list of voting developers, we have:
Current Developer Count = 1018 Q ( sqrt(#devel) / 2 ) = 15.9530561335438 K min(5, Q ) = 5 Quorum (3 x Q ) = 47.8591684006314
Quorum
- Option1 Reached quorum: 117 > 47.8591684006314
- Option2 Reached quorum: 224 > 47.8591684006314
- Option3 Reached quorum: 204 > 47.8591684006314
- Option4 Reached quorum: 194 > 47.8591684006314
- Option5 Reached quorum: 191 > 47.8591684006314
- Option6 Reached quorum: 180 > 47.8591684006314
Data and Statistics
For this GR, as always statistics shall be gathered about ballots received and acknowledgements sent periodically during the voting period. Additionally, the list of voters would be made publicly available. Also, the tally sheet may also be viewed after to voting is done (Note that while the vote is in progress it is a dummy tally sheet). Until these are published, live stats are available.
Majority Requirement
Amendments A (choice 2), B (choice 3), C (choice 4), and E (choice 6) supersede foundation documents, temporarily or permanently, and thus need a 3:1 majority. The Proposal (choice 1) and Amendment D (choice 5) require a simple majority to pass.
Majority
- Dropping Option1 because of Majority. 0.518 (117/226) <= 1
- Dropping Option2 because of Majority. 1.736 (224/129) <= 3
- Dropping Option3 because of Majority. 1.407 (204/145) <= 3
- Dropping Option4 because of Majority. 1.268 (194/153) <= 3
- Option5 passes Majority. 1.194 (191/160) >= 1
- Dropping Option6 because of Majority. 1.065 (180/169) <= 3
Outcome
In the graph above, any pink colored nodes imply that the option did not pass majority, the Blue is the winner. The Octagon is used for the options that did not beat the default.
- Option 1 "Reaffirm the Social Contract"
- Option 2 "Allow Lenny to release with proprietary firmware [3:1]"
- Option 3 "Allow Lenny to release with DFSG violations [3:1]"
- Option 4 "Empower the release team to decide about allowing DFSG violations [3:1]"
- Option 5 "Assume blobs comply with GPL unless proven otherwise"
- Option 6 "Exclude source requirements for firmware (defined) [3:1]"
- Option 7 "Further Discussion"
In the following table, tally[row x][col y] represents the votes that option x received over option y. A more detailed explanation of the beat matrix may help in understanding the table. For understanding the Condorcet method, the Wikipedia entry is fairly informative.
Option | |||||||
---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | |
Option 1 | 46 | 60 | 72 | 73 | 89 | 117 | |
Option 2 | 281 | 160 | 160 | 171 | 177 | 224 | |
Option 3 | 255 | 61 | 125 | 137 | 151 | 204 | |
Option 4 | 253 | 121 | 146 | 160 | 166 | 194 | |
Option 5 | 234 | 105 | 128 | 135 | 136 | 191 | |
Option 6 | 220 | 118 | 134 | 125 | 134 | 180 | |
Option 7 | 226 | 129 | 145 | 153 | 160 | 169 |
Looking at row 2, column 1, Allow Lenny to release with proprietary firmware [3:1]
received 281 votes over Reaffirm the Social Contract
Looking at row 1, column 2, Reaffirm the Social Contract
received 46 votes over Allow Lenny to release with proprietary firmware [3:1].
Pair-wise defeats
- Option 5 defeats Option 7 by ( 191 - 160) = 31 votes.
The Schwartz Set contains
- Option 5 "Assume blobs comply with GPL unless proven otherwise"
The winners
- Option 5 "Assume blobs comply with GPL unless proven otherwise"
Debian uses the Condorcet method for voting.
Simplistically, plain Condorcets method
can be stated like so :
Consider all possible two-way races between candidates.
The Condorcet winner, if there is one, is the one
candidate who can beat each other candidate in a two-way
race with that candidate.
The problem is that in complex elections, there may well
be a circular relationship in which A beats B, B beats C,
and C beats A. Most of the variations on Condorcet use
various means of resolving the tie. See
Cloneproof Schwartz Sequential Dropping
for details. Debian's variation is spelled out in the
constitution,
specifically, A.6.
Manoj Srivastava