Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: Jun 27, 2017''
+
''Status last updated: Jun 30, 2017''
  
 
'''Leadership'''
 
'''Leadership'''
* Technical Committee vision (gothicmindfood, johnthetubaguy, cdent, dtroyer)
+
* Technical Committee vision (johnthetubaguy, cdent, dtroyer)
 
** Initial draft for public feedback [https://review.openstack.org/453262]  
 
** Initial draft for public feedback [https://review.openstack.org/453262]  
 
** Subsequent patch 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: Discussion in progress
+
** Status: Discussion still in progress, mostly on the most appropriate level of details.
 
* 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: Discussion in progress. New patchset likely needed.
 
* Add "Glance Contributors " to top-5 wanted list [https://review.openstack.org/474604] (flaper87)
 
* Add "Glance Contributors " to top-5 wanted list [https://review.openstack.org/474604] (flaper87)
** Status: Voting in progress
+
** Status: Voting in progress, still missing a couple of votes
 
* ''Resurrect SWG''
 
* ''Resurrect SWG''
 +
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html''
 
** ''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''
 
** ''Next step: johnthetubaguy to resurrect the group, set up reporting and grow new members / leaders from there''
 
** ''Next step: johnthetubaguy to resurrect the group, set up reporting and grow new members / leaders from there''
Line 37: Line 38:
 
* 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: Open discussion.
+
** Status: Discussion in progress. New patchset likely needed.
 
** 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)
 
** Status: Majority reached. To be approved on May 29 unless someone objects
 
  
  
 
'''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: New patchset posted. Open discussion
+
** Status: Discussion in progress. Might be better expressed as a principle and a project-team-guide chapter
 
* 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 77: Line 76:
 
** 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
 +
* ''Allow teams to use their channel for meetings (flaper87)''
 +
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html''
 +
** ''Status: Brainstorming''
 +
* ''How to deal with confusion around "hosted" projects (ttx)''
 +
** ''Initial ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118368.html''
 +
** ''Subsequent ML thread'': http://lists.openstack.org/pipermail/openstack-dev/2017-June/119043.html''
 +
** ''Status: Brainstorming''
  
  

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

Leadership

  • Technical Committee vision (johnthetubaguy, cdent, dtroyer)
  • Describe what upstream support means [3] (johnthetubaguy)
    • Status: Discussion in progress. New patchset likely needed.
  • Add "Glance Contributors " to top-5 wanted list [4] (flaper87)
    • Status: Voting in progress, still missing a couple of votes
  • Resurrect SWG


New project teams


Simplification


Inclusion & Diversity

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


Other


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