Jump to: navigation, search

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 23rd, 2018'''
+
'''Status last updated: January 26th, 2018'''
  
  
Line 21: Line 21:
 
An evolution of the process for tracking goals was also proposed:
 
An evolution of the process for tracking goals was also proposed:
 
* update the goal process to use storyboard for tracking [https://review.openstack.org/534443]
 
* update the goal process to use storyboard for tracking [https://review.openstack.org/534443]
** Status: Vote in progress, still missing a couple of votes
+
** Status: Majority reached, to be approved on Tuesday unless new objections are posted.
  
  
Line 27: Line 27:
  
 
* Qinling: Function as a Service in OpenStack [https://review.openstack.org/533827]
 
* Qinling: Function as a Service in OpenStack [https://review.openstack.org/533827]
** Status: Majority reached, to be approved on Friday if no new objection is posted.
+
** Status: Majority reached, but good comments on the review that are worth exploring a bit more.
  
  
Line 39: Line 39:
 
==== Other ====
 
==== Other ====
  
* Allow public polling to choose release names [https://review.openstack.org/534226]
 
** Status: Majority reached, to be approved on Friday if no new objection is posted.
 
 
* Naming poll for S development cycle
 
* Naming poll for S development cycle
** Status: Not started, need above rule change and a volunteer first
+
** Status: Not started, volunteer seeked
* Update Python PTI for tests to be specific and explicit [https://review.openstack.org/519751] (mtreinish)
 
** Status: Majority reached, to be approved on Friday if no new objection is posted
 
 
* 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 15:34, 26 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 26th, 2018


Rocky goals

Here are the currently-proposed options:

  • Add Cold upgrades capabilities [1] (masayuki)
  • Remove mox [2] (smcginnis, chandankumar)
  • Ensure pagination links [3] (mordred)
  • Storyboard Migration [4] (diablo_rojo)
  • Enable mutable configuration [5] (gcb)


An evolution of the process for tracking goals was also proposed:

  • update the goal process to use storyboard for tracking [6]
    • Status: Majority reached, to be approved on Tuesday unless new objections are posted.


New teams

  • Qinling: Function as a Service in OpenStack [7]
    • Status: Majority reached, but good comments on the review that are worth exploring a bit more.


Leadership


Other

  • Naming poll for S development cycle
    • Status: Not started, volunteer seeked
  • Support "Driver teams" [9] [10]
    • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper