Hi! With a few hours in advance (blame Bastille Day!) 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 == * Add Queens goal: policy and docs in code [1][2][3] * Add champions to selected Pike goals [4] * Remove remaining 'big tent' references [5] * New repositories: castellan-ui, tripleo-upgrade, os-service-types, tempest-tripleo-ui [1] https://review.openstack.org/#/c/469954/ [2] https://review.openstack.org/#/c/475882/ [3] https://review.openstack.org/#/c/481654/ [4] https://review.openstack.org/#/c/482869/ [5] https://review.openstack.org/#/c/480500/ So the cross-project goals for the Queens cycle have been defined, you can find them at: https://governance.openstack.org/tc/goals/queens/index.html One difference with the Pike goals is that each goal will have an active champion to project-manage them to completion, providing assistance, reminders and sometimes direct help to the project teams. == Open discussions == We have two new project teams being actively discussed, for potential approval once the Queens cycle is opened: Glare[6][7] and Blazar[8]. Please ask questions or voice your objections at: [6] https://review.openstack.org/#/c/479285/ [7] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119442.html [8] https://review.openstack.org/#/c/482860/ Discussion is still in progress on two clarifications from John Garbutt, where new patchsets have been recently posted: Decisions should be globally inclusive: https://review.openstack.org/#/c/460946/ Describe what upstream support means: https://review.openstack.org/440601 == Voting in progress == The TC vision for 2019 was discussed at a recent TC meeting[9], brilliantly summarized by cdent at [10]. [9] http://eavesdrop.openstack.org/meetings/tc/2017/tc.2017-07-11-20.01.html [10] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119569.html It now has majority votes, and is about to be approved early next week, in the form of the following patch chain: https://review.openstack.org/#/c/453262/ https://review.openstack.org/#/c/473620/ https://review.openstack.org/#/c/482152/ https://review.openstack.org/#/c/482686/ This vision is of course produced on a specific date by a specific membership of the TC. Future TC members should definitely revisit it and potentially produce a new vision for another point in the future if they feel like the current vision is no longer productive. The long-standing "Declare plainly the current state of PostgreSQL in OpenStack" resolution is just one formal vote away from being approved: https://review.openstack.org/#/c/427880/ Finally, a number of tag changes are about to be approved: unless there are objections congress should get the stable:follows-policy tag[11], and Nova and Ironic should get the assert:supports-api-interoperability tag[12] [11] https://review.openstack.org/479030 [12] https://review.openstack.org/482759 == TC member actions for the coming week(s) == flaper87 to update "Drop Technical Committee meetings" with a new revision dims to sync with Stackube on progress and report back == Need for a TC meeting next Tuesday == No initiative is currently stuck, so there is no need for a TC meeting next week. 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
