Technical Committee Tracker

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.

Status last updated: January 23rd, 2018

Rocky goals

Here are the currently-proposed options:

• Add Cold upgrades capabilities [1] (masayuki)
• Remove mox [2] (smcginnis, chandankumar)
• Ensure pagination links [3] (mordred)
• Storyboard Migration [4] (diablo_rojo)
• Enable mutable configuration [5] (gcb)

An evolution of the process for tracking goals was also proposed:

• update the goal process to use storyboard for tracking [6]
  • Status: Vote in progress, still missing a couple of votes

New teams

• Qinling: Function as a Service in OpenStack [7]
  • Status: Majority reached, to be approved on Friday if no new objection is posted.

Leadership

• Clarify testing for interop programs [8] (mugsie)
  • Status: Options still being discussed, no clear consensus yet
  • See cmurphy's write-up at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html

Other

• Allow public polling to choose release names [9]
  • Status: Majority reached, to be approved on Friday if no new objection is posted.
• Naming poll for S development cycle
  • Status: Not started, need above rule change and a volunteer first
• Update Python PTI for tests to be specific and explicit [10] (mtreinish)
  • Status: Majority reached, to be approved on Friday if no new objection is posted
• Support "Driver teams" [11] [12]
  • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper