<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Hi Team,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I'd like to announce my candidacy to continue as the OpenStack-Helm PTL<o:p></o:p></p>
<p class="MsoPlainText">for the Rocky cycle.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I have been working in the OpenStack community for about a year and a half,<o:p></o:p></p>
<p class="MsoPlainText">helping lead upstream development efforts for my employer. In this capacity<o:p></o:p></p>
<p class="MsoPlainText">I worked to bring new OpenStack contributors up to speed, help them understand<o:p></o:p></p>
<p class="MsoPlainText">and keep them aligned to community goals, and to be the voice of community and<o:p></o:p></p>
<p class="MsoPlainText">upstream-first development within my workplace. More recently I have had the<o:p></o:p></p>
<p class="MsoPlainText">privilege of taking a more hands-on role with OpenStack-Helm, and have served<o:p></o:p></p>
<p class="MsoPlainText">as PTL as it transitioned to become an Official OpenStack project.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">OpenStack-Helm is a technically impressive project, and has the potential to<o:p></o:p></p>
<p class="MsoPlainText">not only redefine how OpenStack clouds are deployed and operated, but also to<o:p></o:p></p>
<p class="MsoPlainText">help redefine what it means to be an OpenStack cloud, by allowing simple<o:p></o:p></p>
<p class="MsoPlainText">stitching together of OpenStack and third-party components into custom<o:p></o:p></p>
<p class="MsoPlainText">solutions. However, the reason OpenStack-Helm is successful is because of a<o:p></o:p></p>
<p class="MsoPlainText">passionate team of talented engineers who work tirelessly to push the boundary<o:p></o:p></p>
<p class="MsoPlainText">of what's possible with containerized technology. I'm humbled daily by<o:p></o:p></p>
<p class="MsoPlainText">this team, and a key goal of mine in the Rocky cycle is to enable you, help<o:p></o:p></p>
<p class="MsoPlainText">you succeed, and grow your ranks. I see PTL as a servant leader role.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">In the Rocky release I would like to accomplish the following:<o:p></o:p></p>
<p class="MsoPlainText">* Cut our 1.0 OpenStack-Helm release<o:p></o:p></p>
<p class="MsoPlainText">* Build the skills and experience of the existing OpenStack-Helm team members<o:p></o:p></p>
<p class="MsoPlainText">* Create mentoring/onboarding opportunities to onboard new team members quickly<o:p></o:p></p>
<p class="MsoPlainText">* Build gates for Ocata and begin to ensure compatibility with Pike and Queens<o:p></o:p></p>
<p class="MsoPlainText">* Develop and formalize our plans for OpenStack-Helm releases<o:p></o:p></p>
<p class="MsoPlainText">* Groom a more diverse core reviewer team<o:p></o:p></p>
<p class="MsoPlainText">* Harden OpenStack-Helm resiliency, scalability, and day 2 ops<o:p></o:p></p>
<p class="MsoPlainText">* Create ops-oriented documentation for OpenStack-Helm<o:p></o:p></p>
<p class="MsoPlainText">* Achieve OpenStack-Helm cross-gating with other projects<o:p></o:p></p>
<p class="MsoPlainText">* Collaborate with other project teams on their charts' development<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thank you for your consideration!<o:p></o:p></p>
<p class="MsoPlainText">Matt McEuen<o:p></o:p></p>
</div>
</body>
</html>