Jump to: navigation, search

Difference between revisions of "PTL Elections Fall 2013"

Line 57: Line 57:
* Block Storage (Cinder)
* Block Storage (Cinder)
** [http://lists.openstack.org/pipermail/openstack-dev/2013-September/015442.html John Griffith]
** [http://lists.openstack.org/pipermail/openstack-dev/2013-September/015442.html John Griffith]
** [http://lists.openstack.org/pipermail/openstack-dev/2013-September/015692.html Duncan Thomas]
* Metering/Monitoring (Ceilometer)
* Metering/Monitoring (Ceilometer)
** [http://lists.openstack.org/pipermail/openstack-dev/2013-September/015485.html Julien Danjou]
** [http://lists.openstack.org/pipermail/openstack-dev/2013-September/015485.html Julien Danjou]

Revision as of 16:31, 26 September 2013


  • Anita Kuno (anteaya)

Election system

Elections will be held using CIVS and a Condorcet algorithm (Schulze/Beatpath/CSSD variant). Any tie will be broken using Governance/TieBreaking.


  • Sep 20 - Sep 26: Open candidacy to PTL positions
  • Sep 27 - Oct 3: PTL elections

Elected positions

Every program must elect a PTL. PTLs are elected for 6 months:

  • Compute (Nova) - one position
  • Object Storage (Swift) - one position
  • Image Service (Glance) - one position
  • Identity (Keystone) - one position
  • Dashboard (Horizon) - one position
  • Networking (Neutron) - one position
  • Block Storage (Cinder) - one position
  • Metering/Monitoring (Ceilometer) - one position
  • Orchestration (Heat) - one position
  • Database Service (Trove) - one position
  • Bare metal (Ironic) - one position
  • Queue service (Marconi) - one position
  • Common Libraries (Oslo) - one position
  • Infrastructure - one position
  • Documentation - one position
  • Quality Assurance (QA) - one position
  • Deployment (TripleO) - one position
  • Devstack (DevStack) - one position
  • Release cycle management - one position


Except otherwise-noted in the program description, the electorate for a given program PTL election are the Foundation individual members that are also committers for one of the program projects over the Grizzly-Havana timeframe (from 2012-09-27 to 2013-09-26, 23:59 PST).


Any member of an election electorate can propose his/her candidacy for the same election. No nomination is required. They do so by sending an email to the openstack-dev@lists.openstack.org mailing-list, which the subject: "PROGRAM 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.

Confirmed candidates for Fall 2013 PTL Elections (alphabetically by last name):

Links to results