openstack
/
election
Code Issues Proposed changes
OpenStack Elections repository
703 Commits 1 Branch 0 Tags 12 MiB
DIGITAL Command Language 73.2%
Python 18.8%
Jinja 4.3%
C++ 1.5%
Roff 0.8%
Other 1.4%
Go to file
Tristan Cacqueray 8791d36b37 Rewrite the event logic in javascript 
The current events extension is computing the statuses at build time,
which is getting incorrect when an event is outdated until there is
a rebuild. This change fix that by doing the event status computation
at load time in javascript.

Moreover this change removes an unused import in utils.

Change-Id: Ifd1b84ff0182cf9bb7950da3d59f36c83019ac30
 		2017-01-30 01:48:11 +00:00
candidates Merge "Adding matthew wagoner candidacy for Community App Catalog" 2017-01-30 00:55:55 +00:00
doc/source Rewrite the event logic in javascript 2017-01-30 01:48:11 +00:00
openstack_election Rewrite the event logic in javascript 2017-01-30 01:48:11 +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
.yamllint Allow human readable yaml 2017-01-05 12:57:03 +11:00
README.rst Merge "Minor fix to follow-up last refactor" 2017-01-05 04:18:08 +00:00
configuration.yaml Prepare Pike PTL election 2016-12-21 08:53:23 +00:00
exceptions.txt Fix PTL candidates name 2017-01-30 01:14:31 +00:00
requirements.txt Support for running tools under python3 2017-01-05 12:57:03 +11:00
setup.cfg Don't build manpages 2017-01-05 12:57:04 +11: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 Update default tox envs to be py35 rather than py34 2017-01-05 12:57:03 +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-all-candidacies, 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

Once the email deadline is reached: * Ask the TC chair to tag the governance repository

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'