|
1 month ago | |
---|---|---|
.zuul.d | 11 months ago | |
candidates | 4 months ago | |
doc | 1 month ago | |
openstack_election | 1 month ago | |
tools | 4 months ago | |
.gitignore | 1 year ago | |
.gitreview | 1 year ago | |
.stestr.conf | 2 years ago | |
.yamllint | 4 years ago | |
README.rst | 10 months ago | |
bindep.txt | 3 years ago | |
configuration.yaml | 5 months ago | |
exceptions.txt | 3 years ago | |
requirements.txt | 1 year ago | |
setup.cfg | 1 year ago | |
setup.py | 8 months ago | |
test-requirements.txt | 5 months ago | |
tox.ini | 5 months ago |
This repository contains OpenStack Elections reference documents and tooling to run elections.
Things to keep in mind when selecting election dates:
setup-election-config
can be used to pick some obvous dates that need to be checked by the election officials and TC
As early as possible but at least a month before election starts:
edit configuration.yaml
tox -evenv -- create-directories
A couple of weeks before election starts:
tox -e venv -- template-emails election_season
When PTL Candidacy start:
tox -e venv -- template-emails nominations_kickoff
During the PTL Candidacy round:
tox -evenv -- check-all-candidacies
, ortox -evenv -- ci-check-all-candidate-files candidates/release/project/candidates
, ortox -evenv -- check-candidacy change_id
--limit 5
(optional)exception.txt
file or requesting the candidate to update thier OSF member profile.Once the email deadline is reached:
tox -evenv -- generate-rolls
A couple of days before the candidacy submission ends:
tox -evenv -- render-statistics
tox -e venv -- template-emails nominations_last_days
When PTL Candidacy submission ends:
tox -e venv -- template-emails end_nominations
tox -evenv -- generate-rolls
When PTL Election begins:
tox -e venv -- template-emails voting_kickoff
A couple of days before the PTL Election ends:
tox -e venv -- template-emails voting_last_days
When PTL Election ends:
tox -evenv -- close-election --round ptl
edit doc/sources/pike/ptl.yaml
and set election winners to True
update-governance
step will communicate that to the TC and the process in that repo will set the project leader.doc/source/results/release/announce_ptl.rst
generated by building the docs with tox -e docs
after doc/source/results/release/ptl.yaml
has been created and updatedtox -e venv update-governance -- --governance-repo ../governance/
Things to keep in mind when selecting election dates:
setup-election-config
can be used to pick some obvous dates that need to be checked by the election officials and TC
As early as possible but at least a month before election starts:
edit configuration.yaml
A couple of weeks before election starts:
tox -e venv -- template-emails election_season
When TC Candidacy starts:
tox -e venv -- template-emails nominations_kickoff
During the TC Candidacy round:
A couple of days before the candidacy submission ends:
tox -e venv -- template-emails nominations_last_days
When TC Candidacy submission ends:
tox -e venv -- template-emails end_nominations
Once the email deadline is reached:
tox -evenv -- generate-rolls
The TC election includes a period after the candidates are defined but before the election, for candidates to answer questions from the community. Open this with:
tox -e venv -- template-emails campaigning_kickoff
Before TC Election begins:
Send to other officials to verify
- Check number of seats
- Check closing date
When TC Election begins:
tox -e venv -- template-emails voting_kickoff
A couple of days before the TC Election ends:
tox -e venv -- template-emails voting_last_days
When TC Election ends:
tox -e venv -- close-election --round tc
edit doc/source/pike/tc.yaml
setting the winners to True
doc/source/results/release/announce_tc.rst
generated by building the docs with tox -e docs
after doc/source/results/release/tc.yaml
has been created and updatedreference/members
in governance repository
chair
and vice-chair
from filetc-election-summary.py
with election statistics