d377b3834b
There was a question during the Nov 29 weekly meeting [1] about when is it ok to +2 a spec, when the other parts do not relate to one's area of expertise but also to others. This includes the answer proposed into the policy. Also, change 'devtest' to 'undercloud install' to reflect the tooling update. [1] http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-11-29-14.00.log.html Change-Id: I12c4cdd6c61188a570b8d891d30af36bac794157 |
||
---|---|---|
doc/source | ||
specs | ||
tests | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
tox.ini |
README.rst
Team and repository tags
tripleo-specs
TripleO specs repository
- Free software: Apache license
- Documentation: https://specs.openstack.org/openstack/tripleo-specs
- Source: http://git.openstack.org/cgit/openstack/tripleo-specs
- Bugs: http://bugs.launchpad.net/tripleo
Features
- TODO