Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: August 11th, 2017''
+
''Status last updated: August 15th, 2017''
 
 
'''Leadership'''
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: Majority reached, to be approved on Aug 15th unless new objections are raised
 
 
 
  
 
'''New project teams'''
 
'''New project teams'''
Line 29: Line 24:
 
** Status: Discussion in progress on latest revision, another patchset likely needed
 
** Status: Discussion in progress on latest revision, another patchset likely needed
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
** Status: Needs a new patchset to incorporate feedback (or abandon since it's been implemented already)
+
** Status: Discussion in progress on latest patchset
** Next step: flaper87 to update this proposal
 
 
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
 
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
** ''Status: ML created, "meta" SIG set up, initial discussions being held''
+
** ''Status: ML created, "meta" SIG set up, first workgroups to be migrated''
** ''Next step: Meta SIG to reach out to existing WG to migrate them over''
+
** ''Next step: Migrate volunteer WGs''
  
  
 
'''Other'''
 
'''Other'''
 
* Amend leaderless program resolution timeframe [https://review.openstack.org/492578] (persia)
 
* Amend leaderless program resolution timeframe [https://review.openstack.org/492578] (persia)
** Status: Voting in progress
+
** Status: Voting in progress, still missing one vote
 
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87)
 
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87)
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
** Status: New patchset posted, discussion in progress
+
** Status: Discussion in progress on latest patchset
 
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
 
* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839]
 
** Status: Frozen while thingee works on driver discoverability
 
** Status: Frozen while thingee works on driver discoverability

Revision as of 09:07, 15 August 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: August 15th, 2017

New project teams

  • Add Stackube project team [1]
    • 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 [2]
    • Status: Frozen while Gluon discusses further integration opportunities with Neutron
    • Next step: waiting a few months to see how the integration goes (ttx to mentor them through the steps)
  • Add Glare project team [3]
  • Add Blazar project team [4]
    • Status: Discussion in progress, decision likely to be made after Pike releases


Inclusion & Diversity

  • Decisions should be globally inclusive [5] (johnthetubaguy)
    • Status: Discussion in progress on latest revision, another patchset likely needed
  • Drop Technical Committee meetings [6] (flaper87)
    • Status: Discussion in progress on latest patchset
  • Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)


Other


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