OpenStack Technical Committee Decisions
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 2506b2e477 Merge "gitignore: add .eggs" 49 minutes ago
doc Merge "Add ':' separator for tag deliverables" 4 days ago
goals Merge "Add IPv6 support and testing goal for Train" 4 days ago
openstack_governance Drop references to git.openstack.org 1 month ago
pre-history Add some pre-history meeting summaries 5 years ago
reference Merge "Remove source license from generated doc output" 4 days ago
resolutions Add resolution to namespace unofficial projects 2 months ago
tools tools: report dissenting votes for project-update 4 days ago
.gitignore gitignore: add .eggs 4 days ago
.gitreview OpenDev Migration Patch 1 month ago
.stestr.conf add module for fetching and parsing governance data 6 months ago
.yamllint Reduce the scope of yamllints coverage 2 years ago
.zuul.yaml OpenDev Migration Patch 1 month ago
CHAIR.rst add a note to notify the community when the TC chair changes 2 months ago
README.rst clean up readme 5 months ago
requirements.txt add a script to randomly assign TC members as liaisons 7 months ago
setup.cfg move members file parsing into a reusable module 7 months ago
setup.py provide infrastructure for publishing docs to html 5 years ago
test-requirements.txt add module for fetching and parsing governance data 6 months ago
tox.ini add module for fetching and parsing governance data 6 months ago

README.rst

openstack-governance

The repository http://git.openstack.org/cgit/openstack/governance/ contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee. It also contains a library for accessing some of the machine-readable data in the repository.

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.

goals/

Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.

See https://governance.openstack.org/tc/ for details.