Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 15:07, 7 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 7, 2017

Leadership

Technical Committee vision [1] (gothicmindfood, johnthetubaguy, cdent, dtroyer)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115006.html
- Status: Feedback was collected on draft review, ML and anonymous survey
- Next step: feedback needs to be distilled into actionable points (and split between cosmetic and significant changes).
Introduce assert:supports-api-interoperability tag [2] (mtreinish, sdague)
- Status: Needs another patchset
- Next step: mtreinish to address dhellmann's comments
Describe what upstream support means [3] (johnthetubaguy)
- Status: New revision needed
- Next step: johnthetubaguy to update it next week-ish
Top 5 wanted list (ttx, dims)
- Introduce Top 5 help wanted list [4]
- Add "Doc owners" to top-5 wanted list [5]
- Status: Voting in progress

New project teams

Add Stackube project team [6] (dims, ttx)
- 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 [7] (?)
- Status: Frozen while Gluon discusses further integration opportunities with Neutron
- Next step: This prospective team needs a TC sponsor/mentor to help them through the steps. Any volunteer ?
Add Blazar project team
- Under discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-June/117844.html

Simplification

postgresql support in OpenStack -- two alternative solutions:
- Declare plainly the current state of Posgresql in OpenStack [8] (sdague)
- Document lack of postgresql support [9] (cdent)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
- Status: Waiting for a new patchset
- Next step: dirk to integrate the latest feedback in sdague's proposal
Culling projects that are not going anywhere (ttx, ?)
- Status: brainstorming

Inclusion & Diversity

Decisions should be globally inclusive [10] (johnthetubaguy)
- Status: New revision needed
- Next step: johnthetubaguy to update it
Drop Technical Committee meetings [11] (flaper87)
- Status: New revision needed
- Next step: flaper87 to update it
Office hours -- two patches:
- Introduce office hours [12] (ttx)
- Establish a #openstack-tc water cooler channel [13] (dims)
- Status: Majority reached on May 30. To be approved on Jun 5
Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
- Status: brainstorming

Goals

Discovery alignment (two options):
- Add Queens goal to add collection links [14]
- Add Queens Goal for full discovery alignment [15]
- Status: Initial discussion
Policy and docs in code [16]
- Status: Initial discussion
Migrate off paste
- Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html
Continuing Python 3.5+ Support
- Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html

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
Guidelines for managing releases of binary artifacts [22] (dhellmann)
- Status: Voting in progress

Next Meeting

Date: TBD
Chair: EBD

Agenda

[add agenda items here]
Open discussion

Apologies for Absence

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: Jun 2, 2017''
+''Status last updated: Jun 7, 2017''
 '''Leadership'''
@@ Line 20: / Line 20: @@
 ** Introduce Top 5 help wanted list [https://review.openstack.org/#/c/466684/]
 ** Add "Doc owners" to top-5 wanted list [https://review.openstack.org/469115]
-** Status: Initial discussion on the patch
+** Status: Voting in progress
@@ Line 39: / Line 39: @@
 ** Document lack of postgresql support [https://review.openstack.org/465589] (cdent)
 ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
-** Status: No consensus yet, and energy is running low on pushing subsequent refinement patchsets
+** Status: Waiting for a new patchset
-** Next step: Sync discussion iat next week meeting
+** Next step: dirk to integrate the latest feedback in sdague's proposal
 * ''Culling projects that are not going anywhere (ttx, ?)''
 ** ''Status: brainstorming''
@@ Line 61: / Line 61: @@
 '''Goals'''
-* Add etherpad link with detailed steps to split-tempest-plugins goal [https://review.openstack.org/468972]
-** Status: Majority reached on Jun 1. To be approved on Jun 5.
 * Discovery alignment (two options):
 ** Add Queens goal to add collection links [https://review.openstack.org/468436]
@@ Line 81: / Line 79: @@
 ** 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
-* Policy on binary images publication (dhellmann)
+* Guidelines for managing releases of binary artifacts [https://review.openstack.org/469265] (dhellmann)
-** Guidelines for managing releases of binary artifacts [https://review.openstack.org/469265]
+** Status: Voting in progress
-** Resolution regarding container images [https://review.openstack.org/469248]
-** Status: Initial discussion
 === Next Meeting ===