Hi! This is the weekly summary of Technical Committee initiatives. You can find the full list of all open topics (updated twice a week) at:
https://wiki.openstack.org/wiki/Technical_Committee_Tracker If you are working on something (or plan to work on something) that is not on the tracker, feel free to add to it ! == Recently-approved changes == * Add "goal champions" as a top-5 help wanted area [1][2] * Rename Shade team to OpenStackSDK, include os-client-config [3][4][5] * Rename 'top-5' list to 'help most needed' list [6][7] * Removing unused docs:follows-policy tag [8] * New repos: mistral-tempest-plugin, congress-tempest-plugin, self-healing-sig * Goal updates: mistral, tacker, cloudkitty, octavia, congress, murano [1] https://review.openstack.org/#/c/527138/ [2] https://review.openstack.org/#/c/510656/ [3] https://review.openstack.org/#/c/523520/ [4] https://review.openstack.org/#/c/523519/ [5] https://review.openstack.org/#/c/524249/ [6] https://review.openstack.org/#/c/520619/ [7] https://review.openstack.org/#/c/527138/ [8] https://review.openstack.org/#/c/524217/ Most significant change this week is the addition of "goal champions" as one area in our top-5 list, now renames "Help most needed" list. Now that the list is fully formed, we'll ramp up the communication around it as an effort to point organizations and contributors to areas in most need of urgent help. You can find the list at: https://governance.openstack.org/tc/reference/help-most-needed.html == Voting in progress == Debian packaging activity moved from OpenStack repositories to Debian repositories, and therefore the repositories (and corresponding project team) are being retired. This is still missing a couple of votes: https://review.openstack.org/524732 == Under discussion == As you probably noticed, I started a discussion around the possibility of increasing the length of our "coordinated releases" development cycle, as a way to reduce overall pressure in development. I'll try to summarize the thread soon, but in the mean time if you have a strong opinion on it, please join the party at: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125473.html The discussion started by Graham Hayes to clarify how the testing of interoperability programs should be organized in the age of add-on trademark programs is still going on, with most people still trying to wrap their heads around the various options. We'd welcome more opinions on that thread, so please chime in on the review: https://review.openstack.org/521602 Matt Treinish proposed an update to the Python PTI for tests to be specific and explicit. Wider community input is needed on that topic. Please review at: https://review.openstack.org/519751 We still only have one goal proposed for Rocky. We need other proposals before we can make a call. See the thread: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124976.html == TC member actions for the coming week(s) == Please brainstorm potential goals for the Rocky cycle, so that we can move to proposal phase soon. == 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 For the coming week, I expect a continuation of the discussion around one-year cycles and alternate solutions to make openstack development more accessible to part-time contributors, as well as a bit of live Rocky goal brainstorming. 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
