Hi! Here is our regular 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 a regularly-updated status list of all open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee == Recently-approved changes == * Introduce Top 5 help wanted list [1] * Add "Doc owners" to top-5 wanted list [2] * Guidelines for managing releases of binary artifacts [3] * Barbican gets the assert:supports-upgrade tag [4] * New git repositories: kuryr-tempest-plugins, zuul-sphinx, openstack-ansible-os_freezer, puppet-ganesha [1] https://review.openstack.org/#/c/466684/ [2] https://review.openstack.org/#/c/469115/ [3] https://review.openstack.org/#/c/469265/ [4] https://review.openstack.org/#/c/472547/ The "Top 5 help wanted list" is published at: https://governance.openstack.org/tc/reference/top-5-help-wanted.html The idea is to be explicit about where OpenStack, as a whole, urgently needs help, and where contributing would make a significant difference. Let's all encourage investment in those areas and celebrate whoever works on them. == Open discussions == The latest draft for the TC vision is still up for review. Please see it at: * Begin integrating vision feedback and editing for style [5] [5] https://review.openstack.org/#/c/473620/ The database support resolution is also up for review, although it could use a new patchset to address formatting issues. Please review it at: * Declare plainly the current state of PostgreSQL in OpenStack [6] [6] https://review.openstack.org/427880 Discussion also continues on John Garbutt's resolution on ensuring that decisions are globally inclusive. Please see: * Decisions should be globally inclusive [7] [7] https://review.openstack.org/#/c/460946/ John also updated his clarification of what "upstream support" means. It's up for review at: * Describe what upstream support means [8] [8] https://review.openstack.org/440601 We had a meeting this week around goals, and the outcome was summarized by thingee in the following ML thread: http://lists.openstack.org/pipermail/openstack-dev/2017-June/118808.html TL;DR: is that we identified a need for project management to drive the completion of goal, therefore goals should probably have "champions" pushing them. We think that Queens should only have two goals, with the following options leading the pack: * Split tempest plugins (already approved) [9] * Policy and docs in code [10] [9] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html [10] https://review.openstack.org/#/c/469954/ The other goals were a bit less popular. Discovery alignment [11][12] was deemed a bit difficult, Migrate off paste [13] lacking a practical success story and Python3.5 continuation [14] slightly premature. Please comment on those reviews and threads if you feel stronglmy one way or another: [11] https://review.openstack.org/#/c/468436/ [12] https://review.openstack.org/#/c/468437/ [13] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117747.html [14] http://lists.openstack.org/pipermail/openstack-dev/2017-May/117746.html == Voting in progress == Two patches reached majority votes earlier this week and will be approved Monday unless there are last-minute objections: * Remove "meritocracy" from the opens [15] * Introduce assert:supports-api-interoperability tag [16] [15] https://review.openstack.org/473510 [16] https://review.openstack.org/418010 Flavio proposed an addition to the top-5 wanted list, which seems rather consensual: * Add "Glance Contributors " to top-5 wanted list [17] [17] https://review.openstack.org/#/c/474604/ Finally, following a discussion on the ML I proposed to remove Fuel from the official list of projects, which also seems consensual so far: * Move Fuel from official to unofficial (hosted) [18] [18] https://review.openstack.org/#/c/475721/ == 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 ttx to sync with Gluon on progress and report back johnthetubaguy to resurrect the SWG group and set up regular reporting == Need for a TC meeting next Tuesday == We don't seem to be blocked on anything currently, so I don't think a meeting is necessary to make progress. Cheers! -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev