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 == Other approved changes: * add champion section to goal template https://review.openstack.org/575934 * a "castellan-compatible key store" is now part of the base services list https://governance.openstack.org/tc/reference/base-services.html#current-list-of-base-services Office hour logs from last week: * http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-19-09.00.html * http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-20-01.09.html * http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-21-15.00.html A few folks expressed concern that using the meeting bot to record the office hours made them more like a meeting. It would be useful to have some feedback from the community about whether having the logs separate is helfpul, or if linking to the timestamp in the regular channel logs would be sufficient. == Ongoing Discussions == The Adjutant team application was updated. * https://review.openstack.org/553643 Thierry started drafting a "technical design tenets" chapter for the project team guide as a place to explain topics like base services and other things we expect to be common development patterns in the community. * https://storyboard.openstack.org/#!/story/2002611 == TC member actions/focus/discussions for the coming week(s) == Project team "health check" interviews continue. Our goal is to check in with each team between now and the PTG, and record notes in the wiki. * https://wiki.openstack.org/wiki/OpenStack_health_tracker Remember that we agreed to send status updates on initiatives separately to openstack-dev every two weeks. If you are working on something for which there has not been an update in a couple of weeks, please consider summarizing the status. == 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. 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.