<div dir="ltr">I'm fine with Train but I'm also fine with just adding it to the list and voting on it. It will win.<div><br></div><div>Also, for those not familiar with the debian/ubuntu command "sl", now is the time to become so.</div><div><br></div><div>apt install sl</div><div>sl -Flea #ftw</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds <<a href="mailto:tony@bakeyournoodle.com">tony@bakeyournoodle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all,<br>
As per [1] the nomination period for names for the T release have<br>
now closed (actually 3 days ago sorry). The nominated names and any<br>
qualifying remarks can be seen at2].<br>
<br>
Proposed Names<br>
* Tarryall<br>
* Teakettle<br>
* Teller<br>
* Telluride<br>
* Thomas<br>
* Thornton<br>
* Tiger<br>
* Tincup<br>
* Timnath<br>
* Timber<br>
* Tiny Town<br>
* Torreys<br>
* Trail<br>
* Trinidad<br>
* Treasure<br>
* Troublesome<br>
* Trussville<br>
* Turret<br>
* Tyrone<br>
<br>
Proposed Names that do not meet the criteria<br>
* Train<br>
<br>
However I'd like to suggest we skip the CIVS poll and select 'Train' as<br>
the release name by TC resolution[3]. My think for this is <br>
<br>
* It's fun and celebrates a humorous moment in our community<br>
* As a developer I've heard the T release called Train for quite<br>
sometime, and was used often at the PTG[4].<br>
* As the *next* PTG is also in Colorado we can still choose a<br>
geographic based name for U[5]<br>
* If train causes a problem for trademark reasons then we can always<br>
run the poll<br>
<br>
I'll leave[3] for marked -W for a week for discussion to happen before the<br>
TC can consider / vote on it.<br>
<br>
Yours Tony.<br>
<br>
[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2018-September/134995.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2018-September/134995.html</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Release_Naming/T_Proposals" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Release_Naming/T_Proposals</a><br>
[3] <a href="https://review.openstack.org/#/q/I0d8d3f24af0ee8578712878a3d6617aad1e55e53" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/I0d8d3f24af0ee8578712878a3d6617aad1e55e53</a><br>
[4] <a href="https://twitter.com/vkmc/status/1040321043959754752" rel="noreferrer" target="_blank">https://twitter.com/vkmc/status/1040321043959754752</a><br>
[5] <a href="https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T%E2%80%93Z" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T–Z</a><br>
_______________________________________________<br>
openstack-sigs mailing list<br>
<a href="mailto:openstack-sigs@lists.openstack.org" target="_blank">openstack-sigs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs</a><br>
</blockquote></div>