<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=utf-8">
<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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">So are we formally announcing <a href="https://en.wikipedia.org/wiki/Xanadu">
<b><span style="font-size:12.0pt;font-family:"Verdana",sans-serif;color:#338899">Xanadu</span></b></a> as the next release name?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Sean McGinnis <sean.mcginnis@gmx.com> <br>
<b>Sent:</b> Thursday, December 10, 2020 10:53 AM<br>
<b>To:</b> openstack-discuss<br>
<b>Subject:</b> [TC][all] X Release name polling<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p><span style="color:#CE1126">[EXTERNAL EMAIL] <o:p></o:p></span></p>
</div>
<p>Hey everyone,<o:p></o:p></p>
<p>We recently collected naming suggestions for the X release name. A lot of great suggestions by the community! Much more than I had expected for this letter.<o:p></o:p></p>
<p>As a reminder, starting with the W release we had changed the process for selecting the name [1]. We collected suggestions from the community, then the members of the TC voted in a poll [2] to select which name(s) out of the suggestions to go with. The vetting
of the top choices from that process is happening now, and we should have a official result soon.<o:p></o:p></p>
<p>This is a bit of a mea culpa from me about an issue with how this was conducted though. The naming process specifically states: "<span style="font-size:10.5pt;color:#333333;background:white">the poll should be run in a manner that allows members of the community
to see what each TC member voted for.</span>" When I set up the CIVS poll, I failed to check the box that would allow seeing the detailed results of the poll. So while we do have the winning names, we are not able to see which TC members voted and how. I apologize
for missing this step (and I've noted that we really should add some detailed process for future coordinators to follow!).<o:p></o:p></p>
<p>I believe the intent with that part of the process was to allow the community to see how your elected TC members voted as one factor to consider when reelecting anyone. Also transparency to show that no one is pushing through their own choices, circumventing
any process.<o:p></o:p></p>
<p>The two options I see at this point would be to either redo the entire naming poll, or just try to capture what TC members voted for somewhere so we have a record of that.<o:p></o:p></p>
<p>It's been long enough now since taking the poll that I don't expect TC members to remember exactly how they ranked things. But we've also started the vetting process through the Foundation (lawyers engaged, etc) so I'd really rather not start over if we
can avoid it. If TC members could respond here with what they remember voting for, I hope that is enough to satisfy the spirit of the defined process.<o:p></o:p></p>
<p>If there are any members of the community that have a strong objection to this, please say so. I leave it up to the TC then to decide how to proceed.<o:p></o:p></p>
<p>Again, apologies for missing this step. Otherwise, I think the process has worked well, and I hope we can declare an official X name shortly.<o:p></o:p></p>
<p>Thanks!<o:p></o:p></p>
<p>Sean<o:p></o:p></p>
<p>[1] <a href="https://governance.openstack.org/tc/reference/release-naming.html#release-naming-process">
https://governance.openstack.org/tc/reference/release-naming.html#release-naming-process</a><br>
[2] <a href="https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e6e96070af39fe7">
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e6e96070af39fe7</a><o:p></o:p></p>
</div>
</body>
</html>