CloudKitty (Rating) design specification
Go to file
zhouxinyong 8d4c819e6b Applying the HTTPS protocol in template.rst.
To keep the website in this file be more robust,we'd better update the links to HTTPS type

Change-Id: I2800910f65b78e503c19f3a1b95c266c6def838f
2018-11-14 08:37:55 +00:00
doc/source Add pike in cloudkitty-specs 2018-10-23 09:31:59 +00:00
specs Applying the HTTPS protocol in template.rst. 2018-11-14 08:37:55 +00:00
.gitignore Initialize cloudkitty-specs repo 2017-01-09 09:37:44 +08:00
.gitreview Added .gitreview 2016-11-24 15:09:06 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-31 08:57:19 -04:00
LICENSE Initialize cloudkitty-specs repo 2017-01-09 09:37:44 +08:00
README.rst Refreshing the repository 2018-10-25 16:39:58 +02:00
requirements.txt Initialize cloudkitty-specs repo 2017-01-09 09:37:44 +08:00
setup.cfg Initialize cloudkitty-specs repo 2017-01-09 09:37:44 +08:00
setup.py Initialize cloudkitty-specs repo 2017-01-09 09:37:44 +08:00
tox.ini fix tox python3 overrides 2018-09-26 18:50:37 -04:00

README.rst

OpenStack Cloudkitty Specifications

This git repository is used to hold approved design specifications for additions to the Cloudkitty 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 story for a given release can be found by looking at the story in Storyboard. Not all stories 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.

For more information about working with gerrit, see:

http://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.