Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 02:39, 21 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 21, 2017

Leadership

Describe what upstream support means [1] (johnthetubaguy)
- Status: Discussion in progress on latest revision.
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 [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

Simplification

Declare plainly the current state of PostgreSQL in OpenStack [6] (sdague, dirkm, cdent)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
- Status: Majority reached, will be approved on July 24 unless new objections are posted

Inclusion & Diversity

Decisions should be globally inclusive [7] (johnthetubaguy)
- Status: New revision posted. Might be better expressed as a principle and a project-team-guide chapter
Drop Technical Committee meetings [8] (flaper87)
- Status: New revision posted, discussion in progress
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 [9] (flaper87)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
- Status: Initial discussion
Support "Driver teams" [10] [11] (dhellmann)
- Status: Frozen while thingee works on driver discoverability
networking-cisco project team addition [12] (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

@@ Line 4: / Line 4: @@
 === Current proposals ===
-''Status last updated: July 13, 2017''
+''Status last updated: July 21, 2017''
 '''Leadership'''
-* Technical Committee vision (johnthetubaguy, cdent, dtroyer)
-** Initial draft for public feedback [https://review.openstack.org/453262]
-** Subsequent patch integrating feedback and editing for style [https://review.openstack.org/473620]
-** Fix typo in vision document [https://review.openstack.org/482152]
-** move the vision from reference to resolution [https://review.openstack.org/482686]
-** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
-** Status: The whole patch chain now has majority support, will be merged on July 17 unless new objections are raised.
 * Describe what upstream support means [https://review.openstack.org/440601] (johnthetubaguy)
-** Status: Discussion in progress on latest revision. New patchset likely needed.
+** Status: Discussion in progress on latest revision.
 * ''Resurrect SWG''
 ** ''ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html''
@@ Line 33: / Line 26: @@
 ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
 * Add Blazar project team [https://review.openstack.org/482860]
-** Status: Initial discussion
+** Status: Discussion in progress, decision likely to be made after Pike releases
@@ Line 39: / Line 32: @@
 * 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
-** Status: Voting in progress, just missing a few votes
+** Status: Majority reached, will be approved on July 24 unless new objections are posted
@@ Line 46: / Line 39: @@
 ** Status: New revision posted. Might be better expressed as a principle and a project-team-guide chapter
 * Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87)
-** Status: New revision needed
+** Status: New revision posted, discussion in progress
-** Next step: flaper87 to update it
 * ''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.''
+** ''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'''
-* Support "Driver teams" [https://review.openstack.org/403826] [https://review.openstack.org/403829] [https://review.openstack.org/403836] [https://review.openstack.org/403839] (dhellmann)
+* 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
+** Status: Initial discussion
+* Support "Driver teams" [https://review.openstack.org/403836] [https://review.openstack.org/403839] (dhellmann)
 ** Status: Frozen while thingee works on driver discoverability
 * networking-cisco project team addition [https://review.openstack.org/363709]  (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''