openstack
/
security-specs
Code Issues Proposed changes
RETIRED, OpenStack Security Specifications
20 Commits 1 Branch 0 Tags 384 KiB
Go to file
Doug Hellmann cf7175c1cc update sphinx 
Update to a newer version of sphinx and remove the version caps.

Ignore warnings for non-local images.

Stop using pbr's deprecated sphinx integration, and have tox call
sphinx-build directly instead.

Change-Id: I9363265647ad84cc06c499858acddab2a0b84940
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
 		2018-10-01 16:48:31 -04:00
doc/source update sphinx 2018-10-01 16:48:31 -04:00
specs Changed the mikata directory to mitaka. (Correct spelling) 2016-02-23 12:50:45 +00:00
.gitignore Setup Security Specs Repo 2015-07-07 12:08:00 -07:00
.gitreview Added .gitreview 2015-06-30 16:57:11 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-20 16:57:12 -04:00
LICENSE Setup Security Specs Repo 2015-07-07 12:08:00 -07:00
README.rst Update links in README 2018-03-02 18:06:21 +08:00
requirements.txt update sphinx 2018-10-01 16:48:31 -04:00
setup.cfg update sphinx 2018-10-01 16:48:31 -04:00
setup.py Sync with global requirements 2015-07-17 09:12:10 +02:00
tox.ini update sphinx 2018-10-01 16:48:31 -04:00

README.rst

Team and repository tags

image

OpenStack Security Specifications

This git repository is used to hold approved design specifications for additions to the OpenStack Security Projects. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the security projects and supporting tools.

The layout of this repository is:

specs/<release>/

You can find an example spec in doc/source/specs/template.rst. Fill it in with the details of a new blueprint for documentation.

For security projects, blueprints are required for larger, coordinated projects but not for small fixes. It's a judgement call for whether you need a spec, so feel free to ask in the #openstack-security IRC channel or on the openstack-security mailing list.

To propose a specification for a release-specific project, add a new file to the specs/<release> directory and post it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in Launchpad (and the spec links to Launchpad).

Please realize that not all approved blueprints will get fully implemented.

Security blueprints are being introduced with the Liberty development cycle using this repository.

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see https://wiki.openstack.org/wiki/Blueprints.

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. Please do not check in the generated HTML files as a part of your commit.

The files are published at http://specs.openstack.org/openstack/security-specs.

The git repository is located at http://git.openstack.org/cgit/openstack/security-specs/.