Mailing List Archive: [all] Naming the T release of OpenStack

[all] Naming the T release of OpenStack

Oct 17, 2018, 11:35 PM

Post #1 of 9 (968 views)

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

Re: [all] Naming the T release of OpenStack [ In reply to ]

anteaya at anteaya

Oct 18, 2018, 8:31 AM

Post #2 of 9 (967 views)

Permalink

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@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-sigs] [all] Naming the T release of OpenStack [ In reply to ]

openstack at medberry

Oct 18, 2018, 8:39 AM

Post #3 of 9 (967 views)

Permalink

I'm fine with Train but I'm also fine with just adding it to the list and
voting on it. It will win.

Also, for those not familiar with the debian/ubuntu command "sl", now is
the time to become so.

apt install sl
sl -Flea #ftw

On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds <tony@bakeyournoodle.com>
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
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>

Re: [Openstack-sigs] [all] Naming the T release of OpenStack [ In reply to ]

openstack at medberry

Oct 18, 2018, 8:41 AM

Post #4 of 9 (967 views)

Permalink

and any talks I give in Denver (Forum, Ops, Main) will include "sl". It's
handy in a variety of ways.

On Thu, Oct 18, 2018 at 9:39 AM David Medberry <openstack@medberry.net>
wrote:

> I'm fine with Train but I'm also fine with just adding it to the list and
> voting on it. It will win.
>
> Also, for those not familiar with the debian/ubuntu command "sl", now is
> the time to become so.
>
> apt install sl
> sl -Flea #ftw
>
> On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds <tony@bakeyournoodle.com>
> 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
>> _______________________________________________
>> openstack-sigs mailing list
>> openstack-sigs@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>>
>

Re: [all] Naming the T release of OpenStack [ In reply to ]

mrhillsman at gmail

Oct 18, 2018, 8:43 AM

Post #5 of 9 (967 views)

Permalink

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@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@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>

--
Kind regards,

Melvin Hillsman
mrhillsman@gmail.com
mobile: (832) 264-2646

Re: [all] Naming the T release of OpenStack [ In reply to ]

zhipengh512 at gmail

Oct 18, 2018, 8:46 AM

Post #6 of 9 (967 views)

Permalink

Just do a vote as usual, train is a great candidate :)

On Thu, Oct 18, 2018 at 11:44 PM Melvin Hillsman <mrhillsman@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@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@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> --
> Kind regards,
>
> Melvin Hillsman
> mrhillsman@gmail.com
> mobile: (832) 264-2646
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators@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@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipengh@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado

Re: [all] Naming the T release of OpenStack [ In reply to ]

iain.macdonnell at oracle

Oct 18, 2018, 8:47 AM

Post #7 of 9 (967 views)

Permalink

On 10/18/2018 08:31 AM, Anita Kuno wrote:
> On 2018-10-18 2:35 a.m., Tony Breeds wrote:
...
>> 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.
>
> 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.

+1

... and if you're not going to use the nominations, don't waste people's
time asking for submissions.

I'm not super-fond of Train, since "release train" means something
(else), at least in some contexts...

~iain

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-sigs] [all] Naming the T release of OpenStack [ In reply to ]

openstack at fried

Oct 18, 2018, 9:43 AM

Post #8 of 9 (967 views)

Permalink

Sorry, I'm opposed to this idea.

I admit I don't understand the political framework, nor have I read the
governing documents beyond [1], but that document makes it clear that
this is supposed to be a community-wide vote. Is it really legal for
the TC (or whoever has merge rights on [2]) to merge a patch that gives
that same body the power to take the decision out of the hands of the
community? So it's really an oligarchy that gives its constituency the
illusion of democracy until something comes up that it feels like not
having a vote on? The fact that it's something relatively "unimportant"
(this time) is not a comfort.

Not that I think the TC would necessarily move forward with [2] in the
face of substantial opposition from non-TC "cores" or whatever.

I will vote enthusiastically for "Train". But a vote it should be.

-efried

[1] https://governance.openstack.org/tc/reference/release-naming.html
[2] https://review.openstack.org/#/c/611511/

On 10/18/2018 10:52 AM, Arkady.Kanevsky@dell.com wrote:
> +1 for the poll.
>
> Let’s follow well established process.
>
> If we want to add Train as one of the options for the name I am OK with it.
>
>
>
> *From:* Jonathan Mills <jonmills@gmail.com>
> *Sent:* Thursday, October 18, 2018 10:49 AM
> *To:* openstack-sigs@lists.openstack.org
> *Subject:* Re: [Openstack-sigs] [all] Naming the T release of OpenStack
>
>
>
> [EXTERNAL EMAIL]
> Please report any suspicious attachments, links, or requests for
> sensitive information.
>
> +1 for just having a poll
>
>
>
> On Thu, Oct 18, 2018 at 11:39 AM David Medberry <openstack@medberry.net
> <mailto:openstack@medberry.net>> wrote:
>
> I'm fine with Train but I'm also fine with just adding it to the
> list and voting on it. It will win.
>
>
>
> Also, for those not familiar with the debian/ubuntu command "sl",
> now is the time to become so.
>
>
>
> apt install sl
>
> sl -Flea #ftw
>
>
>
> On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds
> <tony@bakeyournoodle.com <mailto:tony@bakeyournoodle.com>> 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
> <https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T%E2%80%93Z>
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs@lists.openstack.org
> <mailto:openstack-sigs@lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs@lists.openstack.org
> <mailto:openstack-sigs@lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>
>
>
> _______________________________________________
> openstack-sigs mailing list
> openstack-sigs@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
>

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-sigs] [all] Naming the T release of OpenStack [ In reply to ]

tony at bakeyournoodle

Oct 19, 2018, 2:54 AM

Post #9 of 9 (966 views)

Permalink

On Thu, Oct 18, 2018 at 05:35:39PM +1100, 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

I have re-worked my openstack/governance change[1] to ask the TC to accept
adding Train to the poll as (partially) described in [2].

I present the names above to the community and Foundation marketing team
for consideration. The list above does contain Train, clearly if the TC
do not approve [1] Train will not be included in the poll when created.

I apologise for any offence or slight caused by my previous email in
this thread. It was well intentioned albeit, with hindsight, poorly
thought through.

Yours Tony.

[1] https://review.openstack.org/#/c/611511/
[2] https://governance.openstack.org/tc/reference/release-naming.html#release-name-criteria

Mailing List Archive

Attached Files:

Attached Files: