Difference between revisions of "Meetings/TechnicalCommittee"
< Meetings
(→Current proposals) |
|||
| Line 4: | Line 4: | ||
=== Current proposals === | === Current proposals === | ||
| − | ''Status last updated: Jun | + | ''Status last updated: Jun 12, 2017'' |
'''Leadership''' | '''Leadership''' | ||
| Line 35: | Line 35: | ||
'''Simplification''' | '''Simplification''' | ||
| − | * postgresql support in OpenStack -- two alternative solutions: | + | * Document postgresql support in OpenStack -- two alternative solutions: |
| − | ** Declare plainly the current state of | + | ** Declare plainly the current state of MySQL in OpenStack [https://review.openstack.org/427880] (sdague, dirkm) |
** Document lack of postgresql support [https://review.openstack.org/465589] (cdent) | ** Document lack of postgresql support [https://review.openstack.org/465589] (cdent) | ||
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html | ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html | ||
| − | ** Status: | + | ** Status: Dirk has integrated the latest feedback. Discussion in progress on that version |
| − | |||
* ''Culling projects that are not going anywhere (ttx, ?)'' | * ''Culling projects that are not going anywhere (ttx, ?)'' | ||
** ''Status: brainstorming'' | ** ''Status: brainstorming'' | ||
| Line 47: | Line 46: | ||
'''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: New revision | + | ** Status: New revision posted, discussion in progress on that version. |
| − | |||
* Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87) | * Drop Technical Committee meetings [https://review.openstack.org/459848] (flaper87) | ||
** Status: New revision needed | ** Status: New revision needed | ||
** Next step: flaper87 to update it | ** Next step: flaper87 to update it | ||
* Office hours -- two patches: | * Office hours -- two patches: | ||
| − | * | + | * Follow-up precisions on office hours [https://review.openstack.org/470926] (ttx) |
| − | + | ** Status: Voting in progress | |
| − | ** Status: | ||
* ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)'' | * ''Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)'' | ||
** ''Status: brainstorming'' | ** ''Status: brainstorming'' | ||
| Line 64: | Line 61: | ||
** Add Queens goal to add collection links [https://review.openstack.org/468436] | ** Add Queens goal to add collection links [https://review.openstack.org/468436] | ||
** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437] | ** Add Queens Goal for full discovery alignment [https://review.openstack.org/468437] | ||
| − | ** Status: | + | ** Status: Discussion in progress, some questions asked |
* Policy and docs in code [https://review.openstack.org/469954] | * Policy and docs in code [https://review.openstack.org/469954] | ||
| − | ** Status: | + | ** Status: This goal seems to be well accepted. The question is now more if that particular goal should be selected for Queens (rather than others) |
* ''Migrate off paste'' | * ''Migrate off paste'' | ||
** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html'' | ** ''Status: Initial ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html'' | ||
| Line 81: | Line 78: | ||
* 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] (dhellmann) | ||
** Status: Voting in progress | ** Status: Voting in progress | ||
| + | |||
=== Next Meeting === | === Next Meeting === | ||
| − | * Date: | + | * Date: tbd |
| − | * Chair: | + | * Chair: tbd |
| Line 96: | Line 94: | ||
==== Apologies for Absence ==== | ==== Apologies for Absence ==== | ||
| + | * tbd | ||
Revision as of 09:04, 12 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 12, 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)
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
- Document postgresql support in OpenStack -- two alternative solutions:
- Declare plainly the current state of MySQL in OpenStack [8] (sdague, dirkm)
- Document lack of postgresql support [9] (cdent)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html
- Status: Dirk has integrated the latest feedback. Discussion in progress on that version
- Culling projects that are not going anywhere (ttx, ?)
- Status: brainstorming
Inclusion & Diversity
- Decisions should be globally inclusive [10] (johnthetubaguy)
- Status: New revision posted, discussion in progress on that version.
- Drop Technical Committee meetings [11] (flaper87)
- Status: New revision needed
- Next step: flaper87 to update it
- Office hours -- two patches:
- Follow-up precisions on office hours [12] (ttx)
- Status: Voting in progress
- Workgroups should not be UC or TC-side, should always be both (mrhillsman, ttx)
- Status: brainstorming
Goals
- Discovery alignment (two options):
- Policy and docs in code [15]
- Status: This goal seems to be well accepted. The question is now more if that particular goal should be selected for Queens (rather than others)
- 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" [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
- Guidelines for managing releases of binary artifacts [21] (dhellmann)
- Status: Voting in progress
Next Meeting
- Date: tbd
- Chair: tbd
Agenda
- [add agenda items here]
- Open discussion
Apologies for Absence
- tbd
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
