<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>TC Members,<br>
<br>
Our next meeting will be this Thursday, 6 June at 1400 UTC in #openstack-tc.</p>
<p>Since there has not been a TC meeting for some time, the last suggested meeting agenda has been erased in favor of focusing on post-PTG and forum content. You will find the outlined agenda below. Any suggestions, please contact me before COB (relative to
local time) on Wednesday 5 June.</p>
<p>This email contains the agenda for the meeting, based on the content of the wiki [0].<br>
<br>
If you will not be able to attend, please include your name in the "Apologies for Absence" section of the wiki page [0].<br>
<br>
[0] <a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee">
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee</a> <br>
<br>
* Review Denver PTG</p>
<p>All items are from the PTG etherpad at [1]<br>
</p>
<p>** Changes to the health check process. The suggestion was to remove the formality of "health checks" and focus on TC members being liaisons to projects in an effort to help manage a project's health (if required). We need to assign TC members to teams on
the project team page. fungi offered to update the wiki, and asettle offered to update the ML on this change once the wiki was updated. See more action items on line 62 of the etherpad.<br>
</p>
<p>** Evolution of the help-most-needed list - this was discussed and decided to become an uncapped list, adding docs surrounding annual re-submission for items. We will go through the action items on this list (line 84 of the etherpad). Business cases requiring
updates. <br>
</p>
<p>** Goal selection is changing. The way goals are being selected for the upcoming release will change. For Train, we will work on socialising the idea of proposing goals that are OpenStack-wide, but not tech-heavy. The new goal selection process splits the
goals into "goal" and "implementation". Further details at the meeting. See line 101 of the etherpad for action items.</p>
<p>** Pop-up teams have been officially recognised and implemented into governance thanks to ttx. Please review his patch here [2]</p>
<p>** SIG governance is being defined (ricolin and asettle). See line 137 for action items. Will detail further at meeting.</p>
<p>** Python 3 check in. Finalising the migration (mugsie)</p>
<p>** Leaderless projects are becoming a concern - action items were on line 185 of the etherpad. Suggestions include reworking the documentation around the current role of the PTL and providing tips on how to "be a better PTL" and offering shadowing and mentoring
for potential candidates. This all needs to be socialised further.</p>
<p>** Kickstarting innovation in Openstack - Zane proposed a zany (har har har) suggestion regarding a new multi-tenant cloud with ironic/neutron/optionally cinder/keytstone/octavia (vision will be completed with k8s on top of OpenStack). Suggestion was for
new white paper written by zaneb and mnaser.</p>
<p>** Deleting all the things! [3] See line 234 for action items (mugsie).<br>
</p>
<p>[1] <a href="https://etherpad.openstack.org/p/tc-train-ptg">https://etherpad.openstack.org/p/tc-train-ptg</a><br>
[2] <a href="https://review.opendev.org/#/c/661356/">https://review.opendev.org/#/c/661356/
<br>
<u><font color="#000000">[3]</font></u> https://memegenerator.net/img/instances/14634311.jpg<br>
</a></p>
<p>* Review Denver Forum</p>
** Forum session planning for the next summit as this one was done rather hastily and we missed a few things (such as a goals session). See action items on line 243 of the PTG etherpad [1]<br>
<p>* Other</p>
<p>** Socialising successbot and thanksbot. Get to it, team!<br>
</p>
<p>Cheers,<br>
</p>
<p>Alex</p>
<p>p.s - I have a well known habit for getting meeting agenda's HORRIBLY wrong every time, so feel free to ping a gal and tell her what you know.
<br>
</p>
<p><br>
</p>
</body>
</html>