Jump to: navigation, search

Difference between revisions of "PTL Elections September/October 2014"

(Add Ben Swartzlander, James Slagle and Anne Gentle candidacies)
(Add Douglas Mendizabal candidacy)
Line 90: Line 90:
 
** [http://lists.openstack.org/pipermail/openstack-dev/2014-September/046636.html Flavio Percoco]
 
** [http://lists.openstack.org/pipermail/openstack-dev/2014-September/046636.html Flavio Percoco]
 
* Key Management Service (Barbican)
 
* Key Management Service (Barbican)
 +
** [http://lists.openstack.org/pipermail/openstack-dev/2014-September/047161.html Douglas Mendizabal]
 
* DNS Services (Designate)
 
* DNS Services (Designate)
 
** [http://lists.openstack.org/pipermail/openstack-dev/2014-September/046820.html Kiall Mac Innes]
 
** [http://lists.openstack.org/pipermail/openstack-dev/2014-September/046820.html Kiall Mac Innes]

Revision as of 17:00, 25 September 2014

PTL Elections September/October 2014

Officials

  • Anita Kuno (anteaya) anteaya at anteaya dot info
  • Tristan Cacqueray (tristanC) tristan dot cacqueray at enovance 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.

Timeline

  • September 19 - September 26, 05:59 UTC: Open candidacy for PTL positions
  • September 26 - October 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
  • 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
  • Data Processing Service (Sahara) - one position
  • Message Service (Zaqar) - one position
  • Key Management Service (Barbican) - one position
  • DNS Services (Designate) - one position
  • Shared File Systems (Manila) - one position


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

Electorate

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 Icehouse-Juno timeframe (September 26, 2013 06:00 UTC to September 26, 2014 05:59 UTC).

The electorate is requested to confirm their email address in gerrit, review.openstack.org > Settings > Contact Information > Preferred Email, prior to September 26, 2014 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: http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20140711-election-activities.rst.

Candidates

Any member of an election electorate can propose their candidacy for the same election until September 26, 05:59 UTC. 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: