[openstack-dev] [tc] Technical Committee Status update, January 19th

Thierry Carrez thierry at openstack.org
Fri Jan 19 10:05:22 UTC 2018


This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:


If you are working on something (or plan to work on something)
governance-related that is not reflected on the tracker yet, please feel
free to add to it !

== Recently-approved changes ==

* Extra ATCs updates: trove, I18n
* Goal updates: blazar, trove

Not much was approved last week as we rebuild a pipeline of changes
after the holiday break.

== Rocky goals ==

We now have a set of proposed goals and associated champions:

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

[1] https://review.openstack.org/513875
[2] https://review.openstack.org/532361
[3] https://review.openstack.org/532627
[4] https://review.openstack.org/#/c/533544/
[5] https://review.openstack.org/534605

Many thanks to the volunteers! Now we need to decide how many goals we
want to pursue during the Rocky cycle, and which ones. The selection has
a good mix of dev-facing improvements (storyboard, mox), operator-facing
improvements (cold upgrade capabilities, mutable config), and
enduser-facing improvements (pagination links).

Emilien started a thread to collect the community input on those, before
the TC makes the final cut. Please chime in on the thread at:


== Voting in progress ==

Matt Treinish's update to the Python PTI for tests to be specific and
explicit is still missing a couple of votes to pass:


Following Monty's suggestion, I proposed a change in the release naming
process polling to use a CIVS public poll to rank the naming candidates.
This is still missing a couple of votes to pass:


Doug proposed to use StoryBoard for tracking Rocky goal completion
(rather than a truckload of governance changes). Voting is in progress
on that change, please comment at:


== Under discussion ==

The discussion started by Graham Hayes to clarify how the testing of
interoperability programs should be organized in the age of add-on
trademark programs is still going on, now on an active mailing-list
thread. Please chime in to inform the TC choice:


A new OpenStack project team was proposed to add a function-as-a-service
component to OpenStack (called Qinling). At this point this team would
obviously be added to the Rocky development cycle. Please give your
opinion at:


== TC member actions for the coming week(s) ==

TC member activity will be focused on Rocky goal selection for the
coming week.

We also need to look into the discussions we need to have at the PTG --
we have plenty of room for additional discussion topics during the
Monday-Tuesday part of the event, so it is easy to dedicate a room for
half a day to a full day to make good progress on critical issues.

Finally, we should also be thinking about topics that would make good
post-lunch presentations at the PTG in Dublin:


== Office hours ==

To be more inclusive of all timezones and more mindful of people for
which English is not the primary language, the Technical Committee
dropped its dependency on weekly meetings. So that you can still get
hold of TC members on IRC, we instituted a series of office hours on

* 09:00 UTC on Tuesdays
* 01:00 UTC on Wednesdays
* 15:00 UTC on Thursdays

For the coming week, I expect discussions to be focused around Rocky
goal selection.


Thierry Carrez (ttx)

More information about the OpenStack-dev mailing list