Meetings/TechnicalCommittee

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)
  • Initial draft for public feedback [1]
  • Subsequent patch integrating feedback and editing for style [2]
  • 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.
• 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
  • 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
  • Next step: johnthetubaguy to resurrect the group, set up reporting and grow new members / leaders from there

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 Blazar project team
  • 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

Simplification

• Declare plainly the current state of PostgreSQL in OpenStack [7] (sdague, dirkm)
  • ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
  • Status: Discussion in progress. New patchset likely needed.
  • Next step: sdague or dirkm to post formatting revision to address latest cdent's comments

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)
  • Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html

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

• Support "Driver teams" [17] [18] [19] [20] (dhellmann)
  • Status: Frozen while thingee works on driver discoverability
• networking-cisco project team addition [21] (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
• 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

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