This type is for when TC and PTL elections must overlap. There is a
built in assumption that each "phase" of an election:
- Nominations
- Campaigning
- Election
are completely synchronous
NOTE: This change leaves the template-emails broken, as I do not add new
functions for combined_$email. This is because I'd like to
If64c075b4a799574bc51ccd13019d472ee9a4b0e merge first, and I'd also like
to avoid to many rebases
Change-Id: Id39c50e71dc91bea8034ce443287463094e2f37f
This consumes (and modifies) render-statistics. Factoring this out will
be done at the end of the series
Change-Id: I878de8288f1ac047d844085f05261a6d3b1daac1
Show the number of candidates and then cleanly show the email
addresses separated by commas and without the Python formatting markup
indicating that they are unicode strings.
Change-Id: I6df888115ce556e2b029dcde0494a95a17d98abd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Process the teams in sorted order so that the verbose output is easier
to scan for details.
Change-Id: I1fc93924733831033fcf97606eca4b8638fee646
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
From time to time we have project that have a candidate that has shown
the intent to nominate, mostly likely with a review, but that candidate
isn't fully validated.
Add a hack to list those projects on the command line so they're
accounted for in the stats.
Change-Id: Ica6e416433cab1232b4b41ccc609bdf29add065c
* Fix candidate detection to look for files containing an '@' rather
than ending in '.txt'
* Clarify the tool description
* Exit early if it's a TC election
* This election cycle used a slightly different label for the nomination
phase :/ my bad
Change-Id: I8250952341850e0d58cc3910a20931060d670e88
This change fix the render-statistics command to use the new
timeline structure. It also update the name of the
check-all-candidacy command in the README.rst file
Change-Id: Iacf98655ce74880410125229cea623485a8d5e09
If we run the tools (create-directories or check-all-candidacies) under
python3 they'll fail with silly errors (like[1]). This is because we
have a number of assumptions they we'll be running under python2 like:
- pickle.protocol: we done specify one so if we write a pickle file
from python3 we can't read it in python2.
- urllib and urlparse: those modules change paths in python 2 or 3 so
use the six helpers to get the bits we want.
- Explicitly write files in binary format
- Various str vs bytes issues
- dict().keys() returns dict_keys under python3 explictly cast that to
list()
After addressing these issues we can run the tools under either python2
or python3. To make this easy to check create explicit ven2 and venv3
test environments, leaving all other testenvs to use the system default.
[1] http://paste.openstack.org/show/593823/
Change-Id: I20334a52500847c810b486c9c8b108e75a5d6303
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
* Remove TC from project list (there are only 59 project, not 60)
* Display project without_candidate and that need_election
Change-Id: I7d66d4e5ed1ab5af0950428d55062b772c32d58a