Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 20: Line 20:
 
** Status: New revision needed
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it next week-ish
 
** Next step: johnthetubaguy to update it next week-ish
 +
* ''Publish official "help wanted" list (ttx)''
 +
** ''Status: to be proposed''
  
  
Line 46: Line 48:
 
** Status: New revision needed
 
** Status: New revision needed
 
** Next step: flaper87 to update it
 
** 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''
  
  

Revision as of 10:55, 17 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)
  • 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)
    • Status: to be proposed


New project teams

  • Add Stackube project team [5] (dims, ttx)
    • Status: Under discussion in the review.
  • Add Gluon project team [6] (?)
    • Status: Under discussion in the review. Needs a sponsor to help it through.


Simplification


Inclusion & Diversity

  • Decisions should be globally inclusive [8] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it
  • Stop requiring public IRC meetings [9] (johnthetubaguy)
    • Status: Voting in progress. Could use being separated from parent change
  • Document voting process for `formal-vote` patches [10] (flaper87)
    • Status: Majority support reached on May 16, about to be approved
  • Drop Technical Committee meetings [11] (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 [12] (mtreinish)
    • Status: Majority support reached on May 16, about to be approved


Other

  • Fix comment about design summits [13] (jhesketh, ttx)
    • Status: New revision needed
    • Next step: ttx to follow up with jhesketh to see if he will push it to the end, and to adopt it if not
  • Support "Driver teams" [14] [15] [16] [17] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [18] (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


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