Update the URLs in various templates and generated content to
consistently use https:// instead of a mix of that and http://, and
while we're at it set the homepage for the Python package of this
repo to the election site rather than the OpenStack Foundation site.
Change-Id: I4fa53076ed9bcdf1545d9c4aa5e80dc5dad95210
All governance subwebsites switched from using an old
oslosphinx-based theme to inheriting from openstackdocstheme
instead. Also switch the election website for consistency.
Depends-On: https://review.openstack.org/611761
Change-Id: I3ec2ff2bc2ec6683919ea6541fd657cdc8723df8
This does several things to reduce the number of warnings generated in a
docs build.
. Only generate the {ptl,tc}.rst for the type of election we're running
. use a for loop to match the undreline with the section title
. Ensure that we use anonymous hyperlinks ``__ vs ``_
. tell sphinx to ignore the generated announcement as they're not linked
There are still 4 left which look to me like actual bugs in
sphinux/docutils rather than our RST.
Change-Id: I64a12d1c49c5b71a6849ad1724ac4ae09daeb85a
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 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