Jump to: navigation, search

Difference between revisions of "Fuel/Elections Spring 2016"

Line 1: Line 1:
=== Component Leads Elections Spring 2016 ===
=== Component Leads Elections Spring 2016 ===
DIDN'T HAPPEN DUE TO https://review.openstack.org/301194
=== Officials ===
=== Officials ===

Latest revision as of 10:10, 7 April 2016

Component Leads Elections Spring 2016

DIDN'T HAPPEN DUE TO https://review.openstack.org/301194


  • Serg Melikyan (irc: sergmelikyan) smelikyan at mirantis 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.


Component Lead: Defines architecture of a particular module or component in Fuel, resolves technical disputes in their area of responsibility. All design specs that impact a component must be approved by the corresponding component lead. See Team Structure for more details.

Fuel has three large sub-teams, with roughly comparable codebases, that need dedicated component leads:

  • fuel-library
  • fuel-web
  • fuel-ui


  • March 25 - April 7: Open candidacy for Component leads positions
  • April 8 - April 15: Component leads elections


The electorate for a given Component Leads election are the Foundation individual members that are also committers to repository corresponding to specific component over the last year timeframe (March 25, 2015 0:00 UTC to March 24, 2015 23:59 UTC).

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


Any member of an election electorate can propose their candidacy for the same election. Self-nomination is common, third party nomination is not 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: "[fuel] <component> lead candidacy" (for example, "[fuel] fuel-library lead 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:

  • Fuel Library Component Lead
  • Fuel Web Component Lead
  • Fuel UI Component Lead


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