Blueprints for the barbican project
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.
pengyuesheng 7b6075717b Blacklist sphinx 2.1.0 (autodoc bug) 2 months ago
doc/source Secret Consumers 5 months ago
specs Secret Consumers 5 months ago
.gitignore Ignore some files during running tox 2 years ago
.gitreview OpenDev Migration Patch 7 months ago
.zuul.yaml import zuul job settings from project-config 1 year ago
LICENSE Add License and README 5 years ago
README.rst Update README and specs/template.rst 6 months ago
requirements.txt Blacklist sphinx 2.1.0 (autodoc bug) 2 months ago
setup.cfg Fix author-email in setup.cfg 10 months ago
setup.py First Pass at Doc Build 5 years ago
tox.ini Update min tox version to 2.0 1 year ago

README.rst

OpenStack Barbican Specifications

image

This git repository is used to hold approved design specifications for changes to the Barbican 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:

specs/<release>/

You can find an example spec in 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 story in storyboard. Not all approved blueprints will get fully implemented.

Specifications have to be re-submitted 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:

http://blueprints.launchpad.net/barbican

For more information about working with gerrit, see:

https://docs.openstack.org/infra/manual/developers.html#development-workflow

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.