General Resolution: Declassification of debian-private list archives
- Time Line
- Amendment Proposer
- Amendment Seconds
- Amendment Text
- Data and Statistics
- Majority Requirement
Note:This resolution has been repealed by this vote.
|Proposal and amendment||Tuesday, 15th November, 2005||Friday, 18th November, 2005|
|Discussion Period:||Friday, 18th November, 23:59:59 UTC, 2005||Saturday, 17th December, 23:59:59 UTC, 2005|
|Voting Period||Sunday, 18th December, 00:00:01 UTC, 2005||Saturday, 31st December, 23:59:59 UTC, 2005|
Anthony Towns [firstname.lastname@example.org]
- Anibal Monsalve Salazar [email@example.com]
- Kalle Kivimaa [firstname.lastname@example.org]
- Wouter Verhelst [email@example.com]
- Daniel Ruoso [firstname.lastname@example.org]
- Kurt Roeckx [email@example.com]
- Don Armstrong [firstname.lastname@example.org]
The actual text of the GR is:
In accordance with principles of openness and transparency, Debian will seek to declassify and publish posts of historical or ongoing significance made to the Debian Private Mailing List.
This process will be undertaken under the following constraints:
The Debian Project Leader will delegate one or more
volunteers to form the
debian-private declassification team.
The team will automatically declassify and publish
posts made to that list that are three or more years
old, with the following exceptions:
- the author and other individuals quoted in messages being reviewed will be contacted, and allowed between four and eight weeks to comment;
- posts that reveal financial information about individuals or organizations other than Debian, will have that information removed;
- requests by the author of a post for that post not to be published will be honored;
- posts of no historical or other relevance, such as vacation announcements, or posts that have no content after personal information is removed, will not be published, unless the author requests they be published;
- comments by others who would be affected by the publication of the post will also be taken into account by the declassification team;
- the list of posts to be declassified will be made available to developers two weeks before publication, so that the decisions of the team may be overruled by the developer body by General Resolution, if necessary — in the event such a resolution is introduced (i.e., proposed and sponsored), the declassification and publication of messages specified by the resolution will be deferred until the resolution has been voted on.
Daniel Ruoso [email@example.com]
- Gregory T. Norris [firstname.lastname@example.org]
- John Lightsey [email@example.com]
- Kalle Kivimaa [firstname.lastname@example.org]
- David Moreno Garza [email@example.com]
- Neil McGovern [firstname.lastname@example.org]
The actual text of the amendment is:
Propose that the Debian project resolve that the process defined in the Proposal will be applied only for the future content of debian-private mailing list.
With 967 developers, we have:
Current Developer Count = 967 Q ( sqrt(#devel) / 2 ) = 15.5483118054662 K min(5, Q ) = 5 Quorum (3 x Q ) = 46.6449354163986 Option 1 Reached quorum: 146> 46.6449354163986 Option 2 Reached quorum: 188> 46.6449354163986
Data and Statistics
For this GR, as always, statistics have been gathered about ballots received and acknowledgements sent periodically during the voting period. Additionally, the list of voters is available. Also, the tally sheet may also be viewed (Note that while the vote is in progress it is a dummy tally sheet).
This proposal, along with the amendments, has a simple majority requirement.
Option 1 passes Majority. 1.021 (146/143)> 1 Option 2 passes Majority. 1.825 (188/103)> 1
The winner is: Option 2
Establish declassification procedure for future posts only
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. 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||Option 2||Further Discussion|