Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 08:14, 20 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 20, 2017

Leadership

• Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Initial draft for public feedback [1]
  • New version integrating feedback and editing for style [2]
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
  • Status: New draft produced integrating some of the feedback. Discussion in progress on that version
• Introduce assert:supports-api-interoperability tag [3] (mtreinish, cdent)
  • Status: Voting in progress
• Describe what upstream support means [4] (johnthetubaguy)
  • Status: New revision needed
  • Next step: johnthetubaguy to update it
• Top 5 wanted list (ttx, dims)
  • Introduce Top 5 help wanted list [5]
    • Status: Majority reached on Jun 19, to be approved Jun 22
  • Add "Doc owners" to top-5 wanted list [6]
    • Status: Majority reached on Jun 20, to be approved Jun 23
  • Add "Glance Contributors " to top-5 wanted list [7]
    • Status: Voting in progress

New project teams

• Add Stackube project team [8] (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 [9] (?)
  • 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
  • Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/117844.html

Simplification

• Declare plainly the current state of PostgreSQL in OpenStack [10] (sdague, dirkm)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
  • Status: Still under discussion. Could use a minor formatting revision
• Culling Fuel (ttx)
  • Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118367.html

Inclusion & Diversity

• Decisions should be globally inclusive [11] (johnthetubaguy)
  • Status: Open discussion
• Drop Technical Committee meetings [12] (flaper87)
  • Status: New revision needed
  • Next step: flaper87 to update it
• Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
  • Status: brainstorming

Goals

• Discovery alignment (two options):
  • Add Queens goal to add collection links [13]
  • Add Queens Goal for full discovery alignment [14]
  • Status: Open discussion
• Policy and docs in code [15]
  • Status: This goal seems to be well accepted. The question is now more if that particular goal should be selected for Queens (rather than others)
• Migrate off paste
  • Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html
• Continuing Python 3.5+ Support​
  • Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html

Other

• Support "Driver teams" [16] [17] [18] [19] (dhellmann)
  • Status: Frozen while thingee works on driver discoverability
• networking-cisco project team addition [20] (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
• Guidelines for managing releases of binary artifacts [21] (dhellmann)
  • Status: Voting in progress, still missing a couple votes
• Remove "meritocracy" from the opens [22]
  • Status: Voting in progress

Next Meeting

• Date: June 20, 20:00 on #openstack-meeting
• Chair: ttx (or thingee if ttx is late)

Agenda

• Review proposed Pike goals and come up with a proposed selection
• Open discussion

Apologies for Absence

• smcginnis, dims are traveling and might have a hard time joining
• ttx might be late joining

Past meetings logs

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