Jump to: navigation, search

Technical Committee Tracker

Revision as of 11:50, 5 December 2017 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.

Status last updated: December 5th, 2017


Leadership

  • Add "goal champions" as a top-5 help wanted area [1] (dhellmann)
    • Status: Voting in progress, still missing a couple of votes
  • Clarify testing for interop programs [2] (mugsie)
    • Status: Options still being discussed, no clear consensus yet
  • Rename 'top-5 help wanted' to 'top help wanted' [3] (ttx)
    • Status: New patchset proposed, ready for review


Rocky goals

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


Inclusion & Diversity


Other

  • Rename shade team to OpenStackSDK [5]
    • Status: Majority reached on previous patchset, will be approved on Friday unless new objections are posted
  • Tags are applied to deliverables, or teams [6]
    • Status: Majority reached, will be approved on Friday unless new objections are posted
  • remove docs:follows-policy tag [7]
    • Status: Voting in progress
  • Stop linking to documentation from governance [8] (dhellmann)
    • Status: Majority reached, will be approved on Friday unless new objections are posted
  • Officialize election organization working group [9] (ttx)
    • Status: Majority reached, will be approved on Friday unless new objections are posted
  • Update Python PTI for tests to be specific and explicit [10] (mtreinish)
    • Status: Comments call for opening the discussion in a ML thread
  • Support "Driver teams" [11] [12]
    • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper