<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Hello!</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Continuing the transparency theme since that was a big part of why we were okay with just the TC voting. </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">I voted for Xenon in first and I *think* I put Xerxes as second and left the rest at the default lowest value. </div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">-Kendall (diablo_rojo)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 10, 2020 at 10:08 AM Jay Bryant <<a href="mailto:jungleboyj@gmail.com">jungleboyj@gmail.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">
<div>
<p>Sean,</p>
<p>I echo the other TC members in thanks for you leading up this
process and doing it with transparency! <br>
</p>
<p>I voted for three top options, I believe, leaving the rest ranked
as 30th. I believe they were:</p>
<p> 1. Xenoblast</p>
<p> 2. Xenomorph</p>
<p> 3. Xenith</p>
<p>Why not Xanadu from me, people may ask? Well, honestly, because
I didn't want the song stuck in my head for 6 months.</p>
<p>Thanks!</p>
<p>Jay</p>
<p><br>
</p>
<div>On 12/10/2020 10:53 AM, Sean McGinnis
wrote:<br>
</div>
<blockquote type="cite">
<p>Hey everyone,</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.</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.</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="color:rgb(51,51,51);font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">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!).</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.</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.</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.</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.</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.</p>
<p>Thanks!</p>
<p>Sean<br>
</p>
<p>[1]
<a href="https://governance.openstack.org/tc/reference/release-naming.html#release-naming-process" target="_blank">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" target="_blank">https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_7e6e96070af39fe7</a><br>
</p>
</blockquote>
</div>
</blockquote></div>