Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Lajos Katona]

Hi,

Thanks, I check via mobile net than.

Regards
Lajos

On 2018. 11. 07. 11:20, Colleen Murphy wrote:
> On Wed, Nov 7, 2018, at 11:12 AM, Lajos Katona wrote:
>> Hi,
>>
>> Maybe I missed something but I got the message: "Already voted
>> A vote has already been cast using your voter key.
>>
>> Poll results will be available only to the following users:
>>
>> t...@bakeyournoodle.com"
>>
>> Could you help me to have a correct link?
> The public polling service limits voting to one vote per IP address. If 
> someone in your office space has already voted, the poll won't let anyone 
> else in the office vote. You need to find a different public IP address to 
> vote from, either by tunneling through a proxy or physically going somewhere 
> else with a different network.
>
> Colleen
>
>> Regards
>> Lajos
>>
>> On 2018. 11. 06. 3:19, Tony Breeds wrote:
>>
>>
>> Hi all,
>>
>> Time is running out for you to have your say in the T release name
>> poll.  We have just under 3 days left.  If you haven't voted please do!
>>
>> On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
>>
>>
>> Hi folks,
>>
>> It is time again to cast your vote for the naming of the T Release.
>> As with last time we'll use a public polling option over per user private 
>> URLs
>> for voting.  This means, everybody should proceed to use the following URL to
>> cast their vote:
>>
>>
>> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e
>>
>> We've selected a public poll to ensure that the whole community, not just 
>> gerrit
>> change owners get a vote.  Also the size of our community has grown such 
>> that we
>> can overwhelm CIVS if using private urls.  A public can mean that users
>> behind NAT, proxy servers or firewalls may receive an message saying
>> that your vote has already been lodged, if this happens please try
>> another IP.
>>
>> Because this is a public poll, results will currently be only viewable by 
>> myself
>> until the poll closes. Once closed, I'll post the URL making the results
>> viewable to everybody. This was done to avoid everybody seeing the results 
>> while
>> the public poll is running.
>>
>> The poll will officially end on 2018-11-08 00:00:00+00:00[1], and
>> results will be
>> posted shortly after.
>>
>> [1] https://governance.openstack.org/tc/reference/release-naming.html
>> ---
>>
>> According to the Release Naming Process, this poll is to determine the
>> community preferences for the name of the T release of OpenStack. It is
>> possible that the top choice is not viable for legal reasons, so the second 
>> or
>> later community preference could wind up being the name.
>>
>> Release Name Criteria
>> -
>>
>> Each release name must start with the letter of the ISO basic Latin alphabet
>> following the initial letter of the previous release, starting with the
>> initial release of "Austin". After "Z", the next name should start with
>> "A" again.
>>
>> The name must be composed only of the 26 characters of the ISO basic Latin
>> alphabet. Names which can be transliterated into this character set are also
>> acceptable.
>>
>> The name must refer to the physical or human geography of the region
>> encompassing the location of the OpenStack design summit for the
>> corresponding release. The exact boundaries of the geographic region under
>> consideration must be declared before the opening of nominations, as part of
>> the initiation of the selection process.
>>
>> The name must be a single word with a maximum of 10 characters. Words that
>> describe the feature should not be included, so "Foo City" or "Foo Peak"
>> would both be eligible as "Foo".
>>
>> Names which do not meet these criteria but otherwise sound really cool
>> should be added to a separate section of the wiki page and the TC may make
>> an exception for one or more of them to be considered in the Condorcet poll.
>> The naming official is responsible for presenting the list of exceptional
>> names for consideration to the TC before the poll opens.
>>
>> Exact Geographic Region
>> ---
>>
>> The Geographic Region from where names for the S release will come is 
>> Colorado
>>
>> Proposed Names
>> --
>>
>> * Tarryall
>> * Teakettle
>> * Teller
>> * Telluride
>> * Thomas : the Tank Engine
>> * Thornton
>> * Tiger
>> * Tincup
>> * Timnath
>> * Timber
>> * Tiny Town
>> * Torreys
>> * Trail
>> * Trinidad
>> * Treasure
>> * Troublesome
>> * Trussville
>> * Turret
>> * Tyrone
>>
>> Proposed Names that do not meet the criteria (accepted by the TC)
>> -
>>
>> * Train🚂 : Many Attendees of the first Denver PTG have a story to tell
>> about the trains near the PTG hotel.  We could celebrate those stories
>> with this name
>>
>> Yours Tony.
>>
>>
>>
>>
>>
>>
>>
>> __
>> OpenStack Developmen

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Colleen Murphy]

On Wed, Nov 7, 2018, at 11:12 AM, Lajos Katona wrote:
> Hi,
> 
> Maybe I missed something but I got the message: "Already voted
> A vote has already been cast using your voter key.
> 
> Poll results will be available only to the following users:
> 
> t...@bakeyournoodle.com"
> 
> Could you help me to have a correct link?

The public polling service limits voting to one vote per IP address. If someone 
in your office space has already voted, the poll won't let anyone else in the 
office vote. You need to find a different public IP address to vote from, 
either by tunneling through a proxy or physically going somewhere else with a 
different network.

Colleen

> 
> Regards
> Lajos
> 
> On 2018. 11. 06. 3:19, Tony Breeds wrote:
> 
> 
> Hi all,
> 
>Time is running out for you to have your say in the T release name
> poll.  We have just under 3 days left.  If you haven't voted please do!
> 
> On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
> 
> 
> Hi folks,
> 
> It is time again to cast your vote for the naming of the T Release.
> As with last time we'll use a public polling option over per user private URLs
> for voting.  This means, everybody should proceed to use the following URL to
> cast their vote:
> 
>   
> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e
> 
> We've selected a public poll to ensure that the whole community, not just 
> gerrit
> change owners get a vote.  Also the size of our community has grown such that 
> we
> can overwhelm CIVS if using private urls.  A public can mean that users
> behind NAT, proxy servers or firewalls may receive an message saying
> that your vote has already been lodged, if this happens please try
> another IP.
> 
> Because this is a public poll, results will currently be only viewable by 
> myself
> until the poll closes. Once closed, I'll post the URL making the results
> viewable to everybody. This was done to avoid everybody seeing the results 
> while
> the public poll is running.
> 
> The poll will officially end on 2018-11-08 00:00:00+00:00[1], and 
> results will be
> posted shortly after.
> 
> [1] https://governance.openstack.org/tc/reference/release-naming.html
> ---
> 
> According to the Release Naming Process, this poll is to determine the
> community preferences for the name of the T release of OpenStack. It is
> possible that the top choice is not viable for legal reasons, so the second or
> later community preference could wind up being the name.
> 
> Release Name Criteria
> -
> 
> Each release name must start with the letter of the ISO basic Latin alphabet
> following the initial letter of the previous release, starting with the
> initial release of "Austin". After "Z", the next name should start with
> "A" again.
> 
> The name must be composed only of the 26 characters of the ISO basic Latin
> alphabet. Names which can be transliterated into this character set are also
> acceptable.
> 
> The name must refer to the physical or human geography of the region
> encompassing the location of the OpenStack design summit for the
> corresponding release. The exact boundaries of the geographic region under
> consideration must be declared before the opening of nominations, as part of
> the initiation of the selection process.
> 
> The name must be a single word with a maximum of 10 characters. Words that
> describe the feature should not be included, so "Foo City" or "Foo Peak"
> would both be eligible as "Foo".
> 
> Names which do not meet these criteria but otherwise sound really cool
> should be added to a separate section of the wiki page and the TC may make
> an exception for one or more of them to be considered in the Condorcet poll.
> The naming official is responsible for presenting the list of exceptional
> names for consideration to the TC before the poll opens.
> 
> Exact Geographic Region
> ---
> 
> The Geographic Region from where names for the S release will come is Colorado
> 
> Proposed Names
> --
> 
> * Tarryall
> * Teakettle
> * Teller
> * Telluride
> * Thomas : the Tank Engine
> * Thornton
> * Tiger
> * Tincup
> * Timnath
> * Timber
> * Tiny Town
> * Torreys
> * Trail
> * Trinidad
> * Treasure
> * Troublesome
> * Trussville
> * Turret
> * Tyrone
> 
> Proposed Names that do not meet the criteria (accepted by the TC)
> -
> 
> * Train🚂 : Many Attendees of the first Denver PTG have a story to tell 
> about the trains near the PTG hotel.  We could celebrate those stories 
> with this name
> 
> Yours Tony.
> 
> 
> 
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?
> subject:unsubscribe
> http://lists.openstack.org/cgi-

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Lajos Katona]

Hi,

Maybe I missed something but I got the message: "Already voted
A vote has already been cast using your voter key.

Poll results will be available only to the following users:

t...@bakeyournoodle.com"

Could you help me to have a correct link?

Regards
Lajos

On 2018. 11. 06. 3:19, Tony Breeds wrote:


Hi all,

   Time is running out for you to have your say in the T release name
poll.  We have just under 3 days left.  If you haven't voted please do!

On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:


Hi folks,

It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting.  This means, everybody should proceed to use the following URL to
cast their vote:

  
https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e

We've selected a public poll to ensure that the whole community, not just gerrit
change owners get a vote.  Also the size of our community has grown such that we
can overwhelm CIVS if using private urls.  A public can mean that users
behind NAT, proxy servers or firewalls may receive an message saying
that your vote has already been lodged, if this happens please try
another IP.

Because this is a public poll, results will currently be only viewable by myself
until the poll closes. Once closed, I'll post the URL making the results
viewable to everybody. This was done to avoid everybody seeing the results while
the public poll is running.

The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will 
be
posted shortly after.

[1] https://governance.openstack.org/tc/reference/release-naming.html
---

According to the Release Naming Process, this poll is to determine the
community preferences for the name of the T release of OpenStack. It is
possible that the top choice is not viable for legal reasons, so the second or
later community preference could wind up being the name.

Release Name Criteria
-

Each release name must start with the letter of the ISO basic Latin alphabet
following the initial letter of the previous release, starting with the
initial release of "Austin". After "Z", the next name should start with
"A" again.

The name must be composed only of the 26 characters of the ISO basic Latin
alphabet. Names which can be transliterated into this character set are also
acceptable.

The name must refer to the physical or human geography of the region
encompassing the location of the OpenStack design summit for the
corresponding release. The exact boundaries of the geographic region under
consideration must be declared before the opening of nominations, as part of
the initiation of the selection process.

The name must be a single word with a maximum of 10 characters. Words that
describe the feature should not be included, so "Foo City" or "Foo Peak"
would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may make
an exception for one or more of them to be considered in the Condorcet poll.
The naming official is responsible for presenting the list of exceptional
names for consideration to the TC before the poll opens.

Exact Geographic Region
---

The Geographic Region from where names for the S release will come is Colorado

Proposed Names
--

* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas : the Tank Engine
* Thornton
* Tiger
* Tincup
* Timnath
* Timber
* Tiny Town
* Torreys
* Trail
* Trinidad
* Treasure
* Troublesome
* Trussville
* Turret
* Tyrone

Proposed Names that do not meet the criteria (accepted by the TC)
-

* Train🚂 : Many Attendees of the first Denver PTG have a story to tell about 
the trains near the PTG hotel.  We could celebrate those stories with this name

Yours Tony.







__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



Yours Tony.




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Tony Breeds]

Hi all,

   Time is running out for you to have your say in the T release name
poll.  We have just under 3 days left.  If you haven't voted please do!

On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
> Hi folks,
> 
> It is time again to cast your vote for the naming of the T Release.
> As with last time we'll use a public polling option over per user private URLs
> for voting.  This means, everybody should proceed to use the following URL to
> cast their vote:
> 
>   
> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e
> 
> We've selected a public poll to ensure that the whole community, not just 
> gerrit
> change owners get a vote.  Also the size of our community has grown such that 
> we
> can overwhelm CIVS if using private urls.  A public can mean that users
> behind NAT, proxy servers or firewalls may receive an message saying
> that your vote has already been lodged, if this happens please try
> another IP.
> 
> Because this is a public poll, results will currently be only viewable by 
> myself
> until the poll closes. Once closed, I'll post the URL making the results
> viewable to everybody. This was done to avoid everybody seeing the results 
> while
> the public poll is running.
> 
> The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results 
> will be
> posted shortly after.
> 
> [1] https://governance.openstack.org/tc/reference/release-naming.html
> ---
> 
> According to the Release Naming Process, this poll is to determine the
> community preferences for the name of the T release of OpenStack. It is
> possible that the top choice is not viable for legal reasons, so the second or
> later community preference could wind up being the name.
> 
> Release Name Criteria
> -
> 
> Each release name must start with the letter of the ISO basic Latin alphabet
> following the initial letter of the previous release, starting with the
> initial release of "Austin". After "Z", the next name should start with
> "A" again.
> 
> The name must be composed only of the 26 characters of the ISO basic Latin
> alphabet. Names which can be transliterated into this character set are also
> acceptable.
> 
> The name must refer to the physical or human geography of the region
> encompassing the location of the OpenStack design summit for the
> corresponding release. The exact boundaries of the geographic region under
> consideration must be declared before the opening of nominations, as part of
> the initiation of the selection process.
> 
> The name must be a single word with a maximum of 10 characters. Words that
> describe the feature should not be included, so "Foo City" or "Foo Peak"
> would both be eligible as "Foo".
> 
> Names which do not meet these criteria but otherwise sound really cool
> should be added to a separate section of the wiki page and the TC may make
> an exception for one or more of them to be considered in the Condorcet poll.
> The naming official is responsible for presenting the list of exceptional
> names for consideration to the TC before the poll opens.
> 
> Exact Geographic Region
> ---
> 
> The Geographic Region from where names for the S release will come is Colorado
> 
> Proposed Names
> --
> 
> * Tarryall
> * Teakettle
> * Teller
> * Telluride
> * Thomas : the Tank Engine
> * Thornton
> * Tiger
> * Tincup
> * Timnath
> * Timber
> * Tiny Town
> * Torreys
> * Trail
> * Trinidad
> * Treasure
> * Troublesome
> * Trussville
> * Turret
> * Tyrone
> 
> Proposed Names that do not meet the criteria (accepted by the TC)
> -
> 
> * Train🚂 : Many Attendees of the first Denver PTG have a story to tell about 
> the trains near the PTG hotel.  We could celebrate those stories with this 
> name
> 
> Yours Tony.



> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Tony Breeds]

On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote:
> I must be losing it. On what planet is "Tiny Town" a single word, and
> "Troublesome" not more than 10 characters?

Sorry for the mistake.  Should either of these names win the popular
vote clearly they would not be viable.

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[iain macdonnell]

I must be losing it. On what planet is "Tiny Town" a single word, and
"Troublesome" not more than 10 characters?

~iain


On Mon, Oct 29, 2018 at 10:41 PM Tony Breeds  wrote:
>
> Hi folks,
>
> It is time again to cast your vote for the naming of the T Release.
> As with last time we'll use a public polling option over per user private URLs
> for voting.  This means, everybody should proceed to use the following URL to
> cast their vote:
>
>   
> https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e
>
> We've selected a public poll to ensure that the whole community, not just 
> gerrit
> change owners get a vote.  Also the size of our community has grown such that 
> we
> can overwhelm CIVS if using private urls.  A public can mean that users
> behind NAT, proxy servers or firewalls may receive an message saying
> that your vote has already been lodged, if this happens please try
> another IP.
>
> Because this is a public poll, results will currently be only viewable by 
> myself
> until the poll closes. Once closed, I'll post the URL making the results
> viewable to everybody. This was done to avoid everybody seeing the results 
> while
> the public poll is running.
>
> The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results 
> will be
> posted shortly after.
>
> [1] https://governance.openstack.org/tc/reference/release-naming.html
> ---
>
> According to the Release Naming Process, this poll is to determine the
> community preferences for the name of the T release of OpenStack. It is
> possible that the top choice is not viable for legal reasons, so the second or
> later community preference could wind up being the name.
>
> Release Name Criteria
> -
>
> Each release name must start with the letter of the ISO basic Latin alphabet
> following the initial letter of the previous release, starting with the
> initial release of "Austin". After "Z", the next name should start with
> "A" again.
>
> The name must be composed only of the 26 characters of the ISO basic Latin
> alphabet. Names which can be transliterated into this character set are also
> acceptable.
>
> The name must refer to the physical or human geography of the region
> encompassing the location of the OpenStack design summit for the
> corresponding release. The exact boundaries of the geographic region under
> consideration must be declared before the opening of nominations, as part of
> the initiation of the selection process.
>
> The name must be a single word with a maximum of 10 characters. Words that
> describe the feature should not be included, so "Foo City" or "Foo Peak"
> would both be eligible as "Foo".
>
> Names which do not meet these criteria but otherwise sound really cool
> should be added to a separate section of the wiki page and the TC may make
> an exception for one or more of them to be considered in the Condorcet poll.
> The naming official is responsible for presenting the list of exceptional
> names for consideration to the TC before the poll opens.
>
> Exact Geographic Region
> ---
>
> The Geographic Region from where names for the S release will come is Colorado
>
> Proposed Names
> --
>
> * Tarryall
> * Teakettle
> * Teller
> * Telluride
> * Thomas : the Tank Engine
> * Thornton
> * Tiger
> * Tincup
> * Timnath
> * Timber
> * Tiny Town
> * Torreys
> * Trail
> * Trinidad
> * Treasure
> * Troublesome
> * Trussville
> * Turret
> * Tyrone
>
> Proposed Names that do not meet the criteria (accepted by the TC)
> -
>
> * Train : Many Attendees of the first Denver PTG have a story to tell about 
> the trains near the PTG hotel.  We could celebrate those stories with this 
> name
>
> Yours Tony.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all]Naming the T release of OpenStack -- Poll open

[Tony Breeds]

Hi folks,

It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting.  This means, everybody should proceed to use the following URL to
cast their vote:

  
https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e

We've selected a public poll to ensure that the whole community, not just gerrit
change owners get a vote.  Also the size of our community has grown such that we
can overwhelm CIVS if using private urls.  A public can mean that users
behind NAT, proxy servers or firewalls may receive an message saying
that your vote has already been lodged, if this happens please try
another IP.

Because this is a public poll, results will currently be only viewable by myself
until the poll closes. Once closed, I'll post the URL making the results
viewable to everybody. This was done to avoid everybody seeing the results while
the public poll is running.

The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will 
be
posted shortly after.

[1] https://governance.openstack.org/tc/reference/release-naming.html
---

According to the Release Naming Process, this poll is to determine the
community preferences for the name of the T release of OpenStack. It is
possible that the top choice is not viable for legal reasons, so the second or
later community preference could wind up being the name.

Release Name Criteria
-

Each release name must start with the letter of the ISO basic Latin alphabet
following the initial letter of the previous release, starting with the
initial release of "Austin". After "Z", the next name should start with
"A" again.

The name must be composed only of the 26 characters of the ISO basic Latin
alphabet. Names which can be transliterated into this character set are also
acceptable.

The name must refer to the physical or human geography of the region
encompassing the location of the OpenStack design summit for the
corresponding release. The exact boundaries of the geographic region under
consideration must be declared before the opening of nominations, as part of
the initiation of the selection process.

The name must be a single word with a maximum of 10 characters. Words that
describe the feature should not be included, so "Foo City" or "Foo Peak"
would both be eligible as "Foo".

Names which do not meet these criteria but otherwise sound really cool
should be added to a separate section of the wiki page and the TC may make
an exception for one or more of them to be considered in the Condorcet poll.
The naming official is responsible for presenting the list of exceptional
names for consideration to the TC before the poll opens.

Exact Geographic Region
---

The Geographic Region from where names for the S release will come is Colorado

Proposed Names
--

* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas : the Tank Engine
* Thornton
* Tiger
* Tincup
* Timnath
* Timber
* Tiny Town
* Torreys
* Trail
* Trinidad
* Treasure
* Troublesome
* Trussville
* Turret
* Tyrone

Proposed Names that do not meet the criteria (accepted by the TC)
-

* Train🚂 : Many Attendees of the first Denver PTG have a story to tell about 
the trains near the PTG hotel.  We could celebrate those stories with this name

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Ed Leafe]

On Oct 18, 2018, at 11:43 AM, Michał Dulko  wrote:
> 
> I'm totally supportive for OpenStack Train, but got to say that
> OpenStack Troublesome is a wonderful name as well. :)

Yeah, I’m sure that the marketing people won’t have a problem vetting that 
name. :)

-- Ed Leafe






__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Michał Dulko]

On Thu, 2018-10-18 at 17:35 +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
> 
> 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'm totally supportive for OpenStack Train, but got to say that
OpenStack Troublesome is a wonderful name as well. :)

> 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Jeremy Stanley]

On 2018-10-18 08:35:21 -0500 (-0500), Jay S Bryant wrote:
[...]
> When OpenStack developers think Denver, we think Trains.  :-)
[...]

As, presumably, do many OpenStack operators now since the Ops
Mid-Cycle event was co-located with the most recent PTG.
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Neil Jerram]

On Thu, Oct 18, 2018 at 2:35 PM Jay S Bryant  wrote:
>
>
>
> 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

:-) Thanks!
Neil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Jay S Bryant]

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 > 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



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Neil Jerram]

FWIW, I've have no clue if this is serious or not, or what 'Train' refers
to...


On Thu, Oct 18, 2018 at 2:25 PM Jay S Bryant  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
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Naming the T release of OpenStack

[Jay S Bryant]

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


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Naming the T release of OpenStack

[Tony Breeds]

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


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev