Jump to: navigation, search

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: January 30th, 2018'''
+
'''Status last updated: February 2nd, 2018'''
  
  
Line 19: Line 19:
  
  
An evolution of the process for tracking goals was also proposed:
+
Additionally, dhellmann proposed an evolution of the process for tracking goals:
 
* 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: Majority reached, but Doug has asked for more time fleshing out the implementation details
+
** Status: Doug has asked for more time fleshing out the implementation details
  
  
 
==== New teams ====
 
==== New teams ====
  
* Qinling: Function as a Service in OpenStack [https://review.openstack.org/533827]
+
* OpenStack-PowerVM project [https://review.openstack.org/540165]
** Status: Majority reached and questions answered, will be approved on Friday unless new objections are posted
+
** Status: Under discussion
  
  
Line 33: Line 33:
  
 
* 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
** See cmurphy's write-up at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html
+
** See cmurphy's write-up and following ML discussion at http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html
  
  
Line 40: Line 40:
  
 
* Naming poll for S development cycle
 
* Naming poll for S development cycle
** Status: Not started, volunteer seeked
+
** Status: pabelanger volunteered to drive it, waiting for release_naming.rst patches.
 
* 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:46, 2 February 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: February 2nd, 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 toggling debug option at runtime [5] (gcb)


Additionally, dhellmann proposed an evolution of the process for tracking goals:

  • update the goal process to use storyboard for tracking [6]
    • Status: Doug has asked for more time fleshing out the implementation details


New teams

  • OpenStack-PowerVM project [7]
    • Status: Under discussion


Leadership


Other

  • Naming poll for S development cycle
    • Status: pabelanger volunteered to drive it, waiting for release_naming.rst patches.
  • Support "Driver teams" [9] [10]
    • Status: Frozen while thingee works on driver discoverability and cdent works on getting more drivers into Neutron proper