[Openstack-operators] [all] Naming the T release of OpenStack
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-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [all] Naming the T release of OpenStack
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-operators] [all] Naming the T release of OpenStack
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 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 mrhills...@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
Re: [Openstack-operators] [all] Naming the T release of OpenStack
Just do a vote as usual, train is a great candidate :) On Thu, Oct 18, 2018 at 11:44 PM Melvin Hillsman 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 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 > mrhills...@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: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [all] Naming the T release of OpenStack
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
[Openstack-operators] [all]Naming the T release of OpenStack -- Poll open
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-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
