Jump to: navigation, search


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/ . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode. See the governance website for details on how to propose governance changes.

Current proposals

Status last updated: July 4, 2017


  • Technical Committee vision (johnthetubaguy, cdent, dtroyer)
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: Discussion in progress. New patchset likely needed.
  • Add "Glance Contributors " to top-5 wanted list [4] (flaper87)
    • Status: Majority reached on June 30, to be approved on July 6 unless last-minute objections are raised.
  • Resurrect SWG

New project teams

  • Add Stackube project team [5]
    • Status: Frozen until the project is set up as a hosted project and openly collaborates there for some time
    • Next step: Setting up openstack/stackube as an OpenStack-hosted project (dims to mentor them through the steps)
  • Add Gluon project team [6]
    • Status: Frozen while Gluon discusses further integration opportunities with Neutron
    • Next step: waiting a few months to see how the integration goes (ttx to mentor them through the steps)
  • Add Glare project team [7]
    • Status: Initial discussion
  • Add Blazar project team


Inclusion & Diversity

  • Decisions should be globally inclusive [9] (johnthetubaguy)
    • Status: Discussion in progress. Might be better expressed as a principle and a project-team-guide chapter
  • Drop Technical Committee meetings [10] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it
  • Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)

Queens Goals

  • Need for project-management by Goal champions to ensure smoother delivery, see thread at [11]
  • Goal selection
    • We'll probably only pick 2, currently leading the pack are:
      • Split Tempest plugins (already approved)
      • Policy and docs in code [12]
    • Other proposals
      • Discovery alignment (two options):
        • Add Queens goal to add collection links [13]
        • Add Queens Goal for full discovery alignment [14]
      • Migrate off paste [15]
        • This one is considered a bit vague, lacking a practical success story in one project
      • Continuing Python 3.5+ Support​ [16]
        • We should wait for Pike goal completion before "extending" this one
  • Follow-ups
    • Clean up boilerplate code in policy docs goal [17]


Next Meeting

  • Date: tbd
  • Chair: tbd


  • tbd
  • Open discussion

Apologies for Absence

  • tbd

Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc