<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Here is the link to the session in case you'd like to add it to
your schedule [0].<br>
<br>
[0]
<a class="moz-txt-link-freetext" href="https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21759/openstack-is-mature-time-to-get-serious-on-maintainers">https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21759/openstack-is-mature-time-to-get-serious-on-maintainers</a></tt><br>
<br>
<div class="moz-cite-prefix">On 05/17/2018 07:55 PM, Rochelle Grober
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DA7681A6D234954992BD2FB907F966620BC53D72@sjceml521-mbx.china.huawei.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal">Folks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">TL;DR<o:p></o:p></p>
<p class="MsoNormal">The last session related to extended
releases is: <span
style="font-size:10.5pt;font-family:"Arial Unicode
MS",sans-serif;color:#333333;background:white">
OpenStack is "mature" -- time to get serious on Maintainers<br>
It will be in room 220 at 11:00-11:40</span><o:p></o:p></p>
<p class="MsoNormal">The etherpad for the last session in the
series on Extended releases is here:<o:p></o:p></p>
<p class="MsoNormal"><a
href="https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3"
moz-do-not-send="true">https://etherpad.openstack.org/p/YVR-openstack-maintainers-maint-pt3</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are links to info on other
communities’ maintainer process/role/responsibilities also, as
reference material on how other have made it work (or not).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The nitty gritty details:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The upcoming Forum is filled with sessions
that are focused on issues needed to improve and maintain the
sustainability of OpenStack projects for the long term. We
have discussion on reducing technical debt, extended releases,
fast forward installs, bringing Ops and User communities
closer together, etc. The community is showing it is now
invested in activities that are often part of “Sustaining
Engineering” teams (corporate speak) or “Maintainers (OSS
speak). We are doing this; we are thinking about the moving
parts to do this; let’s think about the contributors who want
to do these and bring some clarity to their roles and the
processes they need to be successful. I am hoping you read
this and keep these ideas in mind as you participate in the
various Forum sessions. Then you can bring the ideas
generated during all these discussions to the Maintainers
session near the end of the Summit to brainstorm how to
visualize and define this new(ish) component of our technical
community.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, who has been doing the maintenance work
so far? Mostly (mostly) unsung heroes like the Stable Release
team, Release team, Oslo team, project liaisons and the
community goals champions (yes, moving to py3 is a
sustaining/maintenance type of activity). And some operators
(Hi, mnaser!). We need to lean on their experience and what
we think the community will need to reduce that technical debt
to outline what the common tasks of maintainers should be,
what else might fall in their purview, and how to partner with
them to better serve them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With API lower limits, new tool versions,
placement, py3, and even projects reaching “code complete” or
“maintenance mode,” there is a lot of work for maintainers to
do (I really don’t like that term, but is there one that fits
OpenStack’s community?). It would be great if we could find a
way to share the load such that we can have part time
contributors here. We know that operators know how to
cherrypick, test in there clouds, do bug fixes. How do we
pair with them to get fixes upstreamed without requiring them
to be full on developers? We have a bunch of alumni who have
stopped being “cores” and sometimes even developers, but who
love our community and might be willing and able to put in a
few hours a week, maybe reviewing small patches, providing
help with user/ops submitted patch requests, or whatever.
They were trusted with +2 and +W in the past, so we should at
least be able to trust they know what they know. We would
need some way to identify them to Cores, since they would be
sort of 1.5 on the voting scale, but……<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, burn out is high in other communities
for maintainers. We need to find a way to make sustaining the
stable parts of OpenStack sustainable.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hope you can make the talk, or add to the
etherpad, or both. The etherpad is very musch still a work in
progress (trying to organize it to make sense). If you want
to jump in now, go for it, otherwise it should be in
reasonable shape for use at the session. I hope we get a good
mix of community and a good collection of those who are
already doing the job without title.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks and see you next week.<o:p></o:p></p>
<p class="MsoNormal">--rocky<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" style="text-align:center" align="center">
<hr width="100%" size="1" align="center">
</div>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:SimSun">华为技术有限公司 Huawei
Technologies Co., Ltd.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:SimSun"><img
id="Picture_x0020_2"
src="cid:part2.EBC97C01.860D8475@gmail.com"
alt="Company_logo" class="" width="102" border="0"
height="32"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:SimSun">Rochelle Grober<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:SimSun">Sr. Staff Architect,
Open Source<br>
Office Phone:408-330-5472<br>
<a class="moz-txt-link-abbreviated" href="mailto:Email:rochelle.grober@huawei.com">Email:rochelle.grober@huawei.com</a><o:p></o:p></span></p>
<div class="MsoNormal" style="text-align:center" align="center"><span
style="font-size:12.0pt;font-family:SimSun">
<hr width="100%" size="1" align="center">
</span></div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"></span><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:ZH-CN">
</span><span
style="font-size:7.5pt;font-family:SimSun;color:gray;mso-fareast-language:ZH-CN"
lang="ZH-CN">本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁</span><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:ZH-CN"><br>
</span><span
style="font-size:7.5pt;font-family:SimSun;color:gray;mso-fareast-language:ZH-CN"
lang="ZH-CN">止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中</span><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:ZH-CN"><br>
</span><span
style="font-size:7.5pt;font-family:SimSun;color:gray;mso-fareast-language:ZH-CN"
lang="ZH-CN">的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！</span><span
style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:ZH-CN"><br>
This e-mail and its attachments contain confidential
information from HUAWEI, which
<br>
is intended only for the person or entity whose address is
listed above. Any use of the
<br>
information contained herein in any way (including, but not
limited to, total or partial
<br>
disclosure, reproduction, or dissemination) by persons other
than the intended <br>
recipient(s) is prohibited. If you receive this e-mail in
error, please notify the sender by
<br>
phone or email immediately and delete it!</span><span
style="font-size:12.0pt;font-family:SimSun;mso-fareast-language:ZH-CN"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
User-committee mailing list
<a class="moz-txt-link-abbreviated" href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a>
</pre>
</blockquote>
<br>
</body>
</html>