Jump to: navigation, search

PTL Elections April 2015

Revision as of 17:59, 13 March 2015 by Tristan Cacqueray (talk | contribs) (Initial creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

PTL Elections April 2015


  • Tristan Cacqueray (tristanC) tristan dot cacqueray at enovance dot com
  • Elizabeth K. Joseph (pleia2) lyz at princessleia dot com

Election System

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


  • April 2 - April 9, 05:59 UTC: Open candidacy for PTL positions
  • April 10 - April 16: 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
  • Common Libraries (Oslo) - one position
  • Infrastructure - one position
  • Documentation - one position
  • Quality Assurance (QA) - one position
  • Deployment (TripleO) - one position
  • Release cycle management - one position
  • Message Service (Zaqar) - one position
  • Data Processing Service (Sahara) - one position
  • Key Management Service (Barbican) - one position
  • DNS Services (Designate) - one position
  • Shared File Systems (Manila) - one position

Reference: https://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml


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 Juno-Kilo timeframe (April 16, 2014 06:00 UTC to April 16, 2015 05:59 UTC).

The electorate is requested to confirm their email address in gerrit, review.openstack.org > Settings > Contact Information > Preferred Email, prior to April 9, 2015 05:59 UTC so that the emailed ballots are mailed to the correct email address.

There is a resolution to the governance repo that all of the electorate is expected to follow: https://git.openstack.org/cgit/openstack/governance/tree/resolutions/20140711-election-activities.rst.


Any member of an election electorate can propose their candidacy for the same election until April 9, 05:59 UTC. Self-nomination is common, third party nomination is required, and on-list candidate support emails are discouraged both to reduce mailing list traffic and to keep everything fair for nominees. Nominees propose their candidacy 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.

There is a resolution to the governance repo in case a program is leaderless: https://git.openstack.org/cgit/openstack/governance/tree/resolutions/20141128-elections-process-for-leaderless-programs.rst

Confirmed candidates:

  • Compute (Nova)
  • Object Storage (Swift)
  • Image Service (Glance)
  • Identity (Keystone)
  • Dashboard (Horizon)
  • Networking (Neutron)
  • Block Storage (Cinder)
  • Metering/Monitoring (Ceilometer)
  • Orchestration (Heat)
  • Database Service (Trove)
  • Bare metal (Ironic)
  • Common Libraries (Oslo)
  • Infrastructure
  • Documentation
  • Quality Assurance (QA)
  • Deployment (TripleO)
  • Release cycle management
  • Message Service (Zaqar)
  • Data Processing Service (Sahara)
  • Key Management Service (Barbican)
  • DNS Services (Designate)
  • Shared File Systems (Manila)

NB: any tie should be broken using Governance/TieBreaking.