When building docs if a single candidate runs for PTL of multiple projects
sphinx will generate warnings like:
.../openstack/election/doc/source/ocata/ptl.rst:3: WARNING: Duplicate explicit target name: "tony breeds (tonyb)".
.../openstack/election/doc/source/ocata/ptl.rst:3: WARNING: Duplicate explicit target name: "tony breeds (tonyb)".
.../openstack/election/doc/source/ocata/ptl.rst:3: WARNING: Duplicate explicit target name: "tony breeds (tonyb)".
Make the candidate links anonymous to avoid those warnings.
Even though it can't be a problem for the TC make those links anonymous for
consistency
Change-Id: I5a812db7f9ac1438b79db0cd8c77f8850c1922bf
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
This change modifies the timeline structure to describe a
start and end date instead of two different events.
Moreover this change adds:
* the number of days remaining until the next event.
* a 'next' status when current event haven't started yet
Change-Id: Ib76b0315a7409a8442c1be6f8341b0596c1d56ae
This change renders dynamic rst file to doc/source instead of candidate directory
so that they gets published by infra docs jobs. This is just to be able to access
the source rst file on docs-draft.openstack.org host.
Change-Id: I2435531d091ff051338c4ba9a495834d6653ab68
./doc/source/_exts/candidates.py:20:1: H306 imports not in alphabetical order (jinja2.filesystemloader, jinja2.environment.environment)
./doc/source/_exts/events.py:17:1: H306 imports not in alphabetical order (os, calendar)
./doc/source/_exts/events.py:21:1: H306 imports not in alphabetical order (jinja2.filesystemloader, jinja2.environment.environment)
./openstack_election/check_candidacy.py:62:29: E126 continuation line over-indented for hanging indent
./openstack_election/utils.py:27:1: H306 imports not in alphabetical order (yaml, re)
./openstack_election/cmds/close_election.py:90:9: H232 Python 3.x incompatible octal 755 should be written as 0o755
./openstack_election/tests/test_utils.py:25:21: E126 continuation line over-indented for hanging indent
./tools/new-election.py:18:31: H301 one import per line
./tools/new-election.py:27:5: H233 Python 3.x incompatible use of print operator
./tools/new-election.py:31:5: H233 Python 3.x incompatible use of print operator
./tools/new-election.py:41:5: H233 Python 3.x incompatible use of print operator
Co-Authored-By: Nguyen Hung Phuong <phuongnh@vn.fujitsu.com>
Change-Id: Idd9bc1f1f92da1658e6da2af588c575ee0ba2cb0
Per previous discussions, the proper contact point for Openstack
election questions should be the #openstack-dev IRC channel, not
the #openstack-election IRC channel.
Change-Id: I86c4eeecf601b33c96325cad3a39bdd31a9e922b
* close-election [ptl|tc] generate a yaml archive in doc/source
* docs render the results pages based on the archive
* add documentation about the whole election officials process
Change-Id: I8f737f33befc1e8af52dac9c059f73e2874eb5f8
This change enforce the first and last component
of a fullname to start with an uppercase letter.
This is to keep user's custom capitalisation such as:
* middle name should be lower-case
* keep in-middle uppercase such as "McGinnis"
Change-Id: Ifdad9f05c0d74d18396e9b06bd57c1c0f391be8d
Currently we don't need to do this thing but it's the only piece of data
missing that prevents us from scripting an updte to projects.yaml in the
openstack/governance repo
Change-Id: Ia346cef333158f4a6f2c57e519d4ad58045e3a1a
This change refactor events.yaml into something more generic and
usable by openstack_election module
Change-Id: I26e25cb31c60645742baba1e73f8da9043029381
Samuel Cassiba's IRC 'sc`' contains a ` which has special meaning in RST
Escape the URL and strings as passed to sphinx to render correctly.
Note: if we discover similarly problematic characters we'll need to create a
more comprehensive escape function.
Change-Id: I4634457b7251ca96fde91b48a09538fccb721374
This change improves candidate list rendering using gerrit to retrieve fullname.
The list rendering now uses the openstack_election libraries and some part
have been refactored accordingly.
Change-Id: Iccba3e4c529740758323b51548a2144fc7c77879
This change now uses the new schema to render candidate
list including ircname.
Moreover this change introduces an exceptions.txt file to
manage candidacies exception where a candidate isn't the
git commit author of a candidacy statement. In such case
the candidacy needs to be manually verified and the candidate
fullname needs to be added to the exceptions.txt.
Change-Id: I2e59f4880d34cdb09321dbc110ecf5a103f81dff
This changes add a new 'events' extensions to manage
events timeline. Events are described in the events.yaml file.
The 'events' extensions will generate an rst document with:
* Timer clock for upcoming event
* Tabulated events list
Change-Id: Ib5c9d96663bd2197beea7aab226a3d46bc82067c
