Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 4: Line 4:
  
 
=== Current proposals ===
 
=== Current proposals ===
''Status last updated: July 7, 2017''
+
''Status last updated: July 11, 2017''
  
 
'''Leadership'''
 
'''Leadership'''
Line 10: Line 10:
 
** 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]
 +
** Fix typo in vision document [https://review.openstack.org/482152]
 
** 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 still in progress, mostly on the most appropriate level of details.
 
** 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: Discussion in progress. New patchset likely needed.
 
** Status: Discussion in progress. New patchset likely needed.
* Remove remaining 'big tent' references [https://review.openstack.org/480500] (ttx)
 
** Status: Voting in progress
 
 
* ''Resurrect SWG''
 
* ''Resurrect SWG''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html''
 
** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html''
Line 38: Line 37:
 
* Declare plainly the current state of PostgreSQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm, cdent)
 
* Declare plainly the current state of PostgreSQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm, cdent)
 
** 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: Voting in progress
+
** Status: Voting in progress, just missing a few votes
  
  
Line 67: Line 66:
 
* Follow-ups
 
* Follow-ups
 
** Clean up boilerplate code in policy docs goal [https://review.openstack.org/475882]
 
** Clean up boilerplate code in policy docs goal [https://review.openstack.org/475882]
 +
** Remove unnecessary < and > from policy goal [https://review.openstack.org/481654]
  
  
Line 80: Line 80:
 
* ''How to deal with confusion around "hosted" projects (ttx)''
 
* ''How to deal with confusion around "hosted" projects (ttx)''
 
** ''Initial ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118368.html''
 
** ''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''
+
** ''Subsequent ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119043.html''
 
** ''Status: Brainstorming''
 
** ''Status: Brainstorming''
  

Revision as of 07:58, 11 July 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: July 11, 2017

Leadership


New project teams

  • Add Stackube project team [5]
    • 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 [6]
    • 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 [7]
    • Status: Initial discussion
  • Add Blazar project team


Simplification


Inclusion & Diversity

  • Decisions should be globally inclusive [9] (johnthetubaguy)
    • Status: Discussion in progress. Might be better expressed as a principle and a project-team-guide chapter
  • 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]
    • Remove unnecessary < and > from policy goal [18]


Other


Next Meeting

  • Date: July 11th, 20:00utc
  • Chair: ttx


Agenda

  • Final selection of Queens goals
  • TC 2019 vision next step
  • Open discussion


Apologies for Absence

  • tbd


Past meetings logs

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