Open Stack

Hi!

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

https://wiki.openstack.org/wiki/Technical_Committee_Tracker

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 ==

Nothing merged this week, but we are getting closer to final approval on
several long-standing proposals, see below!


== Voting in progress ==

One of the option for clarifying testing for interop programs seems to
be consensual enough to pass. It extends potential test locations to
match the current state of things and what teams agree to support.
Please review and chime in on:

https://review.openstack.org/#/c/550571/

The definition of "extended maintenance" is also reaching its
conclusion, with a proposal that is being consensual so far. Under this
proposal stable branches shall remain open to accept fixes as long as
reasonably possible, enabling people to step up and maintain branches
beyond the minimal maintenance window guaranteed by the stable branch
maintenance team. Please review and comment on:

https://review.openstack.org/#/c/548916/

Tony Breeds proposed to rename the clarify the scope for the
recently-added PowerStackers team, to reflect its focus on PowerVM
(rather than all things POWER). We are still missing a number of votes
to pass that change. Please see:

https://review.openstack.org/#/c/551413/

Finally, we have a change to move Zuul out of the OpenStack Infra
project team repositories and OpenStack governance. This is the first
step in establishing our infrastructure tooling under its own brand, to
make it easier to promote it beyond OpenStack. The rationale was
explained by Jim Blair in more detail at:

http://lists.openstack.org/pipermail/openstack-dev/2018-March/128396.html

While the decision is more of an infra team internal decision on which
repositories they directly maintain, feel free to chime in on the thread
or the review with your thoughts on this. This already has majority
support from the TC, and will be approved on Tuesday unless new
objections are posted:

https://review.openstack.org/#/c/552637/


== Under discussion ==

There is a proposal about splitting the Kolla-kubernetes team out of the
Kolla/Kolla-ansible team, to reflect the fact that the teams are
actually separate. This obviously creates naming/namespace questions,
which are as everyone knows the hardest problem in computer science.
Please chime in on:

https://review.openstack.org/#/c/552531/

A new project team was just proposed to make the Adjutant project an
official OpenStack deliverable. Adjutant is a service built to help
manage certain elements of operations processes by providing micro APIs
around complex underlying workflow. Please review the proposal at:

https://review.openstack.org/#/c/553643/


== TC member actions/focus/discussions for the coming week(s) ==

For this week I expect final votes on the Extended maintenance proposal
and the interop tests locations, which may trigger additional
last-minute discussions.

I'll create stories in StoryBoard to track high-level TC initiatives. A
general overview of the stories to create is available for review at:

https://etherpad.openstack.org/p/rocky-tc-stories

We should also establish an etherpad to discuss potential Forum sessions
we'd like to file for the Vancouver Summit.


== 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
#openstack-tc:

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

Feel free to add your own office hour conversation starter at:
https://etherpad.openstack.org/p/tc-office-hour-conversation-starters

Cheers,

-- 
Thierry Carrez (ttx)