openstack/governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
386 Commits 1 Branch 19 Tags 42 MiB
Python 96.3%
DIGITAL Command Language 2.5%
Shell 1%
C++ 0.2%
bf8d72ea96
Go to file
Joe Gordon bf8d72ea96 Add tool/framework to automatically validate the tag applications. 
Add tools/validate_tags.py framework to automatically validate the usage
of tags in reference/projects.yaml. This is only for tags that can be
enforced pragmatically.

This is not intended for gating purposes, rather to make the process of
updating projects.yaml easier.

Supports both team and repository based tags.

Updated diversity.py to work with validate_tags

Change-Id: Id477bfcfccb4dbf5f03f328273c9487ccc48e054
2015-04-20 08:46:51 -07:00
doc/source Publish the extra ATCs for projects 2015-03-04 18:04:53 -05:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Merge "Adding Mistral Workflow Service to OpenStack" 2015-04-14 20:21:15 +00:00
resolutions Fix tiny typo: compatability => compatibility 2015-04-10 15:14:09 -04:00
tools Add tool/framework to automatically validate the tag applications. 2015-04-20 08:46:51 -07:00
.gitignore Add .pyc files to gitignore 2015-03-03 14:58:34 -08:00
.gitreview Added .gitreview 2013-08-30 16:00:06 +00:00
README.rst provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
setup.cfg update doc build requirements 2014-10-27 13:44:50 -04:00
setup.py provide infrastructure for publishing docs to html 2014-01-07 15:29:11 -05:00
test-requirements.txt Build list of teams from YAML file 2015-02-24 18:15:04 -05:00
tox.ini begin conversion to rst 2014-04-15 08:24:17 -04:00

README.rst

This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.

Directory structure:

reference/

Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.

resolutions/

When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.

See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.