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: September 29th, 2017

Leadership

• Add Designate to the top 5 help wanted. [1] (mugsie)
  • Status: Voting in progress
• Adjustments to Infra contributors top-5 entry [2] (fungi)
  • Status: Voting in progress

New project teams

• Add Glare project team [3]
  • Status: Open discussion, likely to be delayed
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
• Add Stackube project team [4]
  • Status: Voting in progress
• Masakari - Instances High Availability Service [5]
  • Status: Voting in progress
• Mogan - Bare Metal Compute Service [6]
  • Status: Open discussion

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: Proper promotion of created SIGs on events, documentation and websites

Other

• Removing unused upgrade tags [7] [8] (smcginnis)
  • Status: Voting in progress, one of them might be kept around as some projects could already assert it
• Be explicit about supported database versions [9] (mordred)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html
  • Status: Open discussion, needs another patchset
• Support "Driver teams" [10] [11]
  • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper
• networking-cisco project team addition [12] (thingee)
  • Status: Blocked until driver teams are a thing
  • Next step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue