[Openstack-operators] [all] Naming the T release of OpenStack
Zhipeng Huang
zhipengh512 at gmail.com
Thu Oct 18 15:46:12 UTC 2018
Just do a vote as usual, train is a great candidate :)
On Thu, Oct 18, 2018 at 11:44 PM Melvin Hillsman <mrhillsman at gmail.com>
wrote:
> I agree with Anita and wonder why Train did not meet the criteria? If
> there is no way for Train to be an option outside of killing the voting,
> than for the sake of integrity of processes which I have heard quite a few
> people hold close to we should drop Train from the list. It is an
> unfortunate thing in my view because I am actually a "non-developer" who
> agreed during the feedback session that Train would be a great name but
> Anita is right on this one imho.
>
> On Thu, Oct 18, 2018 at 10:32 AM Anita Kuno <anteaya at anteaya.info> wrote:
>
>> On 2018-10-18 2:35 a.m., 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
>> >
>> > 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
>>
>> I stand in opposition to any action that further undermines democracy.
>>
>> I have avoided events in Denver lately for this reason.
>>
>> If the support for Train is as universal as is portrayed, the poll with
>> show us that.
>>
>> I don't care what the name is. I do want to participate in the
>> selection. The method of participating has heretofore been a poll. I
>> have seen no convincing argument to abandon the use of a poll now.
>>
>> I stand for what democracy there remains. I would like to participate in
>> a poll.
>>
>> Thank you, Anita
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> --
> Kind regards,
>
> Melvin Hillsman
> mrhillsman at gmail.com
> mobile: (832) 264-2646
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard & Patent/IT Product Line
Huawei Technologies Co,. Ltd
Email: huangzhipeng at huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen
(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipengh at uci.edu
Office: Calit2 Building Room 2402
OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20181018/4b4a4664/attachment.html>
More information about the OpenStack-operators
mailing list