|
|
| (42 intermediate revisions by 7 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 ==
| |
| − | | |
| − | === Allow projects to drop py27 support in the PTI ===
| |
| − | Drivers: mugsie, dhellmann
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | References
| |
| − | * [https://review.openstack.org/561922 PTI documentation change]
| |
| − | * [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline] APPROVED
| |
| − | * [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes] | |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]
| |
| − | * [https://review.openstack.org/#/c/575933/ python 3 as default goal]
| |
| − | | |
| − | === Starting work on constellations ===
| |
| − | | |
| − | Drivers:
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | References
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html openstack-dev mailing list post]
| |
| − | * [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
| |
| − | * [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation] | |
| − | | |
| − | === Adding a key manager to base services ===
| |
| − | Drivers: fungi
| |
| − | | |
| − | Status: Discussing going beyond "castellan-compatible"
| |
| − | | |
| − | References
| |
| − | * https://etherpad.openstack.org/p/BOS-forum-key-management
| |
| − | * ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
| |
| − | * https://review.openstack.org/572656 castellan-compatible key store - APPROVED
| |
| − | | |
| − | === 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 [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"
| |
| − | | |
| − | === StarlingX ===
| |
| − | Drivers: mnaser, EmilienM
| |
| − | | |
| − | Status: [https://storyboard.openstack.org/#!/story/2002123 In progress]
| |
| − | | |
| − | References
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130913.html ML thread post-summit discussions]
| |
| − | * [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]
| |
| − | | |
| − | === Clarifying the terms of service for hosted projects ===
| |
| − | Drivers: zaneb, ttx
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | Ties into the OSF project governance discussion at board-level. A strawman should be proposed as a result to the ML soon.
| |
| − | | |
| − | References
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130807.html openstack-dev mailing list thread raising the topic]
| |
| − | | |
| − | === Technical Vision for OpenStack ===
| |
| − | Drivers: zaneb, ttx, 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
| |
| − | * [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
| |
| − | | |
| − | === 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
| |
| − | * [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21738/s-release-goals Rocky Forum session]
| |
| − | | |
| − | === Anti-nitpicking Cultural Change ===
| |
| − | Drivers: TheJulia, ttx
| |
| − | | |
| − | Status: Done
| |
| − | | |
| − | References
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]
| |
| − | * [https://review.openstack.org/#/c/570940/ principle about valuing peer review] APPROVED
| |
| − | | |
| − | === 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] | |
| − | | |
| − | === Reviewing the TC Vision ===
| |
| − | Drivers: ttx, EmilienM, fungi
| |
| − | | |
| − | Status: [https://storyboard.openstack.org/#!/story/2002132 In progress]
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum] | |
| − | | |
| − | === Reviewing TC Office Hour Times and Locations ===
| |
| − | Drivers: dhellmann
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible.
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
| |
| − | | |
| − | === Actively Monitoring Teams ===
| |
| − | Drivers: dhellmann
| |
| − | | |
| − | Status: In process
| |
| − | | |
| − | During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum] | |
| − | * [[OpenStack_health_tracker]]
| |
| − | | |
| − | === Status of Electorate ===
| |
| − | Drivers:
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | During the retrospective at the Rocky Forum we discussed the status of the TC electorate, and what is perceived as a low level of engagement. This needs a bit more research to compare recent elections so we can understand how things stand, and then we should talk about ways to improve the situation.
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
| |
| − | | |
| − | === Improving the help-wanted list ===
| |
| − | Drivers: Sean, Graham, Dims, and Julia
| |
| − | | |
| − | Board support: Allison Randal, Alan Clark, Prakash Ramchandran, Chris Price, and Johan Christenson
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | During the Board/TC/UC meeting at Vancouver, we came up with an idea on what we can put together a better way to ask platinum/gold and other companies in the eco system for help (crossing traditional job descriptions and volunteer/skill match websites)
| |
| − | | |
| − | References
| |
| − | * [https://etherpad.openstack.org/p/job-description-template Sample Job description template] | |
| − | | |
| − | === project infrastructure governance proposal ===
| |
| − | Drivers: dhellmann
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | corvus started a discussion about the relationship between the foundation projects and the infrastructure management team as that team shifts from being governed by the TC to being a foundation-wide project.
| |
| − | | |
| − | References
| |
| − | * http://lists.openstack.org/pipermail/openstack-dev/2018-May/130896.html
| |
| − | | |
| − | === finding help for the unified CLI team ===
| |
| − | Drivers:
| |
| − | | |
| − | Status: Needs a driver
| |
| − | | |
| − | During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.
| |
| − | | |
| − | === Update PTI around project doc translation and PDF ===
| |
| − | Drivers:
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | References:
| |
| − | * https://review.openstack.org/572559
| |
| − | | |
| − | === Project team guide: add "technical design tenets" chapter ===
| |
| − | | |
| − | Drivers: ttx
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | We need a place to explain things like base services (external services you can assume will be around and therefore you don't need to reinvent locally) and other basic design tenets.
| |
| − | | |
| − | References:
| |
| − | https://storyboard.openstack.org/#!/story/2002611
| |
| − | | |
| − | === Scheduling PTL & TC elections for Stein ===
| |
| − | | |
| − | Drivers: cmurphy
| |
| − | | |
| − | Status: Under discussion
| |
| − | | |
| − | References:
| |
| − | | |
| − | * https://governance.openstack.org/tc/reference/charter.html#election-for-ptl-seats
| |
| − | * https://governance.openstack.org/tc/reference/charter.html#election-for-tc-seats
| |
| − | * election setup: https://review.openstack.org/#/c/582109/
| |
| − | * schedule update: https://review.openstack.org/582831
| |
| − | | |
| − | === 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.
| |
| − | | |
| − | Status: New
| |
| − | | |
| − | References:
| |
| − | | |
| − | * https://review.openstack.org/#/c/589696/
| |
| − | | |
| − | == Tracking OpenStack team health ==
| |
| − | See [[OpenStack_health_tracker]] for liaison assignment and status updates.
| |
| − | | |
| − | | |
| − | == Recently completed things ==
| |
| − | | |
| − | === Organizational diversity tags ===
| |
| − | Drivers: ttx, mnaser
| |
| − | | |
| − | Status: Done
| |
| − | | |
| − | References
| |
| − | * [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]
| |
| − | * removing the tags: https://review.openstack.org/#/c/579870/
| |
| − | * team "fragility" stats script: https://review.openstack.org/#/c/579142/
| |
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.
