Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

 
(184 intermediate revisions by 13 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/ .
 +
 
 +
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].
 +
 
 +
Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].
 +
 
 +
'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''
 +
 
 +
== Project team changes ==
 +
 
 +
== Documentation Changes ==
 +
 
 +
 
 +
== 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]
 +
 
 +
Next step: Forum session
 +
 
 +
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.
 +
 
 +
=== Facilitating cross-project work / Formalizing pop-up teams ===
 +
Drivers: ttx
 +
 
 +
Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002251.html mailing-list]
 +
 
 +
Next step: Forum session
 +
 
 +
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.
  
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/ .
+
=== Technical Vision for OpenStack ===
 +
Drivers: zaneb, 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]
  
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
+
=== Tags indicating the upgrade support in deployment tools ===
 +
Drivers: ttx
  
'''Status last updated: February 9th, 2018'''
+
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.
  
==== Rocky goals ====
+
References
 +
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]
  
The following set will be approved on Tuesday unless new objections are posted that changes the member votes:
+
=== Do a better job at driving larger technical goals  ===
* Enable toggling debug option at runtime [https://review.openstack.org/534605] (gcb)
+
Drivers: ttx, TheJulia, cdent
* Remove mox [https://review.openstack.org/532361] (smcginnis, chandankumar)
 
  
 +
Status:
 +
Documenting the role of the TC revealed the need for the TC to do a better job at painting larger technical goals for the OpenStack community, beyond release goals.
  
As a reminder, here were the other proposed options:
+
Next step: Forum session
* Add Cold upgrades capabilities [https://review.openstack.org/#/c/533544/] (masayuki)
 
* Ensure pagination links [https://review.openstack.org/532627] (mordred)
 
* Storyboard Migration [https://review.openstack.org/513875] (diablo_rojo)
 
  
 +
=== Clarifying Requirements for PTL Contact Details ===
  
Additionally, dhellmann proposed an evolution of the process for tracking goals:
+
Drivers:  
* update the goal process to use storyboard for tracking [https://review.openstack.org/534443]
 
** Status: Majority reached, to be approved on Tuesday unless new objections are posted
 
  
 +
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.
  
==== New teams ====
+
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
  
* Add PowerStackers project [https://review.openstack.org/540165]
+
Status: New
** Status: Under discussion
 
  
 +
References:
  
==== Leadership ====
+
* https://review.openstack.org/#/c/589696/ (abandoned)
 +
* https://review.openstack.org/#/c/590082/ (fills in missing nicks with "None supplied")
  
* Clarify testing for interop programs [https://review.openstack.org/521602] (mugsie)
+
== Tracking OpenStack team health ==
** Status: Options still being discussed
+
See [[OpenStack_health_tracker]] for liaison assignment and status updates.
** See cmurphy's write-up and following ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html
 
  
  
==== Other ====
+
== Recently completed things ==
* Dedicate Queens release to Shawn Pearce [https://review.openstack.org/541313]
 
** Status: Voting in progress
 
* Naming poll for S development cycle
 
** Status: pabelanger volunteered to drive it, waiting for release_naming.rst patches.
 
* 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 09:32, 8 March 2019

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. We hold office hours at various times during the week on the #openstack-tc IRC channel. Conversation starters for the office hours are here.

Other tasks can be found in the storyboard project.

Status last updated: 2019/03/08

Project team changes

Documentation Changes

Other Initiatives

Help most needed list evolution

Drivers: ttx

Status: under discussion on the mailing-list

Next step: Forum session

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.

Facilitating cross-project work / Formalizing pop-up teams

Drivers: ttx

Status: under discussion on the mailing-list

Next step: Forum session

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 Kubernetes working groups) would help.

Technical Vision for OpenStack

Drivers: zaneb, cdent

Status: Under dicussion

The initial 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

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

Do a better job at driving larger technical goals

Drivers: ttx, TheJulia, cdent

Status: Documenting the role of the TC revealed the need for the TC to do a better job at painting larger technical goals for the OpenStack community, beyond release goals.

Next step: Forum session

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:

Tracking OpenStack team health

See OpenStack_health_tracker for liaison assignment and status updates.


Recently completed things