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 == * Officialize election organization working group [1] * stop linking to documentation from governance [2] * Tags are applied to deliverables, or teams [3] * Remove redundant links in index.rst [4] * Update URL for TC tracker on the wiki [5] * New repos: masakari-dashboard, log-classify, ansible-role-k8s-glance * Goal updates: vitrage, panko [1] https://review.openstack.org/521062 [2] https://review.openstack.org/523195 [3] https://review.openstack.org/#/c/523886/ [4] https://review.openstack.org/523121 [5] https://review.openstack.org/523381 Nothing really significant this week, mostly a bunch of cleanup changes and clarifications. == Voting in progress == Monty's patch updating shade team metainfo is still missing a couple of votes: https://review.openstack.org/523519 Doug Hellmann proposes to round up our top-5 "help needed" list with goal champions. His proposal is still short of a couple of votes: https://review.openstack.org/510656 The patch to remove the unused docs:follows-policy tag reached majority and will be approved on Tuesday unless new objections are posted: https://review.openstack.org/524217 == Under discussion == Graham Hayes proposed various options to clarify how the testing of interoperability programs should be organized, in the age of add-on trademark programs. It is a difficult trade-off between the benefits of centralizing reviews and decentralizing reviews for that specific area. 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 The "top-5 help wanted list" assumes there will always be 5 items, and the name is a bit of a mouthful. Naming is hard. Current proposal is to call is the "help most needed" list. If you prefer your bikesheds painted in blue, please comment at: https://review.openstack.org/520619 Emilien Macchi officially launched the goal proposing season for the Rocky cycle in a thread at: http://lists.openstack.org/pipermail/openstack-dev/2017-November/124976.html We already have one proposal on the docket (Storyboard migration), thanks to Kendall Nelson. Please chime in on whether it's a good idea at: https://review.openstack.org/513875 == TC member actions for the coming week(s) == Nothing specific. == 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 reports around the cross-community discussions that happened at KubeCon. 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
