Michal, that will never work it’s 11 characters long
> On Oct 18, 2018, at 09:43, Eric Fried <openst...@fried.cc> wrote: > > 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 > <https://governance.openstack.org/tc/reference/release-naming.html> > [2] https://review.openstack.org/#/c/611511/ > <https://review.openstack.org/#/c/611511/> > > On 10/18/2018 10:52 AM, arkady.kanev...@dell.com > <mailto:arkady.kanev...@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 <jonmi...@gmail.com> >> *Sent:* Thursday, October 18, 2018 10:49 AM >> *To:* openstack-s...@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 <openst...@medberry.net >> <mailto:openst...@medberry.net <mailto:openst...@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 >> <t...@bakeyournoodle.com <mailto:t...@bakeyournoodle.com> >> <mailto:t...@bakeyournoodle.com <mailto:t...@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> >> >> <https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T%E2%80%93Z >> <https://en.wikipedia.org/wiki/List_of_places_in_Colorado:_T%E2%80%93Z>> >> _______________________________________________ >> openstack-sigs mailing list >> openstack-s...@lists.openstack.org >> <mailto:openstack-s...@lists.openstack.org> >> <mailto:openstack-s...@lists.openstack.org >> <mailto:openstack-s...@lists.openstack.org>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs> >> >> _______________________________________________ >> openstack-sigs mailing list >> openstack-s...@lists.openstack.org >> <mailto:openstack-s...@lists.openstack.org> >> <mailto:openstack-s...@lists.openstack.org >> <mailto:openstack-s...@lists.openstack.org>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs> >> >> >> >> _______________________________________________ >> openstack-sigs mailing list >> openstack-s...@lists.openstack.org >> <mailto:openstack-s...@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs> >> > > _______________________________________________ > openstack-sigs mailing list > openstack-s...@lists.openstack.org <mailto:openstack-s...@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs>
__________________________________________________________________________ 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