[openstack-dev] [tc] Status update, Jun 30

Thierry Carrez thierry at openstack.org
Fri Jun 30 09:35:04 UTC 2017


Hi!

This is the weekly update on Technical Committee initiatives. You can
find the full list of all open topics at:

https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee


== Recently-approved changes ==

* Introduce assert:supports-api-interoperability tag [1]
* Move Fuel from official to unofficial (hosted) [2]
* Team diversity tags update [3]
* Do not use confusing "meritocracy" word in the opens [4]
* Goal completion updates from: glance
* New git repositories: neutron-fwaas-dashboard, freezer-tempest-plugin,
ptgbot, puppet-ptgbot, logstash-filters, ironic-python-agent-builder

[1] https://review.openstack.org/#/c/418010/
[2] https://review.openstack.org/#/c/475721/
[3] https://review.openstack.org/#/c/475844/
[4] https://review.openstack.org/#/c/473510/

The "assert:supports-api-interoperability" tag can be asserted for
deliverables which follow the API interoperability guidelines and that
they will not change (or remove) an API in a way that will break
existing users of an API. See details at:

https://governance.openstack.org/tc/reference/tags/assert_supports-api-interoperability.html


== Open discussions ==

The two changes around TC vision are still up for review. Please see
those at:

* Initial draft [5]
* Subsequent draft integrating feedback and editing for style [6]

[5] https://review.openstack.org/#/c/453262/
[6] https://review.openstack.org/#/c/473620/

Discussion also continues on John Garbutt's resolution on ensuring that
decisions are globally inclusive. At this stage it should probably be
turned into a guiding principle, and a chapter in the Project Team
Guide. Please see:

* Decisions should be globally inclusive [7]

[7] https://review.openstack.org/#/c/460946/

The following changes are also still in open discussion, although they
should probably have a new patchset published to take into account the
most recent feedback:

* Declare plainly the current state of PostgreSQL in OpenStack [8]
* Describe what upstream support means [9]

[8] https://review.openstack.org/427880
[9] https://review.openstack.org/440601

Finally, we also have a number of topics being brainstormed openly on
the mailing list. One is about replacing TC/UC side workgroups with
common SIGs [10], another is around finding a new leader for the
Stewardship WG [11], another about allowing teams to use their channel
for meetings [12], and the last one about dealing with the confusion
around "hosted" projects [13]. Please chime in if you have a strong
opinion one way or another:

[10]
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118723.html
[11]
http://lists.openstack.org/pipermail/openstack-dev/2017-June/119068.html
[12]
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
[13]
http://lists.openstack.org/pipermail/openstack-dev/2017-June/119043.html


== Voting in progress ==

Flavio's proposed addition to the top-5 wanted list is still missing a
couple of votes:

* Add "Glance Contributors " to top-5 wanted list [14]

[14] https://review.openstack.org/#/c/474604/


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

flaper87 to update "Drop Technical Committee meetings" with a new
revision

sdague or dirkm to post a new patchset on the database support
resolution, to address formatting issues

dims to sync with Stackube on progress and report back

We also need to find volunteers for the champion role in the proposed
(and already-approved) Pike goals. Please add your name on those if
you're willing to spearhead the effort on those.


== Need for a TC meeting next Tuesday ==

We could have used a meeting next week to discuss the next steps in the
vision if there were enough people interested in that. With July 4th
it's however unlikely that our usual meeting datetime would work for
that. I suggest we discuss it during the office hours or asynchronously
on the #openstack-tc channel instead.


Cheers!

-- 
Thierry Carrez (ttx)



More information about the OpenStack-dev mailing list