Jump to: navigation, search

Difference between revisions of "Fuel/Elections Fall 2015"

(Confirmed candidates:)
(Confirmed candidates:)
Line 107: Line 107:
** [http://lists.openstack.org/pipermail/openstack-dev/2015-September/075657.html Vladimir Kuklin]
** [http://lists.openstack.org/pipermail/openstack-dev/2015-September/075657.html Vladimir Kuklin]
* Fuel-library Component Lead  
* Fuel-library Component Lead  
** http://lists.openstack.org/pipermail/openstack-dev/2015-October/077053.html Sergii Golovatiuk]
** [http://lists.openstack.org/pipermail/openstack-dev/2015-October/077053.html Sergii Golovatiuk]
** [http://lists.openstack.org/pipermail/openstack-dev/2015-October/077055.html Vladimir Kuklin]
** [http://lists.openstack.org/pipermail/openstack-dev/2015-October/077055.html Vladimir Kuklin]
* Fuel-python Component Lead
* Fuel-python Component Lead

Revision as of 13:29, 16 October 2015

PTL & Component Leads Elections April 2015


  • Sergey Lukjanov (irc: SergeyLukjanov) slukjanov 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.


Project Team Lead (PTL): Manages day-to-day operations, drives the project team goals, resolves technical disputes within the project team, https://wiki.openstack.org/wiki/Governance

Component Lead: Defines architecture of a module or component in Fuel, reviews design specs, merges majority of commits and resolves conflicts between Maintainers or contributors in the area of responsibility, http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html

Fuel has two large sub-teams, with roughly comparable codebases, that need dedicated component leads: fuel-library and fuel-python. More info: https://lwn.net/Articles/648610/


  • PTL elections
    • September 18 - September 28, 21:59 UTC: Open candidacy for PTL position
    • September 29 - October 8: PTL elections
  • Component leads elections
    • October 9 - October 15: Open candidacy for Component leads positions
    • October 16 - October 22: Component leads elections


The electorate for a given PTL and Component Leads election are the Foundation individual members that are also committers for one of the Fuel team's repositories over the last year timeframe (September 18, 2014 06:00 UTC to September 18, 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 September 28, 21:59 UTC so that the emailed ballots are mailed to the correct email address.

Electorate for fuel-library and fuel-python Component Leads is based on committes to fuel-library and fuel-web repositories respectively.

List of repositories:

  • stackforge/fuel-agent
  • stackforge/fuel-astute
  • stackforge/fuel-dev-tools
  • stackforge/fuel-devops
  • stackforge/fuel-docs
  • stackforge/fuel-library
  • stackforge/fuel-main
  • stackforge/fuel-mirror
  • stackforge/fuel-nailgun-agent
  • stackforge/fuel-octane
  • stackforge/fuel-ostf
  • stackforge/fuel-ostf-plugin
  • stackforge/fuel-plugin-availability-zones
  • stackforge/fuel-plugin-calamari
  • stackforge/fuel-plugin-calico
  • stackforge/fuel-plugin-ceilometer-redis
  • stackforge/fuel-plugin-cinder-netapp
  • stackforge/fuel-plugin-cisco-aci
  • stackforge/fuel-plugin-contrail
  • stackforge/fuel-plugin-dbaas-trove
  • stackforge/fuel-plugin-detach-database
  • stackforge/fuel-plugin-detach-keystone
  • stackforge/fuel-plugin-detach-rabbitmq
  • stackforge/fuel-plugin-elasticsearch-kibana
  • stackforge/fuel-plugin-external-emc
  • stackforge/fuel-plugin-external-glusterfs
  • stackforge/fuel-plugin-external-zabbix
  • stackforge/fuel-plugin-glance-nfs
  • stackforge/fuel-plugin-ha-fencing
  • stackforge/fuel-plugin-influxdb-grafana
  • stackforge/fuel-plugin-ironic
  • stackforge/fuel-plugin-ldap
  • stackforge/fuel-plugin-lma-collector
  • stackforge/fuel-plugin-lma-infrastructure-alerting
  • stackforge/fuel-plugin-mellanox
  • stackforge/fuel-plugin-midonet
  • stackforge/fuel-plugin-neutron-fwaas
  • stackforge/fuel-plugin-neutron-lbaas
  • stackforge/fuel-plugin-neutron-vpnaas
  • stackforge/fuel-plugin-nova-nfs
  • stackforge/fuel-plugin-nsxv
  • stackforge/fuel-plugin-opendaylight
  • stackforge/fuel-plugin-saltstack
  • stackforge/fuel-plugin-solidfire-cinder
  • stackforge/fuel-plugin-swiftstack
  • stackforge/fuel-plugin-tintri-cinder
  • stackforge/fuel-plugin-tls
  • stackforge/fuel-plugin-vmware-dvs
  • stackforge/fuel-plugin-vxlan
  • stackforge/fuel-plugin-zabbix-monitoring-emc
  • stackforge/fuel-plugin-zabbix-monitoring-extreme-networks
  • stackforge/fuel-plugin-zabbix-snmptrapd
  • stackforge/fuel-plugins
  • stackforge/fuel-provision
  • stackforge/fuel-qa
  • stackforge/fuel-specs
  • stackforge/fuel-stats
  • stackforge/fuel-tasklib
  • stackforge/fuel-upgrade
  • stackforge/fuel-web
  • stackforge/python-fuelclient


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] PTL candidacy" or "[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:


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