Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 84: Line 84:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: June 20 (to be confirmed)
+
* Date: June 20, 20:00 on #openstack-meeting
* Chair: tbd
+
* Chair: ttx (or thingee if ttx is late)
  
  
Line 96: Line 96:
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
  
* tbd
+
* smcginnis, dims are traveling and might have a hard time joining
 +
* ttx might be late joining
  
  

Revision as of 09:39, 19 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 16, 2017

Leadership

  • Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • 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: Voting in progress
    • Add "Doc owners" to top-5 wanted list [6]
      • Status: Voting in progress
    • Add "Glance Contributors " to top-5 wanted list [7]
      • Initial discussion


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


Simplification


Inclusion & Diversity

  • Decisions should be globally inclusive [12] (johnthetubaguy)
    • Status: Open discussion
  • Drop Technical Committee meetings [13] (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


Other

  • Support "Driver teams" [17] [18] [19] [20] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [21] (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 [22] (dhellmann)
    • Status: Voting in progress
  • Remove "meritocracy" from the opens [23]
    • Status: Open discussion


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