Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

 
(208 intermediate revisions by 14 users not shown)
Line 1: Line 1:
__NOTOC__
+
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 the [https://governance.openstack.org/tc/#meeting  weekly meeting].
  
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/ .
+
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.
  
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
+
* [https://etherpad.opendev.org/p/tc-2023.1-tracker 2023.1 Release Cycle Tracker]
 
+
* [https://etherpad.opendev.org/p/tc-zed-tracker Zed Release Cycle Tracker]
'''Status last updated: December 15th, 2017'''
+
* [https://etherpad.opendev.org/p/tc-yoga-tracker  Yoga Release Cycle Tracker]
 
+
* [https://etherpad.opendev.org/p/tc-xena-tracker  Xena Release Cycle Tracker]
 
 
==== Leadership ====
 
 
 
* Clarify testing for interop programs [https://review.openstack.org/521602] (mugsie)
 
** Status: Options still being discussed, no clear consensus yet
 
 
 
 
 
==== Rocky goals ====
 
 
 
* Rocky goal: Storyboard Migration [https://review.openstack.org/513875] (diablo_rojo)
 
** Status: Waiting for more goals to be posted before we make the selection
 
 
 
 
 
==== Inclusion & Diversity ====
 
 
 
* Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html
 
** Status: New SIGs are being created
 
** Next step: Set up SIG governance website
 
 
 
 
 
==== Other ====
 
* Upgrade assertion tags only apply to services [https://review.openstack.org/528745]
 
** Status: Open discussion
 
* Retire Packaging Deb project repos [https://review.openstack.org/524732]
 
** Status: Majority reached, to be approved on Friday unless new objections are posted.
 
* Update Python PTI for tests to be specific and explicit [https://review.openstack.org/519751] (mtreinish)
 
** Status: Comments call for opening the discussion in a ML thread
 
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
 
** Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper
 

Latest revision as of 19:43, 16 November 2022

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/. We hold the weekly meeting.

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.