Jump to: navigation, search

Technical Committee Tracker

Revision as of 10:54, 7 February 2019 by ThierryCarrez (talk | contribs)

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/02/07

Project team changes

Documentation Changes

Other Initiatives

Help most needed list evolution

Drivers: ttx

Status: under discussion on the 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 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 Kubernetes working groups) would help.

Correction to TC member election section of bylaws

Drivers: fungi, dhellmann

Status: Approved during 2018 board election: http://lists.openstack.org/pipermail/foundation/2019-January/002670.html

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 3.b.i reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"

Technical Vision for OpenStack

Drivers: zaneb, ttx, 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.


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.


Next steps in TC Vision / defining role of the TC

Drivers: ttx, TheJulia, cdent

Status: Document created as 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.


Clarifying Requirements for PTL Contact Details


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


Tracking OpenStack team health

See OpenStack_health_tracker for liaison assignment and status updates.

Recently completed things