Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

(Next steps in TC Vision / defining role of the TC)
 
(4 intermediate revisions by 2 users not shown)
Line 14: Line 14:
 
== Other Initiatives ==
 
== Other Initiatives ==
  
=== Correction to TC member election section of bylaws ===
+
=== Help most needed list evolution ===
Drivers: fungi, dhellmann
+
Drivers: ttx
 +
 
 +
Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html mailing-list]
 +
 
 +
Next step: Forum session
  
Status: On hold until the next Foundation vote
+
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.
  
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.
+
=== Facilitating cross-project work / Formalizing pop-up teams ===
 +
Drivers: ttx
  
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…"
+
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.
  
 
=== Technical Vision for OpenStack ===
 
=== Technical Vision for OpenStack ===
Drivers: zaneb, ttx, cdent
+
Drivers: zaneb, cdent
  
 
Status: Under dicussion
 
Status: Under dicussion
Line 35: Line 44:
 
* [https://review.openstack.org/592205 Document review]
 
* [https://review.openstack.org/592205 Document review]
  
=== tags indicating the upgrade support in deployment tools ===
+
=== Tags indicating the upgrade support in deployment tools ===
 
Drivers: ttx
 
Drivers: ttx
  
Line 45: Line 54:
 
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]
 
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]
  
=== Next steps in TC Vision / defining role of the TC ===
+
=== Do a better job at driving larger technical goals  ===
 
Drivers: ttx, TheJulia, cdent
 
Drivers: ttx, TheJulia, cdent
  
 
Status:
 
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.
+
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.
 
 
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.
+
Next step: Forum session
 
 
2018-09-09 - chair to raise this question with the TC after the election completes
 
 
 
References
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
* [http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000542.html discussion]
 
  
 
=== Clarifying Requirements for PTL Contact Details ===
 
=== Clarifying Requirements for PTL Contact Details ===

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