Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 09:40, 19 May 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: May 17, 2017

Leadership

• Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
  • Status: Feedback was collected on draft review, ML and anonymous survey
  • Next step: feedback needs to be distilled into actionable points (and split between cosmetic and significant changes).
• Introduce assert:supports-api-compatibility tag [2] (mtreinish, sdague)
  • Status: Dependency was approved. New revision needed.
  • Next step: sdague to follow up with mtreinish to see if he will push it to the end
• Add tag assert:never-breaks-compat [3] (mordred)
  • Status: New revision needed
  • Next step: ttx to follow up with mordred to see if he will push it to the end
• Describe what upstream support means [4] (johnthetubaguy)
  • Status: New revision needed
  • Next step: johnthetubaguy to update it next week-ish
• Publish official "help wanted" list (ttx, dims)
  • Status: to be proposed

New project teams

• Add Stackube project team [5] (dims, ttx)
  • Status: Under discussion in the review. Needs to be set up as a hosted project before a final decision can be made.
• Add Gluon project team [6] (?)
  • Status: Under discussion in the review. Some answers missing. Needs a sponsor to help it through.

Simplification

• postgresql support in OpenStack -- two alternative solutions:
  • Declare plainly the current state of Posgresql in OpenStack [7] (sdague)
  • Document lack of postgresql support [8] (cdent)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
  • Status: Discussion / refining exact wording (no consensus yet)
• Culling projects that are not going anywhere (ttx, ?)
  • Status: brainstorming

Inclusion & Diversity

• Decisions should be globally inclusive [9] (johnthetubaguy)
  • Status: New revision needed
  • Next step: johnthetubaguy to update it
• Stop requiring public IRC meetings [10] (johnthetubaguy)
  • Status: Voting in progress. Could use being separated from parent change
• Document voting process for `formal-vote` patches [11] (flaper87)
  • Status: Discussion still in progress, probably needs another patchset
• Drop Technical Committee meetings [12] (flaper87)
  • Status: New revision needed
  • Next step: flaper87 to update it
• Setting up TC discussion channel and defining office hours (dims, ttx)
  • Status: to be proposed
• Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
  • Status: brainstorming

Queens goals

• Add Queens goal split out tempest plugins [13] (mtreinish)
  • Status: New patchset posted on May 17. Voting in progress.

Other

• Fix comment about design summits [14] (jhesketh, ttx)
  • Status: New patchset posted on May 18. Voting in progress
• Support "Driver teams" [15] [16] [17] [18] (dhellmann)
  • Status: Frozen while thingee works on driver discoverability
• networking-cisco project team addition [19] (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)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html
  • Status: to be proposed

Next Meeting

• Date: tbd
• Chair: tbd

Agenda

• tbd

Apologies for Absence

• tbd

Past meetings logs

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