Jump to: navigation, search

Governance/TCElectionsFall2012

< Governance
Revision as of 12:22, 10 August 2012 by ThierryCarrez (talk)

Election officials

tbd. Election officials cannot run for the election they are an official for.

PTL Elections

Timeline

  • Aug 30 - Sep 5: Open candidacy to PTL positions
  • Sep 7 - 13: PTL elections

Number of elections and seats

  • Nova PTL (one position)
  • Swift PTL (one position)
  • Glance PTL (one position)
  • Horizon PTL (one position)
  • Keystone PTL (one position)
  • Quantum PTL (one position)
  • Cinder PTL (one position)
  • openstack-common PTL (one position)

Electorate

The electorate for a given project PTL election are the Foundation individual members that are also committers for said project over the Essex-Folsom timeframe, up to 23:59 PST on August 29, 2012.

Candidates

Any member of an election electorate can propose his candidacy for the same election. No nomination is required. They do so by sending an email to the openstack@lists.openstack.org mailing-list, which the subject: "PROJECT PTL candidacy" (for example for Glance: "Glance PTL candidacy"). The email can include a description of the candidate platform. The candidacy is then confirmed by one of the election officials, after verification of the electorate status of the candidate.

Technical committee direct members Election

Timeline

  • Sep 13 - 19: Open candidacy to TC directly-elected seats
  • Sep 21 - 27: TC direct seats election

Number of elections and seats

  • Technical committee directly-elected seats (3 positions)

Electorate

The electorate for the TC direct seats election are the Foundation individual members that are also committers for an official OpenStack project (as defined here), over the Essex-Folsom timeframe, up to 23:59 PST on August 29, 2012.

Candidates

Any member of the TC direct seats election electorate can propose his candidacy for this election. No nomination is required. They do so by sending an email to the openstack@lists.openstack.org mailing-list, which the subject: "TC candidacy". The email can include a description of the candidate platform. The candidacy is then confirmed by one of the election officials, after verification of the electorate status of the candidate.

Voting process

Voting tool

Two online voting tools are currently considered.

OPAvote

See http://www.opavote.org/

Benefits:

  • Straightforward interface
  • No ex-aequo
  • Multiple algorithms supported (STV or Condorcet)
  • Election official can trigger reminder emails for voters who haven't voted yet

Drawbacks:

  • Limited to 20 candidates and 500 voters (though the limit can be increased)
  • No result ranking after the winners set
  • Forces the voter to rank everyone
  • Only used in Ceilometer lead election so far

CIVS

See http://www.cs.cornell.edu/w8/~andru/civs/

Benefits:

  • Full results ranking (allowing to know who is 4th in the TC election)
  • Possibility to rank people at the same level
  • Used in all past OpenStack elections

Drawbacks:

  • Sometimes results produce ex-aequo candidates (no strong winners set)
  • Only Condorcet (with or without the experimental proportional representation mode) is available

Voting algorithm

Four possibilities for the algorithm to use:

  • Condorcet (OPAVote or CIVS): may produce cycles that need to be cut using some extra rule (here the Schulze algorithm)
  • RP Condorcet (CIVS): experimental algorithm that is supposed to ensure proportionality within Condorcet
  • North Ireland STV (OPAvote): good STV compromise that uses random and fractional transfer
  • Warren STV (OPAvote): most representative STV mode