Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: Jun 20, 2017''
+
''Status last updated: Jun 23, 2017''
  
 
'''Leadership'''
 
'''Leadership'''
Line 13: Line 13:
 
** Status: New draft produced integrating some of the feedback. Discussion in progress on that version
 
** Status: New draft produced integrating some of the feedback. Discussion in progress on that version
 
* Introduce assert:supports-api-interoperability tag [https://review.openstack.org/418010] (mtreinish, cdent)
 
* Introduce assert:supports-api-interoperability tag [https://review.openstack.org/418010] (mtreinish, cdent)
 +
** Status: Majority reached on June 21. Will be approved on Jun 26 unless objections are raised.
 +
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 +
** Status: New patchset posted. Discussion in progress on that version
 +
* Add "Glance Contributors " to top-5 wanted list [https://review.openstack.org/474604] (flaper87)
 
** Status: Voting in progress
 
** Status: Voting in progress
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New revision needed
 
** Next step: johnthetubaguy to update it
 
* Top 5 wanted list (ttx, dims)
 
** Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/]
 
*** Status: Majority reached on Jun 19, to be approved Jun 22
 
** Add "Doc owners" to top-5 wanted list [https://review.openstack.org/469115]
 
*** Status: Majority reached on Jun 20, to be approved Jun 23
 
** Add "Glance Contributors " to top-5 wanted list [https://review.openstack.org/474604]
 
*** Status: Voting in progress
 
 
* ''Resurrect SWG''
 
* ''Resurrect SWG''
 
** ''Status: In a meetingless group, someone needs to actively lead the group and post updates''
 
** ''Status: In a meetingless group, someone needs to actively lead the group and post updates''
Line 30: Line 24:
  
 
'''New project teams'''
 
'''New project teams'''
* Add Stackube project team [https://review.openstack.org/462460] (dims, ttx)
+
* Add Stackube project team [https://review.openstack.org/462460]
 
** Status: Frozen until the project is set up as a hosted project and openly collaborates there for some time
 
** 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)
 
** Next step: Setting up openstack/stackube as an OpenStack-hosted project (dims to mentor them through the steps)
* Add Gluon project team [https://review.openstack.org/463069] (?)
+
* Add Gluon project team [https://review.openstack.org/463069]
 
** 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: ttx volunteered to accompany them, will reach out to get updated status
 
* ''Add Blazar project team''
 
* ''Add Blazar project team''
 
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/117844.html''
 
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/117844.html''
Line 43: Line 37:
 
* Declare plainly the current state of PostgreSQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm)
 
* Declare plainly the current state of PostgreSQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm)
 
** 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: Still under discussion. Could use a minor formatting revision
+
** Status: Open discussion.
* ''Culling Fuel (ttx)''
+
** Next step: sdague or dirkm to post formatting revision to address latest cdent's comments
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118367.html''
+
* Move Fuel from official to unofficial (hosted) [https://review.openstack.org/475721] (ttx)
 +
** Status: Voting in progress
  
  
 
'''Inclusion & Diversity'''
 
'''Inclusion & Diversity'''
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
 
* Decisions should be globally inclusive [https://review.openstack.org/460946] (johnthetubaguy)
** Status: Open discussion
+
** Status: New patchset posted. Open discussion
 
* 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
 
** Next step: flaper87 to update it
 
** Next step: flaper87 to update it
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)''
+
* ''Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)''
** ''Status: brainstorming''
+
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html''
  
  
'''Goals'''
+
'''Queens Goals'''
* Discovery alignment (two options):
+
* Need for project-management by Goal champions to ensure smoother delivery, see thread at [http://lists.openstack.org/pipermail/openstack-dev/2017-June/118808.html]
** Add Queens goal to add collection links [https://review.openstack.org/468436]
+
* Goal selection
** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437]
+
** We'll probably only pick 2, currently leading the pack are:
** Status: Open discussion
+
*** Split Tempest plugins (already approved)
* Policy and docs in code [https://review.openstack.org/469954]
+
*** Policy and docs in code [https://review.openstack.org/469954]
** Status: This goal seems to be well accepted. The question is now more if that particular goal should be selected for Queens (rather than others)
+
** Other proposals
* ''Migrate off paste''
+
*** Discovery alignment (two options):
** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html''
+
**** Add Queens goal to add collection links [https://review.openstack.org/468436]
* ''Continuing Python 3.5+ Support​''
+
**** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437]
** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html''
+
*** Migrate off paste [http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html]
 +
**** This one is considered a bit vague, lacking a practical success story in one project
 +
*** Continuing Python 3.5+ Support​ [http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html]
 +
**** We should wait for Pike goal completion before "extending" this one
 +
* Follow-ups
 +
** Clean up boilerplate code in policy docs goal [https://review.openstack.org/475882]
  
  
Line 77: Line 77:
 
** 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
* Guidelines for managing releases of binary artifacts [https://review.openstack.org/469265] (dhellmann)
 
** Status: Voting in progress, still missing a couple votes
 
 
* Remove "meritocracy" from the opens [https://review.openstack.org/473510]
 
* Remove "meritocracy" from the opens [https://review.openstack.org/473510]
** Status: Voting in progress
+
** Status: Majority reached on Jun 21. Will be approved on Jun 26 unless there are last-minute objections.
  
  

Revision as of 08:30, 23 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 23, 2017

Leadership

  • Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Introduce assert:supports-api-interoperability tag [3] (mtreinish, cdent)
    • Status: Majority reached on June 21. Will be approved on Jun 26 unless objections are raised.
  • Describe what upstream support means [4] (johnthetubaguy)
    • Status: New patchset posted. Discussion in progress on that version
  • Add "Glance Contributors " to top-5 wanted list [5] (flaper87)
    • Status: Voting in progress
  • Resurrect SWG
    • Status: In a meetingless group, someone needs to actively lead the group and post updates
    • Next step: johnthetubaguy to resurrect the group, set up reporting and grow new members / leaders from there


New project teams

  • Add Stackube project team [6]
    • 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: ttx volunteered to accompany them, will reach out to get updated status
  • Add Blazar project team


Simplification


Inclusion & Diversity

  • Decisions should be globally inclusive [10] (johnthetubaguy)
    • Status: New patchset posted. Open discussion
  • Drop Technical Committee meetings [11] (flaper87)
    • Status: New revision needed
    • Next step: flaper87 to update it
  • Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)


Queens Goals

  • Need for project-management by Goal champions to ensure smoother delivery, see thread at [12]
  • Goal selection
    • We'll probably only pick 2, currently leading the pack are:
      • Split Tempest plugins (already approved)
      • Policy and docs in code [13]
    • Other proposals
      • Discovery alignment (two options):
        • Add Queens goal to add collection links [14]
        • Add Queens Goal for full discovery alignment [15]
      • Migrate off paste [16]
        • This one is considered a bit vague, lacking a practical success story in one project
      • Continuing Python 3.5+ Support​ [17]
        • We should wait for Pike goal completion before "extending" this one
  • Follow-ups
    • Clean up boilerplate code in policy docs goal [18]


Other

  • Support "Driver teams" [19] [20] [21] [22] (dhellmann)
    • Status: Frozen while thingee works on driver discoverability
  • networking-cisco project team addition [23] (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
  • Remove "meritocracy" from the opens [24]
    • Status: Majority reached on Jun 21. Will be approved on Jun 26 unless there are last-minute objections.


Next Meeting

  • Date: tbd
  • Chair: tbd


Agenda

  • tbd
  • Open discussion


Apologies for Absence

  • tbd


Past meetings logs

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