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) governance-related that is not reflected on the tracker yet, please feel free to add to it ! == Recently-approved changes == * Update Python PTI for tests to be specific and explicit [1] * Allow public polling to choose release names [2] * New repositories: networking-generic-switch-tempest-plugin, tempest-stress, charm-neutron-api-genericswitch, charm-ironic, charm-panko * Goal updates: trove, solum, monasca, ironic, heat [1] https://review.openstack.org/#/c/519751/ [2] https://review.openstack.org/#/c/534226/ This week we finally merged updates to the language used in the Python PTI to be much more specific about how projects should be running tests. The objective is to have a more consistent experience between projects when running tests. Please see the Python PTI (publication job pending) at: https://governance.openstack.org/tc/reference/pti/python.html We also approved release naming process changes to turn the vote into a public poll (and not crash CIVS again with tens of thousands of emails to send to Foundation members). Expect the naming process for the S release to start soon. The updated process will be found here once the publication job runs: https://governance.openstack.org/tc/reference/release-naming.html == Rocky goals == We are in the final steps of selecting a set of community goals for Rocky. We need wide community input on which goals are doable and make the most sense! Please see the list of proposed goals and associated champions: * Storyboard Migration [3] (diablo_rojo) * Remove mox [4] (chandankumar) * Ensure pagination links [5] (mordred) * Add Cold upgrades capabilities [6] (masayuki) * Enable mutable configuration [7] (gcb) [3] https://review.openstack.org/513875 [4] https://review.openstack.org/532361 [5] https://review.openstack.org/532627 [6] https://review.openstack.org/#/c/533544/ [7] https://review.openstack.org/534605 NB: mriedem suggested on the ML that we wait until the PTG in Dublin to make the final call. It gives more time to carefully consider the goals, but delays the start of the work and makes planning pre-PTG a bit more difficult. == Voting in progress == Doug proposed to use StoryBoard for tracking Rocky goal completion (rather than a truckload of governance changes). This change now reached majority votes, and will be approved on Tuesday unless new objections are posted: https://review.openstack.org/#/c/534443/ A new OpenStack project team was proposed to add a function-as-a-service component to OpenStack (called Qinling). The proposal has majority support at this point, but the review raised interesting side discussions and questions. Since the team would be added for the Rocky cycle, there is no hurry so let's continue those discussions for a bit more time: https://review.openstack.org/#/c/533827/ == Under discussion == 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, now on an active mailing-list thread. Please chime in to inform the TC choice: https://review.openstack.org/521602 http://lists.openstack.org/pipermail/openstack-dev/2018-January/126146.html == TC member actions for the coming week(s) == One month out, we need to start looking into the discussions we need to have at the PTG (and good post-lunch presentation topics). We have plenty of room for additional discussion topics during the Monday-Tuesday part of the event, so it is easy to dedicate a room for half a day to a full day to make good progress on critical issues. We might also finalize the Rocky goal selection, unless we take on mriedem's suggestion to wait until PTG to make the final cut. == 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 discussions to be focused around Rocky goal selection and PTG prep. Cheers, -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
