openstack
/
election
Code Issues Proposed changes
OpenStack Elections repository
549 Commits 1 Branch 0 Tags 12 MiB
DIGITAL Command Language 73.2%
Python 18.7%
Jinja 4.3%
C++ 1.5%
Roff 0.8%
Other 1.5%
Go to file
Tristan Cacqueray df232c3074 Refactor all parameters to configuration.yaml 
This change moves parameter from utils.py and index.rst to the
configuration.yaml. Moreover this change does:

* Use ISO 8601 dateformat in configuration
* Change events extension to use datetime instead of calendar
* Add a configuration extension to render doc substitutions

Change-Id: Ie35cb9ae2c334814afaa36b3afd606c8bcf62616
 		2016-11-09 03:24:26 +00:00
candidates Merge "Add candidacy for OpenStack TC" 2016-10-02 00:08:09 +00:00
doc/source Refactor all parameters to configuration.yaml 2016-11-09 03:24:26 +00:00
openstack_election Refactor all parameters to configuration.yaml 2016-11-09 03:24:26 +00:00
results Cargo-culting doc building from openstack/ossa 2015-09-10 13:32:36 -04:00
tools Import the new-election tool as create-directories 2016-11-09 03:24:18 +00:00
.gitignore Render rst file to doc/source 2016-11-09 03:12:51 +00:00
.gitreview Added .gitreview 2015-08-27 12:36:04 +00:00
.testr.conf Make openstack_election look more like a python module 2016-09-12 15:35:40 +10:00
README.rst Import the new-election tool as create-directories 2016-11-09 03:24:18 +00:00
configuration.yaml Refactor all parameters to configuration.yaml 2016-11-09 03:24:26 +00:00
exceptions.txt Add a couple of fullname exceptions 2016-09-21 11:27:45 +10:00
requirements.txt [tools] Render historical stats for TC elections 2016-10-09 23:56:34 +00:00
setup.cfg Import the new-election tool as create-directories 2016-11-09 03:24:18 +00:00
setup.py Add updates from global-requirements 2016-03-11 13:45:45 +11:00
test-requirements.txt Switch to hacking and fix errors 2016-10-07 13:35:46 +11:00
tox.ini Switch to hacking and fix errors 2016-10-07 13:35:46 +11:00

README.rst

openstack/election

This repository contains OpenStack Elections reference documents and tooling to run elections.

Election officials process

Preparation

A month before election starts:

  • Edit elections details (timeline, cycle timeframe):
    • edit configuration.yaml
  • Prepare new election, e.g.:
    • tox -evenv -- create-directories
  • Update index.rst to include ptl.rst
  • Commit to update website

A couple of weeks before election starts * Send 'First announce'

PTL Candidacy round

When PTL Candidacy start * Send 'Opening PTL candidacy round'

During the PTL Candidacy round: * Validate candidacy, e.g.: * tox -evenv -- check-new-candidacy, or * tox -evenv -- check-candidacy change_id * To +2 a candidate: * check commit link is indeed valid * check filename is ircname * cursory check the candidacy statement * To +Workflow, checks the previous +2 details, find another commits using --limit 5 (optionals)

  • Check candidate list and fixes badly generated name using the exception.txt file

A couple of days before the candidacy submission ends: * Render statistics and send 'Motivation call for PTL candidacy round', e.g.: * tox -evenv -- render-statistics

When PTL Candidacy submission ends: * Send 'PTL nomination ending'

PTL Election round

When PreferredEmailDeadLine is reached: * Generate ATC rolls, e.g.: * ./tools/generate-rolls.sh

When PTL Election begins: * Create CIVS page ( https://wiki.openstack.org/wiki/Election_Officiating_Guidelines#Running_the_election_itself ) * Upload rolls * Send 'PTL election opening'

A couple of days before the PTL Election ends: * Send 'PTL vote motivation call'

When PTL Election ends: * close the election and udpate the results: * tox -evenv -- close-election ptl * edit doc/sources/pike/ptl.yaml * update index.rst to include tc.rst instead of ptl.rst * Commit the change and review the results * Send 'PTL results'

TC Candidacy round

When TC Candidacy starts: * Send 'TC Candidacy Opening'

During the TC Candidacy round: * To +2 a candidate: * check candidate profile using http://www.openstack.org/community/members/ * check filename is ircname * cursory check the candidacy statement * To +Workflow, check the previous +2 details

A couple of days before the candidacy submission ends: * Send 'Motivation call for TC Candidacy round'

When TC Candidacy submission ends: * Send 'TC nomiation ending'

TC Election round

  • Create CIVS page
  • Upload rolls
  • Send 'TC election opening'

A couple of days before the TC Election ends: * Send 'TC vote motivation call'

When TC Election ends: * close the election and update the results: * tox -e venv -- close-election tc * edit doc/source/pike/tc.yaml * Commit the change and review the results * Send 'TC results'