Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m
Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: May 30, 2017''
+
''Status last updated: Jun 2, 2017''
  
 
'''Leadership'''
 
'''Leadership'''
Line 17: Line 17:
 
** 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
* Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/] (ttx, dims)
+
* Top 5 wanted list (ttx, dims)
** Status: Should propose a follow-up patch to frame the discussion
+
** Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/]
** Next step: ttx to post one example follow-up patch
+
** Add "Doc owners" to top-5 wanted list [https://review.openstack.org/469115]
* Etcd as a base service [https://review.openstack.org/467436] (dims)
+
** Status: Initial discussion on the patch
** Status: Majority reached on May 26. To be approved on Jun 1st
 
  
  
Line 31: Line 30:
 
** Status: Frozen while Gluon discusses further integration opportunities with Neutron
 
** 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 ?
 
** 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''
  
  
Line 39: Line 40:
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
 
** Status: No consensus yet, and energy is running low on pushing subsequent refinement patchsets
 
** Status: No consensus yet, and energy is running low on pushing subsequent refinement patchsets
** Next step: Might need a sync discussion in a meeting to lean one way or the other
+
** Next step: Sync discussion iat next week meeting
 
* ''Culling projects that are not going anywhere (ttx, ?)''
 
* ''Culling projects that are not going anywhere (ttx, ?)''
 
** ''Status: brainstorming''
 
** ''Status: brainstorming''
Line 45: Line 46:
  
 
'''Inclusion & Diversity'''
 
'''Inclusion & Diversity'''
* How to propose changes: do not mention meetings [https://review.openstack.org/467255] (ttx)
 
** Status: Majority reached on May 29. To be approved on Jun 1st
 
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
** Status: New revision needed
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it
 
** Next step: johnthetubaguy to update it
* Document voting process for `formal-vote` patches [https://review.openstack.org/463141] (flaper87)
 
** Status: 2/3 majority reached on May 29. To be approved on Jun 1st
 
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
 
** Status: New revision needed
 
** Status: New revision needed
Line 58: Line 55:
 
** Introduce office hours [https://review.openstack.org/#/c/467256/] (ttx)
 
** Introduce office hours [https://review.openstack.org/#/c/467256/] (ttx)
 
** Establish a #openstack-tc water cooler channel [https://review.openstack.org/#/c/467386/] (dims)
 
** Establish a #openstack-tc water cooler channel [https://review.openstack.org/#/c/467386/] (dims)
** Status: Voting in progress
+
** Status: Majority reached on May 30. To be approved on Jun 5
 
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
 
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
 
** ''Status: brainstorming''
 
** ''Status: brainstorming''
Line 64: Line 61:
  
 
'''Goals'''
 
'''Goals'''
* Add etherpad link with detailed steps to split-tempest-plugins goal [https://review.openstack.org/468972]
+
* Add etherpad link with detailed steps to split-tempest-plugins goal [https://review.openstack.org/468972]
** Status: Just further documentation for the split-tempest-plugins goal. Voting in progress.
+
** Status: Majority reached on Jun 1. To be approved on Jun 5.
* Queens goal: discovery alignment (two options):
+
* Discovery alignment (two options):
 
** Add Queens goal to add collection links [https://review.openstack.org/468436]
 
** Add Queens goal to add collection links [https://review.openstack.org/468436]
 
** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437]
 
** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437]
** Status: Needs a ML thread
+
** Status: Initial discussion
** Next step: mordred to raise a ML thread about those two options
+
* Policy and docs in code [https://review.openstack.org/469954]
 +
** Status: Initial discussion
 +
* ''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''
  
  
Line 79: Line 81:
 
** Status: Blocked until driver teams are a thing
 
** 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 step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue
* ''Policy on binary images publication (dhellmann)''
+
* Policy on binary images publication (dhellmann)
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html''
+
** Guidelines for managing releases of binary artifacts [https://review.openstack.org/469265]
** ''Status: to be proposed''
+
** Resolution regarding container images [https://review.openstack.org/469248]
 +
** Status: Initial discussion
  
  

Revision as of 09:29, 2 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 2, 2017

Leadership

  • Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Introduce assert:supports-api-interoperability tag [2] (mtreinish, sdague)
    • Status: Needs another patchset
    • Next step: mtreinish to address dhellmann's comments
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it next week-ish
  • Top 5 wanted list (ttx, dims)
    • Introduce Top 5 help wanted list [4]
    • Add "Doc owners" to top-5 wanted list [5]
    • Status: Initial discussion on the patch


New project teams

  • Add Stackube project team [6] (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 [7] (?)
    • 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

  • postgresql support in OpenStack -- two alternative solutions:
  • Culling projects that are not going anywhere (ttx, ?)
    • Status: brainstorming


Inclusion & Diversity

  • Decisions should be globally inclusive [10] (johnthetubaguy)
    • Status: New revision needed
    • Next step: johnthetubaguy to update it
  • Drop Technical Committee meetings [11] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it
  • Office hours -- two patches:
    • Introduce office hours [12] (ttx)
    • Establish a #openstack-tc water cooler channel [13] (dims)
    • Status: Majority reached on May 30. To be approved on Jun 5
  • Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
    • Status: brainstorming


Goals


Other

  • Support "Driver teams" [18] [19] [20] [21] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [22] (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)
    • Guidelines for managing releases of binary artifacts [23]
    • Resolution regarding container images [24]
    • Status: Initial discussion


Next Meeting

  • Date: June 6th
  • Chair: tbd


Agenda

  • Declare the current state of Postgresql in OpenStack
    • Declare plainly the current state of Posgresql in OpenStack [25]
    • Document lack of postgresql support [26]
  • Open discussion


Apologies for Absence

  • tbd


Past meetings logs

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