Open Stack

Hi!

This new regular email will give you an update on the status of a number
of TC-proposed governance changes, in an attempt to rely less on a
weekly meeting to convey that information.

You can find the full status list of open topics at:
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee


== Recently-approved changes ==

* Stop *requiring* IRC meetings for project teams [1]
* Add Queens goal: split out tempest plugins [2]
* Update the language in the "4 opens" around design summits [3]

[1] https://review.openstack.org/#/c/462077/
[2] https://review.openstack.org/#/c/369749/
https://review.openstack.org/#/c/454070/

The Stackube and Gluon project proposals have been frozen by their
proposers, as the formers need to be set up on OpenStack infrastructure
(mentored by dims), and the latter need to engage in further discussions
with Neutron. To that effect, the Gluon team could use a TC member
mentor/sponsor to help them navigate the OpenStack seas. Any volunteer ?


== Open discussions ==

Two changes were recently proposed and are in the initial phases of
discussion/refinement:

* Introduce Top 5 help wanted list [3]
* Etcd as a base service [4]

We also have proposal(s) up to introduce the new office hours:

* Introduce office hours [5]
* Establish a #openstack-tc water cooler channel [6]

Please jump in there if you have an opinion.

[3] https://review.openstack.org/#/c/466684/
[4] https://review.openstack.org/#/c/467436/
[5] https://review.openstack.org/#/c/467256/
[6] https://review.openstack.org/#/c/467386/


== Voting in progress ==

We have two items that now seem ready for voting:

* How to propose changes: do not mention meetings [7]
* Document voting process for `formal-vote` patches [8]

Note that the second one (being a charter change) requires a 2/3 majority.

[7] https://review.openstack.org/#/c/467255/
[8] https://review.openstack.org/#/c/463141/


== Blocked items ==

The discussion around postgresql support in OpenStack is still very much
going on (with 2 slightly-different proposals), and energy is running
low on pushing subsequent refinement patchsets.

* Declare plainly the current state of Posgresql in OpenStack [9]
* Document lack of postgresql support [10]

[9] https://review.openstack.org/#/c/427880/
[10] https://review.openstack.org/465589

A specific meeting might be necessary to converge on a way forward, see
below. Feel free to jump in there (or on the ML discussion at
http://lists.openstack.org/pipermail/openstack-dev/2017-May/116642.html)


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

johnthetubaguy, cdent, dtroyer to continue distill TC vision feedback
into actionable points (and split between cosmetic and significant
changes) [https://review.openstack.org/453262]

johnthetubaguy to update "Describe what upstream support means" with a
new revision [https://review.openstack.org/440601]

johnthetubaguy to update "Decisions should be globally inclusive" with a
new revision [https://review.openstack.org/460946]

flaper87 to update "Drop Technical Committee meetings" with a new
revision [https://review.openstack.org/459848]

dhellmann to post proposal for a policy on binary images publication,
following the thread at
http://lists.openstack.org/pipermail/openstack-dev/2017-May/116677.html

ttx to refresh 2017 contributor attrition stats and report back.


== Need for a TC meeting next Tuesday ==

Based on the current status on the postgresql discussion, a meeting
(with a narrow agenda) could be useful to unblock the situation. A
thread on the openstack-tc list will be posted to see if it's a good
idea, and final decision on the meeting will be taken on Monday.

-- 
Thierry Carrez (ttx)