Difference between revisions of "Meetings/TechnicalCommittee"
< Meetings
| Line 74: | Line 74: | ||
=== Next Meeting === | === Next Meeting === | ||
| − | * Date: | + | * Date: June 6th |
* Chair: tbd | * Chair: tbd | ||
Revision as of 08:48, 29 May 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: May 26, 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: New revision posted May 22, might need another revision
- Describe what upstream support means [3] (johnthetubaguy)
- Status: New revision needed
- Next step: johnthetubaguy to update it next week-ish
- Introduce Top 5 help wanted list [4] (ttx, dims)
- Status: Gathering initial feedback on proposal
- Etcd as a base service [5] (dims)
- Status: Initial discussion on the review
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 ?
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: No consensus yet, and energy is running low on pushing subsequent refinement patchsets
- Next step: Might need a sync discussion in a meeting to lean one way or the other
- Culling projects that are not going anywhere (ttx, ?)
- Status: brainstorming
Inclusion & Diversity
- How to propose changes: do not mention meetings [10] (ttx)
- Status: Small doc catchup change. Voting in progress
- Decisions should be globally inclusive [11] (johnthetubaguy)
- Status: New revision needed
- Next step: johnthetubaguy to update it
- Document voting process for `formal-vote` patches [12] (flaper87)
- Status: New patchset posted on May 22, voting in progress (needs 66%)
- Drop Technical Committee meetings [13] (flaper87)
- Status: New revision needed
- Next step: flaper87 to update it
- Office hours -- two patches:
- Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
- Status: brainstorming
Other
- Support "Driver teams" [16] [17] [18] [19] (dhellmann)
- Status: Frozen while thingee works on driver discoverability
- networking-cisco project team addition [20] (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
- Policy on binary images publication (dhellmann)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html
- Status: to be proposed
Next Meeting
- Date: June 6th
- Chair: tbd
Agenda
- Declare the current state of Postgresql in OpenStack
Apologies for Absence
- tbd
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
