Technical Committee Tracker
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
Status last updated: 2018/05/30
Project team changes
Other Initiatives
Allow projects to drop py27 support in the PTI
Drivers: mugsie
Status: Under discussion
References
Starting work on constellations
Drivers:
Status: Under discussion [5]
Update the requirements for affiliation diversity for new projects
Drivers: zaneb
Status: Under discussion
References
Clarify new project requirements for affiliation diversity
Drivers: zaneb
Status: Under discussion
References
Include the rationale for tracking base services
Drivers: fungi
Status: Approved
References
Note that the old incubation/graduation process is obsolete
Drivers: zaneb
Status: Approved
References
Adding a key manager to base services
Drivers: fungi
Status: In progress
References
- https://etherpad.openstack.org/p/BOS-forum-key-management
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
Improving the visibility of status updates and announcements
Drivers: dhellmann, cdent, ttx
Status: In progress
We are investigating mailman 3, blogging, and Matrix, among other solutions.
Correction to TC member election section of bylaws
Drivers: fungi, dhellmann
Status: On hold until the next Foundation vote
This was discussed in the joint leadership meeting in Vancouver. The change requires a member vote, and the Board passed a resolution allowing the Foundation Secretary to propose the bylaws change as part of the next Board election (early 2019). We anticipate other bylaws changes at the same time.
Section 3.b.i reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"
How do we track updates to old goals for new projects?
Drivers: dhellmann
Status: In progress
References
- See the Kolla Python 3.5 update for example.
Ownership and publishing for the operations guide
Drivers: dhellmann
Status: Resolved, they will start a SIG to own the repository for the guide so it can be published to docs.openstack.org.
References
- Wednesday, May 23, 2018 - session at Vancouver summit
- http://lists.openstack.org/pipermail/openstack-operators/2018-May/015321.html
StarlingX
Drivers: mnaser, EmilienM
Status: In discussion
References
Murano Team Status
Drivers: dhellmann
Status: On hold
With ZTE's future at question, a Murano team member contacted me about the future of the project. I am currently waiting for the question to be raised in an email thread.
Organizational diversity tags
Drivers: ttx, mnaser
Status: Under discussion
References
Clarifying the terms of service for hosted projects
Drivers: zaneb
Status: Under discussion
References
Technical Vision for OpenStack
Drivers: zaneb, cdent (?)
Status: Early
Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.
References
Stein Series Goals
Drivers: smcginnis (?)
Status: Early
Sean organized a session at the Rocky Forum to discuss improving our goal selection process and specific goals for Stein.
References