5118d12464
One of the outcomes of the discussion at the leadership training session earlier this year was the idea that the TC should set some community-wide goals for accomplishing specific technical tasks to get the projects synced up and moving in the same direction. This patch includes the proposed process for managing those goals, a template for describing a goal, the placeholder for goals for the Ocata cycle, and a tool for mechanically generating part of the documents. I had help with reviews and drafts of some portions of this text from a bunch of other folks including jroll, dtroyer, johnthetubaguy, spamaps, mordred, ttx, notmorgan, thingee, and amrith. Change-Id: I46cc66eafe9dbcfda94fb6a1a8c66c2ca77de45a Signed-off-by: Doug Hellmann <doug@doughellmann.com>
1.3 KiB
1.3 KiB
OpenStack Technical Committee Governance Documents
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters.
The Technical Committee is formally defined in the OpenStack
Foundation bylaws (in particular article 4.1(b), article 4.13 and
Appendix 4) and further refined in the reference/charter.
These pages contain OpenStack Technical Committee reference documents and track official resolutions voted by the committee.
Current Members
Reference documents and Resolutions
reference/index goals/index resolutions/index resolutions/superseded/index
See the TechnicalCommittee page in the wiki for details on how to propose governance changes.