Difference between revisions of "Technical Committee Tracker"
Line 5: | Line 5: | ||
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. | This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. | ||
− | '''Status last updated: January | + | '''Status last updated: January 12th, 2018''' |
Line 12: | Line 12: | ||
* Clarify testing for interop programs [https://review.openstack.org/521602] (mugsie) | * Clarify testing for interop programs [https://review.openstack.org/521602] (mugsie) | ||
** Status: Options still being discussed, no clear consensus yet | ** Status: Options still being discussed, no clear consensus yet | ||
+ | ** See cmurphy's write-up at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html | ||
==== Rocky goals ==== | ==== Rocky goals ==== | ||
− | * | + | Waiting for more goals to be posted before we make the selection. Here are the currently-proposed options: |
− | + | ||
+ | * Remove mox [https://review.openstack.org/532361] (smcginnis) | ||
+ | * Ensure pagination links [https://review.openstack.org/532627] (mordred) | ||
+ | * Storyboard Migration [https://review.openstack.org/513875] (diablo_rojo) | ||
Line 27: | Line 31: | ||
** we have outgrown the CIVS service we use for elections (at least for sending to every foundation member) so he proposes just running a public poll | ** we have outgrown the CIVS service we use for elections (at least for sending to every foundation member) so he proposes just running a public poll | ||
* Update Python PTI for tests to be specific and explicit [https://review.openstack.org/519751] (mtreinish) | * Update Python PTI for tests to be specific and explicit [https://review.openstack.org/519751] (mtreinish) | ||
− | ** Status: Comments call for opening the discussion in a ML thread | + | ** Status: Comments call for opening the discussion in a ML thread, looking for volunteer to pick it up |
* 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 and cdent works on getting more drivers into Neutron proper | ** Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper |
Revision as of 09:32, 12 January 2018
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/ .
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
Status last updated: January 12th, 2018
Leadership
- Clarify testing for interop programs [1] (mugsie)
- Status: Options still being discussed, no clear consensus yet
- See cmurphy's write-up at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html
Rocky goals
Waiting for more goals to be posted before we make the selection. Here are the currently-proposed options:
- Remove mox [2] (smcginnis)
- Ensure pagination links [3] (mordred)
- Storyboard Migration [4] (diablo_rojo)
Other
- Naming poll for S development cycle
- Status: Not started
- mordred suggests having our election team manage the poll
- we have outgrown the CIVS service we use for elections (at least for sending to every foundation member) so he proposes just running a public poll
- Update Python PTI for tests to be specific and explicit [5] (mtreinish)
- Status: Comments call for opening the discussion in a ML thread, looking for volunteer to pick it up
- Support "Driver teams" [6] [7]
- Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper