Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: Jun 23, 2017''
+
''Status last updated: Jun 27, 2017''
  
 
'''Leadership'''
 
'''Leadership'''
 
* Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
 
* Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
 
** Initial draft for public feedback [https://review.openstack.org/453262]  
 
** Initial draft for public feedback [https://review.openstack.org/453262]  
** New version integrating feedback and editing for style [https://review.openstack.org/473620]
+
** Subsequent patch integrating feedback and editing for style [https://review.openstack.org/473620]
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
 
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
** Status: New draft produced integrating some of the feedback. Discussion in progress on that version
+
** Status: Discussion in progress
* 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)
 
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
 
** Status: New patchset posted. Discussion in progress on that version
 
** Status: New patchset posted. Discussion in progress on that version
Line 29: Line 27:
 
* 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: ttx volunteered to accompany them, will reach out to get updated status
+
** Next step: waiting a few months to see how the integration goes (ttx to mentor them through the steps)
 
* ''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''
 +
* ''Add Glare project team''
 +
** ''Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118911.html''
  
  
Line 40: Line 40:
 
** Next step: sdague or dirkm to post formatting revision to address latest cdent's comments
 
** Next step: sdague or dirkm to post formatting revision to address latest cdent's comments
 
* Move Fuel from official to unofficial (hosted) [https://review.openstack.org/475721] (ttx)
 
* Move Fuel from official to unofficial (hosted) [https://review.openstack.org/475721] (ttx)
** Status: Voting in progress
+
** Status: Majority reached. To be approved on May 29 unless someone objects
  
  
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
* Remove "meritocracy" from the opens [https://review.openstack.org/473510]
 
** Status: Majority reached on Jun 21. Will be approved on Jun 26 unless there are last-minute objections.
 
  
  

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

Leadership

  • Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: New patchset posted. Discussion in progress on that version
  • Add "Glance Contributors " to top-5 wanted list [4] (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


Simplification

  • Declare plainly the current state of PostgreSQL in OpenStack [7] (sdague, dirkm)
  • Move Fuel from official to unofficial (hosted) [8] (ttx)
    • Status: Majority reached. To be approved on May 29 unless someone objects


Inclusion & Diversity

  • Decisions should be globally inclusive [9] (johnthetubaguy)
    • Status: New patchset posted. Open discussion
  • Drop Technical Committee meetings [10] (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 [11]
  • Goal selection
    • We'll probably only pick 2, currently leading the pack are:
      • Split Tempest plugins (already approved)
      • Policy and docs in code [12]
    • Other proposals
      • Discovery alignment (two options):
        • Add Queens goal to add collection links [13]
        • Add Queens Goal for full discovery alignment [14]
      • Migrate off paste [15]
        • This one is considered a bit vague, lacking a practical success story in one project
      • Continuing Python 3.5+ Support​ [16]
        • We should wait for Pike goal completion before "extending" this one
  • Follow-ups
    • Clean up boilerplate code in policy docs goal [17]


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


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