Difference between revisions of "Meetings/TechnicalCommittee"
< Meetings
| Line 4: | Line 4: | ||
=== Current proposals === | === Current proposals === | ||
| − | ''Status last updated: August | + | ''Status last updated: August 4th, 2017'' |
'''Leadership''' | '''Leadership''' | ||
* Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy) | * Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy) | ||
| − | ** Status: Voting in progress | + | ** Status: Voting in progress, still missing a couple of votes |
| Line 27: | Line 27: | ||
'''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: Discussion in progress on latest revision | + | ** Status: Discussion in progress on latest revision, another patchset likely needed |
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87) | * Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87) | ||
** Status: Needs a new patchset to incorporate feedback (or abandon since it's been implemented already) | ** Status: Needs a new patchset to incorporate feedback (or abandon since it's been implemented already) | ||
| Line 40: | Line 40: | ||
* Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87) | * Allow teams to use their channel for meetings [https://review.openstack.org/485117] (flaper87) | ||
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html | ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html | ||
| − | ** Status: Open discussion | + | ** Status: Open discussion, some revisions expected |
| − | * Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839] | + | * Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839] |
** Status: Frozen while thingee works on driver discoverability | ** Status: Frozen while thingee works on driver discoverability | ||
* networking-cisco project team addition [https://review.openstack.org/363709] (thingee) | * networking-cisco project team addition [https://review.openstack.org/363709] (thingee) | ||
Revision as of 08:53, 4 August 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: August 4th, 2017
Leadership
- Describe what upstream support means [1] (johnthetubaguy)
- Status: Voting in progress, still missing a couple of votes
New project teams
- Add Stackube project team [2]
- 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 [3]
- 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 [4]
- Status: Discussion in progress, decision likely to be made after Pike releases
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
- Add Blazar project team [5]
- Status: Discussion in progress, decision likely to be made after Pike releases
Inclusion & Diversity
- Decisions should be globally inclusive [6] (johnthetubaguy)
- Status: Discussion in progress on latest revision, another patchset likely needed
- Drop Technical Committee meetings [7] (flaper87)
- Status: Needs a new patchset to incorporate feedback (or abandon since it's been implemented already)
- Next step: flaper87 to update this proposal
- Replace UC or TC-side "workgroups" by neutral "SIGs" to encourage wide participation (mrhillsman, ttx)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html
- Status: ML created, "meta" SIG set up, initial discussions being held
- Next step: Meta SIG to reach out to existing WG to migrate them over
Other
- Allow teams to use their channel for meetings [8] (flaper87)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
- Status: Open discussion, some revisions expected
- Support "Driver teams" [9] [10]
- Status: Frozen while thingee works on driver discoverability
- networking-cisco project team addition [11] (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
- 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
Apologies for Absence
- tbd
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
