Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

Line 35: Line 35:
 
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
 
* 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
 
** Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper
 +
* Naming poll for S development cycle
 +
** mordred suggests having our election team manage the poll
 +
** we have outgrown the CIVS service we use for elections (at least for sending to every foundation member) so he proposes just running a public poll

Revision as of 22:06, 8 January 2018


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 5th, 2018


Leadership

  • Clarify testing for interop programs [1] (mugsie)
    • Status: Options still being discussed, no clear consensus yet


Rocky goals

  • Rocky goal: Storyboard Migration [2] (diablo_rojo)
    • Status: Waiting for more goals to be posted before we make the selection


Inclusion & Diversity


Other

  • Upgrade assertion tags only apply to services [3]
    • Status: Vote in progress
  • Update Python PTI for tests to be specific and explicit [4] (mtreinish)
    • Status: Comments call for opening the discussion in a ML thread
  • Support "Driver teams" [5] [6]
    • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper
  • Naming poll for S development cycle
    • mordred suggests having our election team manage the poll
    • we have outgrown the CIVS service we use for elections (at least for sending to every foundation member) so he proposes just running a public poll