Difference between revisions of "Technical Committee Tracker"
m |
|||
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: September | + | '''Status last updated: September 22nd, 2017''' |
==== Leadership ==== | ==== Leadership ==== | ||
− | |||
− | |||
* Adding Infra contributors is a top 5 opportunity [https://review.openstack.org/502259] (fungi) | * Adding Infra contributors is a top 5 opportunity [https://review.openstack.org/502259] (fungi) | ||
− | ** Status: | + | ** Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised. |
* Add Designate to the top 5 help wanted. [https://review.openstack.org/504217] (mugsie) | * Add Designate to the top 5 help wanted. [https://review.openstack.org/504217] (mugsie) | ||
− | ** Status: Open discussion | + | ** Status: Open discussion, likely to need another patchset |
* Update wording in Glance "Top 5" item [https://review.openstack.org/503168] (flaper87) | * Update wording in Glance "Top 5" item [https://review.openstack.org/503168] (flaper87) | ||
− | ** Status: | + | ** Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised. |
==== New project teams ==== | ==== New project teams ==== | ||
− | * | + | |
− | ** Status: Open discussion | + | * Add Blazar project team [https://review.openstack.org/482860] |
+ | ** Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised. | ||
+ | * Add Glare project team [https://review.openstack.org/479285] | ||
+ | ** Status: Open discussion, likely to be delayed | ||
+ | ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html | ||
+ | * Add Stackube project team [https://review.openstack.org/462460] | ||
+ | ** Status: Voting in progress, another patchset likely needed | ||
* Masakari - Instances High Availability Service [https://review.openstack.org/500118] | * Masakari - Instances High Availability Service [https://review.openstack.org/500118] | ||
− | |||
− | |||
** Status: Voting in progress | ** Status: Voting in progress | ||
− | * | + | * Cyborg Application For Official Projects [https://review.openstack.org/504940] |
− | |||
− | |||
− | |||
** Status: Voting in progress | ** Status: Voting in progress | ||
==== 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: Discussion in progress on latest revision. Is likely to be transformed into guidance in the Project Team Guide | ** Status: Discussion in progress on latest revision. Is likely to be transformed into guidance in the Project Team Guide | ||
− | * | + | * 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: New SIGs are being created |
− | ** | + | ** Next step: Proper promotion of created SIGs on events, documentation and websites |
==== Other ==== | ==== Other ==== | ||
− | * | + | |
− | ** Status: | + | * Removing unused upgrade tags [https://review.openstack.org/506241] [https://review.openstack.org/506263] (smcginnis) |
− | * | + | ** Status: Open discussion |
− | ** Status: | + | * Put trove into maintenance mode [https://review.openstack.org/488947] |
+ | ** Status: Open discussion | ||
* Put searchlight into maintenance mode [https://review.openstack.org/502849] | * Put searchlight into maintenance mode [https://review.openstack.org/502849] | ||
** Status: Open discussion | ** Status: Open discussion | ||
− | |||
− | |||
− | |||
− | |||
* Be explicit about supported database versions [https://review.openstack.org/493932] (mordred) | * Be explicit about supported database versions [https://review.openstack.org/493932] (mordred) | ||
** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html | ** ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html | ||
− | ** Status: Open discussion | + | ** Status: Open discussion, needs another patchset |
* 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 | + | ** Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper |
* networking-cisco project team addition [https://review.openstack.org/363709] (thingee) | * networking-cisco project team addition [https://review.openstack.org/363709] (thingee) | ||
** Status: Blocked until driver teams are a thing | ** 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 | ** Next step: thingee to reach out to networking-cisco folks to check how much discoverability solves their issue |
Revision as of 10:27, 22 September 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/ .
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
Status last updated: September 22nd, 2017
Leadership
- Adding Infra contributors is a top 5 opportunity [1] (fungi)
- Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised.
- Add Designate to the top 5 help wanted. [2] (mugsie)
- Status: Open discussion, likely to need another patchset
- Update wording in Glance "Top 5" item [3] (flaper87)
- Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised.
New project teams
- Add Blazar project team [4]
- Status: Majority reached on Sept 20, to be approved on Sept 26 unless new objections are raised.
- Add Glare project team [5]
- Status: Open discussion, likely to be delayed
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html
- Add Stackube project team [6]
- Status: Voting in progress, another patchset likely needed
- Masakari - Instances High Availability Service [7]
- Status: Voting in progress
- Cyborg Application For Official Projects [8]
- Status: Voting in progress
Inclusion & Diversity
- Decisions should be globally inclusive [9] (johnthetubaguy)
- Status: Discussion in progress on latest revision. Is likely to be transformed into guidance in the Project Team Guide
- 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: New SIGs are being created
- Next step: Proper promotion of created SIGs on events, documentation and websites
Other
- Removing unused upgrade tags [10] [11] (smcginnis)
- Status: Open discussion
- Put trove into maintenance mode [12]
- Status: Open discussion
- Put searchlight into maintenance mode [13]
- Status: Open discussion
- Be explicit about supported database versions [14] (mordred)
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121144.html
- Status: Open discussion, needs another patchset
- Support "Driver teams" [15] [16]
- Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper
- networking-cisco project team addition [17] (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