OpenStack Technical Committee Decisions
d4e2124de0
Hi! Despite being away for the first meeting of the new membership, I'd like to propose myself to continue chairing the OpenStack Technical Committee in the coming 6 months. We need to go through a number of significant changes, to adapt OpenStack to the new challenges created by this post-hype phase we are currently in. That will likely involve an increase in the number of janitorial tasks which traditionally fell on the Technical Committee chair. As part of my job at the OpenStack Foundation, I'm able to continue dedicating substantial time tracking efforts and pushing for their completion. I hope you will trust me to help us all through those needed changes. Note: Other candidates should propose alternate patches to this one, and we can use Gerrit votes to select the winner. Change-Id: I8b6464ca96f5c04e76794aee05edacaaf4404cfd |
||
|---|---|---|
| doc/source | ||
| goals | ||
| pre-history | ||
| reference | ||
| resolutions | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .yamllint | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
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.
- 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://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.