openstack
/
governance
Code Issues Proposed changes
OpenStack Technical Committee Decisions
383 Commits 1 Branch 18 Tags 40 MiB
Python 97.6%
DIGITAL Command Language 1.2%
Shell 1%
C++ 0.2%
Go to file
James E. Blair 321a020cbc Let projects add repos without prior-approval 
Some OpenStack projects are adding git repos at a moderate pace
and generally the TC is rubber-stamping them as long as the PTL
approves.  Explicitly codify that this is desirable -- the TC
doesn't really care how many git repos it takes to accomplish a
task, so as long as a new repo fits within the existing mission
statement, indicate that it is permissible to add it without
prior TC approval.

This is not strictly a "new project requirement", however, this
document seems to be the best existing place to add it as it
relates to project creation.

Change-Id: I34acfe4ffe5a0af6a941e70a5315a07d036e6c24
 		2015-04-14 11:50:23 -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 Let projects add repos without prior-approval 2015-04-14 11:50:23 -07:00
resolutions Fix tiny typo: compatability => compatibility 2015-04-10 15:14:09 -04:00
tools Add diversity helper script 2015-04-07 09:27:23 -04: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.