Congress Design Specifications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 531fc152ee OpenDev Migration Patch 1 month ago
doc/source Merge "Experimental component for a JSON data model" 4 months ago
specs Experimental component for a JSON data model 5 months ago
tests Enable specs sphinx build 3 years ago
.gitignore Switch to stestr 9 months ago
.gitreview OpenDev Migration Patch 1 month ago
.stestr.conf Switch to stestr 9 months ago
.zuul.yaml import zuul job settings from project-config 9 months ago
LICENSE adding all spec files 4 years ago
README.rst Show team and repo badges on README 2 years ago
requirements.txt Switch to stestr 9 months ago
setup.cfg Change openstack-dev to openstack-discuss 5 months ago adding all spec files 4 years ago
tox.ini fix tox python3 overrides 7 months ago


Team and repository tags


OpenStack Congress Specifications

This git repository is used to hold approved design specifications for additions to the Congress project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.

The layout of this repository is:


You can find an example spec in doc/source/specs/template.rst.

Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.

Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.

Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

For more information about working with gerrit, see:

To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.