OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|5 hours ago|
|doc||1 month ago|
|goals||1 month ago|
|openstack_governance||4 days ago|
|pre-history||5 years ago|
|reference||1 day ago|
|resolutions||3 weeks ago|
|tools||1 month ago|
|.gitignore||5 months ago|
|.gitreview||5 hours ago|
|.stestr.conf||5 months ago|
|.yamllint||2 years ago|
|.zuul.yaml||5 hours ago|
|CHAIR.rst||1 month ago|
|README.rst||4 months ago|
|requirements.txt||6 months ago|
|setup.cfg||6 months ago|
|setup.py||5 years ago|
|test-requirements.txt||5 months ago|
|tox.ini||5 months ago|
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.
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
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.
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.