openstack
/
governance
Code Issues Proposed changes
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.
4750 Commits
1 Branch
14 Tags
38 MiB
 
 
Tree: de73458a6b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'de73458a6b'
${ noResults }
Zuul de73458a6b
Merge "Changing new release cadence name" 		3 months ago
doc Remove TC Liaisons framework 4 months ago
goals Move FIPS goal from proposed to selected. 3 months ago
openstack_governance Remove TC Liaisons framework 4 months ago
pre-history Add some pre-history meeting summaries 9 years ago
reference Merge "Adding gmann to oslo tact-sig liaison" 3 months ago
resolutions Changing new release cadence name 3 months ago
tools Remove TC Liaisons framework 4 months ago
.gitignore gitignore: add .eggs 3 years ago
.gitreview OpenDev Migration Patch 3 years ago
.stestr.conf add module for fetching and parsing governance data 4 years ago
.yamllint Update assignment script to output to projects.yaml file 3 years ago
.zuul.yaml Update python testing template to yoga 5 months ago
CHAIR.rst Remove TC Liaisons framework 4 months ago
README.rst Replace git.openstack.org URLs with opendev.org URLs 3 years ago
bindep.txt bindep: add pcre development headers to build python-pcre 3 years ago
requirements.txt Fix gate 11 months ago
setup.cfg setup.cfg: Replace dashes with underscores 1 year ago
setup.py provide infrastructure for publishing docs to html 9 years ago
test-requirements.txt Add doc/requirements 2 years ago
tox.ini Merge "Remove the tags framework (part 1)" 6 months ago

README.rst

openstack-governance

The repository https://opendev.org/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.