Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 89: Line 89:
=== Next Meeting ===
=== Next Meeting ===
* Date: June 6th
* Date: June 6th, 20:00UTC on #openstack-meeting
* Chair: tbd
* Chair: smcginnis
Line 103: Line 103:
==== Apologies for Absence ====
==== Apologies for Absence ====
* tbd
* ttx might not be able to join, depending on where he'll be at meeting time

Revision as of 16:21, 2 June 2017

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: Jun 2, 2017


  • Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Introduce assert:supports-api-interoperability tag [2] (mtreinish, sdague)
    • Status: Needs another patchset
    • Next step: mtreinish to address dhellmann's comments
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it next week-ish
  • Top 5 wanted list (ttx, dims)
    • Introduce Top 5 help wanted list [4]
    • Add "Doc owners" to top-5 wanted list [5]
    • Status: Initial discussion on the patch

New project teams

  • Add Stackube project team [6] (dims, ttx)
    • 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 [7] (?)
    • Status: Frozen while Gluon discusses further integration opportunities with Neutron
    • Next step: This prospective team needs a TC sponsor/mentor to help them through the steps. Any volunteer ?
  • Add Blazar project team


  • postgresql support in OpenStack -- two alternative solutions:
  • Culling projects that are not going anywhere (ttx, ?)
    • Status: brainstorming

Inclusion & Diversity

  • Decisions should be globally inclusive [10] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it
  • Drop Technical Committee meetings [11] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it
  • Office hours -- two patches:
    • Introduce office hours [12] (ttx)
    • Establish a #openstack-tc water cooler channel [13] (dims)
    • Status: Majority reached on May 30. To be approved on Jun 5
  • Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
    • Status: brainstorming



  • Support "Driver teams" [18] [19] [20] [21] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [22] (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
  • Policy on binary images publication (dhellmann)
    • Guidelines for managing releases of binary artifacts [23]
    • Resolution regarding container images [24]
    • Status: Initial discussion

Next Meeting

  • Date: June 6th, 20:00UTC on #openstack-meeting
  • Chair: smcginnis


  • Declare the current state of Postgresql in OpenStack
    • Declare plainly the current state of Posgresql in OpenStack [25]
    • Document lack of postgresql support [26]
  • Open discussion

Apologies for Absence

  • ttx might not be able to join, depending on where he'll be at meeting time

Past meetings logs

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