OpenStack Technical Committee Decisions
Go to file
Tom Fifield 2494660b03 Add governance-uc repo
As per mailing list discussion[1], governance.openstack.org will
become a neutral place for all of OpenStack governance reference
information (Board, TC, UC).

This change adds a repository, governance-uc, which is to contain
the content for the UC component of governance.openstack.org, and
is step one of the 5 step plan:

- Create the repository (UC, infra)
- Populate it with the data you want there (UC)
- Work with infra to publish under /uc (UC, infra)
- Propose content for the neutral page (TC, UC)
- Change openstack/governance to publish under /tc,
  set up redirects/aliases (TC, infra)

[1] http://lists.openstack.org/pipermail/openstack-tc/2016-June/001223.html

Change-Id: I941f2df200da0ac714f4afcf0c9d33d2711517d1
Depends-On: I80debe64d6fbf31d23415f373adf47a7a034b7f0
2016-06-16 20:32:16 +08:00
doc/source Add team name exception for I18n team 2016-05-26 15:18:19 +09:00
pre-history Add some pre-history meeting summaries 2013-11-11 09:08:57 -06:00
reference Add governance-uc repo 2016-06-16 20:32:16 +08:00
resolutions Merge "add resolution asking defcore committee to avoid using proxy APIs in tests" 2016-05-31 20:22:00 +00:00
tools Retire release:has-stable-branches tag 2016-04-14 11:29:35 +02:00
.gitignore ignore files created by pbr during build 2015-05-23 08:09:26 -07: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
requirements.txt Keep py3.X compatibility for urllib 2015-12-23 20:48:17 +05:30
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 Lint YAML files 2016-01-25 16:32:54 +01:00
tox.ini Lint YAML files 2016-01-25 16:32:54 +01:00

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.