[openstack-dev] [tc] Technical Committee Status update, March 23rd
Thierry Carrez
thierry at openstack.org
Fri Mar 23 09:36:49 UTC 2018
Hi!
This is the weekly summary of Technical Committee initiatives. You can
find the full list of currently-considered changes at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/project/923
== Recently-approved changes ==
* Resolution about stable branch EOL and "extended maintenance" [1]
* Clarify testing for interop programs [2]
* Rename and clarify scope for PowerStackers [3]
* New repos: oslo.limit, cyborg-specs, ansible-config_template,
ansible-role-systemd* + several xstatic-* repositories
* Removed repos: ironic-inspector-tempest-plugin, zuul-*, nodepool
[1] https://review.openstack.org/#/c/548916/
[2] https://review.openstack.org/#/c/550571/
[3] https://review.openstack.org/#/c/551413/
Two major items were finally approved this week. The first one is the
creation of an "extended maintenance" concept. Stable branches will no
longer be automatically terminated once the maintenance period is over.
They will be kept around for as long as they are maintained by
volunteers. This should enable new resources to step up if they want to
continue maintaining stable branches beyond the minimal period
guaranteed by the stable maintenance team:
https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
The second major item approved this week is the long-awaited
clarification on acceptable location for interoperability tests, in the
age of add-on trademark programs. The adopted resolution relaxes
potential locations and got support from all parties involved:
https://governance.openstack.org/tc/resolutions/20180307-trademark-program-test-location.html
In addition to those two, another noticeable change this week is the
removal of Zuul and Nodepool from OpenStack project governance, as they
are looking into forming a separately-branded project supported by the
OpenStack Foundation. For more details, you can read Jim Blair's email at:
http://lists.openstack.org/pipermail/openstack-dev/2018-March/128396.html
== Voting in progress ==
Melvin and I posted a resolution proposing a minimal governance model
for SIGs. It proposes that any escalated conflict inside a SIG or
between SIGs should be arbitrated by a SIGs admin group formed of one TC
member and one UC member, with the Foundation executive director
breaking ties in case of need. A similar resolution was adopted by the
UC. This resolution has majority support already and will be approved on
Tuesday, unless new objections are posted. So please review at:
https://review.openstack.org/#/c/554254/
Tony proposed an update to the new projects requirements list, to match
our current guidelines in terms of IRC meetings. This resolution also
has majority support already and will be approved on Tuesday, unless new
objections are posted:
https://review.openstack.org/#/c/552728/
== Under discussion ==
Jeffrey Zhang's proposal about splitting the Kolla-kubernetes team out
of the Kolla/Kolla-ansible team is still under discussion, with
questions about the effect of the change on the Kolla-k8s team. A thread
on the mailing-list would be good to make sure this discussion gets
wider input from affected parties. Please chime in on:
https://review.openstack.org/#/c/552531/
The discussion is also on-going the Adjutant project team addition.
Concerns about the scope of Adjutant, as well as fears that it would
hurt interoperability between OpenStack deployments were raised. A
deeper analysis and discussion needs to happen befoer the TC can make a
final call on this one. You can jump in the discussion here:
https://review.openstack.org/#/c/553643/
== TC member actions/focus/discussions for the coming week(s) ==
For the coming week I expect discussions to continue around the Kolla
split and the Adjutant team addition.
I'll be spending time organizing the Kubernetes/OpenStack community
discussions that will happen around KubeCon EU in Copenhagen in May.
We'll continue brainstorming ideas of topics for the Forum in Vancouver.
You can add ideas to:
https://etherpad.openstack.org/p/YVR-forum-TC-sessions
== 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)
More information about the OpenStack-dev
mailing list