|
|
| (9 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ . | + | The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/. We hold [https://governance.openstack.org/tc/#meeting weekly meetings]. |
| | | | |
| − | This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. Conversation starters for the office hours are [https://etherpad.openstack.org/p/tc-office-hour-conversation-starters here]. | + | This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. Since Xena release cycle we started to track the items in etherpad. At the start of every release cycle, the OpenStack Technical Committee will prepare that release tracker which can include the backlogs from the previous release if any item is not finished and worth continuing. |
| | | | |
| − | Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].
| + | * [https://etherpad.opendev.org/p/tc-2024.2-tracker 2024.2 Release Cycle Tracker] |
| − | | + | * [https://etherpad.opendev.org/p/tc-2024.1-tracker 2024.1 Release Cycle Tracker] |
| − | '''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''
| + | * [https://etherpad.opendev.org/p/tc-2023.2-tracker 2023.2 Release Cycle Tracker] |
| − | | + | * [https://etherpad.opendev.org/p/tc-2023.1-tracker 2023.1 Release Cycle Tracker] |
| − | == Project team changes ==
| + | * [https://etherpad.opendev.org/p/tc-zed-tracker Zed Release Cycle Tracker] |
| − | | + | * [https://etherpad.opendev.org/p/tc-yoga-tracker Yoga Release Cycle Tracker] |
| − | == Documentation Changes ==
| + | * [https://etherpad.opendev.org/p/tc-xena-tracker Xena Release Cycle Tracker] |
| − | | |
| − | | |
| − | == Other Initiatives ==
| |
| − | | |
| − | === Help most needed list evolution ===
| |
| − | Drivers: ttx
| |
| − | | |
| − | Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html mailing-list]
| |
| − | | |
| − | Asking for help was not very successful, partially due to how intimidating it is for new contributors to join. Maybe proposing mentoring if you offer time is a more positive way to look at it.
| |
| − | | |
| − | === Formalizing pop-up teams ===
| |
| − | Drivers: ttx
| |
| − | | |
| − | Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002251.html mailing-list]
| |
| − | | |
| − | Cross-project work is still difficult. Maybe formalizing the concept of pop-up teams a bit more, with clear scope and disband criteria (under the model of [https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md Kubernetes working groups]) would help.
| |
| − | | |
| − | === Technical Vision for OpenStack ===
| |
| − | Drivers: zaneb, ttx, cdent
| |
| − | | |
| − | Status: Under dicussion
| |
| − | | |
| − | The initial [https://governance.openstack.org/tc/reference/technical-vision.html vision] has been created. The agreed next step (to be done by cdent and TheJulia) is to publicize it and request that projects self-evaluate themselves against the vision.
| |
| − | | |
| − | References
| |
| − | * [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session] | |
| − | * https://etherpad.openstack.org/p/tech-vision-2018 | |
| − | * [https://review.openstack.org/592205 Document review]
| |
| − | | |
| − | === tags indicating the upgrade support in deployment tools ===
| |
| − | Drivers: ttx
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | During the FFU session at the Rocky Forum, Dan Smith and David Medberry indicated interest in defining tags to describe what upgrade features deployment tools have.
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes] | |
| − | | |
| − | === Next steps in TC Vision / defining role of the TC ===
| |
| − | Drivers: ttx, TheJulia, cdent
| |
| − | | |
| − | Status:
| |
| − | Document created as [https://governance.openstack.org/tc/reference/role-of-the-tc.html role of the tc]. Next step (by cdent): to publicize and get community verify that it represent reality and that reality is what people desire; find out what's missing.
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum] | |
| − | | |
| − | === Clarifying Requirements for PTL Contact Details ===
| |
| − | | |
| − | Drivers:
| |
| − | | |
| − | Monty pointed out that we have a general community expectation that leaders are visible via IRC. That may not always be the case for some corners of our community, however. We need to decide whether we want to require IRC nicks for PTL candidates, whether we want to include other forms of contact for other chat platforms (optionally?), etc. and write a resolution so the election official have clear guidance.
| |
| − | | |
| − | 2018-09-09 - need to figure out how to ask PTLs for a primary means of contact without dictating a specific means and without opening ourselves up to having to sign on to every new chat tool
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | References:
| |
| − | | |
| − | * https://review.openstack.org/#/c/589696/ (abandoned)
| |
| − | * https://review.openstack.org/#/c/590082/ (fills in missing nicks with "None supplied")
| |
| − | | |
| − | == Tracking OpenStack team health ==
| |
| − | See [[OpenStack_health_tracker]] for liaison assignment and status updates.
| |
| − | | |
| − | | |
| − | == Recently completed things ==
| |
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. Since Xena release cycle we started to track the items in etherpad. At the start of every release cycle, the OpenStack Technical Committee will prepare that release tracker which can include the backlogs from the previous release if any item is not finished and worth continuing.
