Debian Project Leader Elections 2017
Time Line
Nomination period: | Sunday, March 5th 00:00:00 UTC, 2017 | Saturday, March 11th 23:59:59 UTC, 2017 |
---|---|---|
Campaigning period: | Sunday, March 12th 00:00:00 UTC, 2017 | Saturday, April 1st 23:59:59 UTC, 2017 |
Voting period: | Sunday, April 2th, 00:00:00 UTC, 2017 | Saturday, April 15th, 23:59:59 UTC, 2017 |
Please note that the new term for the project leader shall start on April 17th, 2017.
Nominations
- Mehdi Dogguy [[email protected]] [nomination mail] [platform]
- Chris Lamb [[email protected]] [nomination mail] [platform]
The ballot, when ready, can be requested through email by sending a signed email to [email protected] with the subject leader2017.
Data and Statistics
This year, like always, statistics will be gathered about ballots received and acknowledgements sent periodically during the voting period. Additionally, the list of voters will be recorded. Also, the tally sheet will also be made available to be viewed. Please remember that the project leader election has a secret ballot, so the tally sheet will not contain the voter's name but a HMAC that allows the voters to check that their vote is in the list of votes. There is a key generated for each voter that is send along with the ack for the vote.
Quorum
With the current list of voting developers, we have:
Current Developer Count = 1062 Q ( sqrt(#devel) / 2 ) = 16.2941707368003 K min(5, Q ) = 5 Quorum (3 x Q ) = 48.8825122104010
Quorum
- Option1 Reached quorum: 299 > 48.8825122104010
- Option2 Reached quorum: 303 > 48.8825122104010
Majority Requirement
The candidate needs a simple majority to be eligible.
Majority
- Option1 passes Majority. 17.588 (299/17) >= 1
- Option2 passes Majority. 25.250 (303/12) >= 1
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 "Mehdi Dogguy"
- Option 2 "Chris Lamb"
- Option 3 "None Of The Above"
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 | |
Option 1 | 132 | 299 | |
Option 2 | 163 | 303 | |
Option 3 | 17 | 12 |
Looking at row 2, column 1, Chris Lamb
received 163 votes over Mehdi Dogguy
Looking at row 1, column 2, Mehdi Dogguy
received 132 votes over Chris Lamb.
Pair-wise defeats
- Option 2 defeats Option 1 by ( 163 - 132) = 31 votes.
- Option 1 defeats Option 3 by ( 299 - 17) = 282 votes.
- Option 2 defeats Option 3 by ( 303 - 12) = 291 votes.
The Schwartz Set contains
- Option 2 "Chris Lamb"
The winners
- Option 2 "Chris Lamb"
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.
Debian Project Secretary