<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Dec 17, 2018 at 12:18 PM Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is the (mostly) weekly summary of work being done by the Technical<br>
Committee members. The full list of active items is managed in the<br>
wiki: <a href="https://wiki.openstack.org/wiki/Technical_Committee_Tracker" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Technical_Committee_Tracker</a><br>
<br>
We also track TC objectives for the cycle using StoryBoard at:<br>
<a href="https://storyboard.openstack.org/#!/project/923" rel="noreferrer" target="_blank">https://storyboard.openstack.org/#!/project/923</a><br>
<br>
== Recent Activity ==<br>
<br>
Project updates:<br>
<br>
* Add os-resource-classes under Nova:<br>
<a href="https://review.openstack.org/#/c/621699/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/621699/</a><br>
<br>
Other updates:<br>
<br>
* I added a TC "house rule" for voting on updates to the release<br>
management metadata for projects, to make it easier to keep those up<br>
to date: <a href="https://review.openstack.org/#/c/622989/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/622989/</a><br>
* Thierry has been working on a series of changes on behalf of the<br>
release management team to record the release management style used<br>
for each deliverable listed in the governance repository.<br>
** <a href="https://review.openstack.org/#/c/622902/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/622902/</a><br>
** <a href="https://review.openstack.org/#/c/622903/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/622903/</a><br>
** <a href="https://review.openstack.org/#/c/622904/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/622904/</a><br>
** <a href="https://review.openstack.org/#/c/624704/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/624704/</a><br>
** <a href="https://review.openstack.org/#/c/624951/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/624951/</a><br>
** <a href="https://review.openstack.org/#/c/624996/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/624996/</a><br>
* I updated the documentation of chair responsibilities to include the<br>
OSF annual report: <a href="https://review.openstack.org/#/c/624790/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/624790/</a><br>
* Lance proposed an update to document the process for changing PTLs in<br>
the middle of a cycle: <a href="https://review.openstack.org/#/c/620928/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/620928/</a><br>
* Ghanshyam proposed an update to clarify the term of TC chair, since<br>
some responsibilities include managing the election fo the next chair:<br>
<a href="https://review.openstack.org/#/c/621498/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/621498/</a><br>
* Zane's resolution describing how we will keep up with future Python 3<br>
releases has been approved: <a href="https://review.openstack.org/#/c/613145/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/613145/</a><br>
* Thierry and Chris' work to document the role of the TC has been<br>
approved: <a href="https://review.openstack.org/#/c/622400/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/622400/</a><br>
* I documented the official topic tags used to designate the voting<br>
rules to apply to each governance patch:<br>
<a href="https://review.openstack.org/#/c/625004/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/625004/</a><br>
<br>
== TC Meetings ==<br>
<br>
The next TC meeting will be 3 December @ 1400 UTC in #openstack-tc. See<br>
<a href="http://eavesdrop.openstack.org/#Technical_Committee_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/#Technical_Committee_Meeting</a> for details<br></blockquote><div><br></div><div>This will be on 3 January, right?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
== Ongoing Discussions ==<br>
<br>
Ghanshyam has proposed an enhancement to the Vision for OpenStack Clouds<br>
to cover feature discovery.<br>
<br>
* <a href="https://review.openstack.org/#/c/621516/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/621516/</a><br>
<br>
I have proposed an update to the TC house voting rules to cover<br>
documentation changes in the governance repository.<br>
<br>
* <a href="https://review.openstack.org/625005" rel="noreferrer" target="_blank">https://review.openstack.org/625005</a><br>
<br>
Dougal Matthews is stepping down as Mistral PTL, to be replaced by Renat<br>
Akhmerov.<br>
<br>
* <a href="https://review.openstack.org/#/c/625537/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/625537/</a><br>
<br>
== TC member actions/focus/discussions for the coming week(s) ==<br>
<br>
We need to work to approve Sean's patch with the Stein supported/testing<br>
runtimes list.<br>
<br>
* <a href="https://review.openstack.org/611080" rel="noreferrer" target="_blank">https://review.openstack.org/611080</a><br>
<br>
Thierry started a thread on the mailing list about adapting our office<br>
hours times. It would be good for us to resolve that so we can make the<br>
change after the new year, so I have renewed the thread with a summary<br>
of the options. Please vote.<br>
<br>
* <a href="http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001036.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-discuss/2018-December/001036.html</a><br>
<br>
== Contacting the TC ==<br>
<br>
The Technical Committee uses a series of weekly "office hour" time<br>
slots for synchronous communication. We hope that by having several<br>
such times scheduled, we will have more opportunities to engage<br>
with members of the community from different timezones.<br>
<br>
Office hour times in #openstack-tc:<br>
<br>
- 09:00 UTC on Tuesdays<br>
- 01:00 UTC on Wednesdays<br>
- 15:00 UTC on Thursdays<br>
<br>
If you have something you would like the TC to discuss, you can add<br>
it to our office hour conversation starter etherpad at:<br>
<a href="https://etherpad.openstack.org/p/tc-office-hour-conversation-starters" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/tc-office-hour-conversation-starters</a><br>
<br>
Many of us also run IRC bouncers which stay in #openstack-tc most<br>
of the time, so please do not feel that you need to wait for an<br>
office hour time to pose a question or offer a suggestion. You can<br>
use the string "tc-members" to alert the members to your question.<br>
<br>
You will find channel logs with past conversations at<br>
<a href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/" rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/irclogs/%23openstack-tc/</a><br>
<br>
If you expect your topic to require significant discussion or to<br>
need input from members of the community other than the TC, please<br>
start a mailing list discussion on openstack-discuss at<br>
<a href="http://lists.openstack.org" rel="noreferrer" target="_blank">lists.openstack.org</a><br>
and use the subject tag "[tc]" to bring it to the attention of TC<br>
members.<br>
<br>
-- <br>
Doug<br>
<br>
</blockquote></div></div>