Open Stack

On 10/18/2018 8:29 AM, Neil Jerram wrote:
> FWIW, I've have no clue if this is serious or not, or what 'Train' 
> refers to...
>
Neil,

The two Project Team Gathering events in Denver were held at a hotel 
next to the train line from downtown to the airport.  The crossing 
signals there had some sort of malfunction in the past causing them to 
not stop the cars when a train was coming properly.  As a result the 
trains were required to blow their horns when passing through that 
area.  Obviously staying in a hotel, by trains that are blowing their 
horns 24/7 was less than ideal.  As a result, many jokes popped up about 
Denver and trains.

When OpenStack developers think Denver, we think Trains.  :-)

Jay
>
> On Thu, Oct 18, 2018 at 2:25 PM Jay S Bryant <jungleboyj at gmail.com 
> <mailto:jungleboyj at gmail.com>> wrote:
>
>     On 10/18/2018 1:35 AM, Tony Breeds wrote:
>
>>     Hello all,
>>          As per [1] the nomination period for names for the T release have
>>     now closed (actually 3 days ago sorry).  The nominated names and any
>>     qualifying remarks can be seen at2].
>>
>>     Proposed Names
>>       * Tarryall
>>       * Teakettle
>>       * Teller
>>       * Telluride
>>       * Thomas
>>       * Thornton
>>       * Tiger
>>       * Tincup
>>       * Timnath
>>       * Timber
>>       * Tiny Town
>>       * Torreys
>>       * Trail
>>       * Trinidad
>>       * Treasure
>>       * Troublesome
>>       * Trussville
>>       * Turret
>>       * Tyrone
>>
>>     Proposed Names that do not meet the criteria
>>       * Train
>>
>>     However I'd like to suggest we skip the CIVS poll and select 'Train' as
>>     the release name by TC resolution[3].  My think for this is
>>
>>       * It's fun and celebrates a humorous moment in our community
>>       * As a developer I've heard the T release called Train for quite
>>         sometime, and was used often at the PTG[4].
>>       * As the *next* PTG is also in Colorado we can still choose a
>>         geographic based name for U[5]
>>       * If train causes a problem for trademark reasons then we can always
>>         run the poll
>     +2 +W  Great names proposed above but based on other discussions
>     with people I think the community would be happy with the Train
>     name.  Plus if people ask about it, it gives us an opportunity to
>     share a story that gives insight into the community we are.  :-) 
>     Thanks for proposing that path Tony!
>
>     Jay
>>     I'll leave[3] for marked -W for a week for discussion to happen before the
>>     TC can consider / vote on it.
>>
>>     Yours Tony.
>>
>>     [1]http://lists.openstack.org/pipermail/openstack-dev/2018-September/134995.html
>>     [2]https://wiki.openstack.org/wiki/Release_Naming/T_Proposals
>>     [3]https://review.openstack.org/#/q/I0d8d3f24af0ee8578712878a3d6617aad1e55e53
>>     [4]https://twitter.com/vkmc/status/1040321043959754752
>>     [5]https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T–Z
>>     <https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T%E2%80%93Z>
>>
>>
>>     __________________________________________________________________________
>>     OpenStack Development Mailing List (not for usage questions)
>>     Unsubscribe:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>     <mailto:OpenStack-dev-request at lists.openstack.org?subject:unsubscribe>
>>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>     __________________________________________________________________________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe:
>     OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>     <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181018/40f7b416/attachment.html>