This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at: https://storyboard.openstack.org/#!/project/923 == Recent Activity == Approved changes: - python3-first goal: https://review.openstack.org/#/c/575933/ == Ongoing Discussions == Dims started porting the compute:starter-kit tag to be a constellation. This highlighted an issue with the current definition of that set of projects and their use of the tools in the base services list. - https://review.openstack.org/#/c/586212/ We had 7 teams without any volunteers to serve as PTL for the Stein cycle (Dragonflow, Freezer, Loci, Packaging-RPM, Refstack, Searchlight, and Winstackers). The Trove team had a volunteer, but that person does not qualify under our normal rules that say the PTL should be an ATC. This triggered some discussion of what the PTL's role is, why we have it, and whether we may need to make some changes in how it is defined and used. The TC will be reviewing what to do with those teams over the next week or two. - https://wiki.openstack.org/wiki/OpenStack_health_tracker#Status_updates Thierry posted about the changes to the Summit & PTG and how they will affect the Stein release cycle. tl;dr: Because the Summit and PTG will be combined at the end of Stein, the cycle will be a little longer to allow the release dates to sync with the event. - http://lists.openstack.org/pipermail/openstack-dev/2018-July/132651.html == TC member actions/focus/discussions for the coming week(s) == The TC members who are liaisons to one of the teams affected by a lack of PTL candidates should contact the current PTL for those teams to ensure that they are aware of the problem. Please review the suggested topics for the TC to discuss at the PTG: - https://etherpad.openstack.org/p/tc-stein-ptg The PTG is approaching quickly. Please complete any remaining team health checks. == Contacting the TC == The Technical Committee uses a series of weekly "office hour" time slots for synchronous communication. We hope that by having several such times scheduled, we will have more opportunities to engage with members of the community from different timezones. Office hour times in #openstack-tc: - 09:00 UTC on Tuesdays - 01:00 UTC on Wednesdays - 15:00 UTC on Thursdays If you have something you would like the TC to discuss, you can add it to our office hour conversation starter etherpad at: https://etherpad.openstack.org/p/tc-office-hour-conversation-starters Many of us also run IRC bouncers which stay in #openstack-tc most of the time, so please do not feel that you need to wait for an office hour time to pose a question or offer a suggestion. You can use the string "tc-members" to alert the members to your question. You will find channel logs with past conversations at http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ If you expect your topic to require significant discussion or to need input from members of the community other than the TC, please start a mailing list discussion on openstack-dev at lists.openstack.org and use the subject tag "[tc]" to bring it to the attention of TC members. __________________________________________________________________________ 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