Re: [Openstack] OpenStack G naming poll
-1 Gazelle seems to carry more of the characteristics we would want (nimble, quick). Grizzly carries rather grim connotations of mauling, lumbering, and having a rather nasty disposition. I would not want that in a cloud. Also, as an adjective, grizzly means 'showing characteristics of age, especially having grey or white hair'. While the name may sound cool, it is actually ill fitting. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Industry and Cloud Standards Member, IBM Academy of Technology IBM Software Group, Standards Strategy email: chris...@us.ibm.com Twitter: christo4ferris phone: +1 508 234 2986 -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: - To: Gabriel Hurley gabriel.hur...@nebula.com From: Mark Collier Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net Date: 07/03/2012 09:46PM Cc: openstack@lists.launchpad.net \(openstack@lists.launchpad.net\) openstack@lists.launchpad.net, Thierry Carrez thie...@openstack.org Subject: Re: [Openstack] OpenStack G naming poll +1 grizzly On Jul 3, 2012, at 7:45 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: +1 on #8220;close enough to an arbitrary territory and also a great name#8221;. ;-) Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html Food for thought. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net ] On Behalf Of Brian Waldon Sent: Tuesday, July 03, 2012 4:50 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Cc: Thierry Carrez Subject: Re: [Openstack] OpenStack G naming poll TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
But on the flip side, Gazelles get eaten by lions. Read into that what you will :) Kind Regards Andrew On 05/07/12 11:41, Christopher B Ferris wrote: -1 Gazelle seems to carry more of the characteristics we would want (nimble, quick). Grizzly carries rather grim connotations of mauling, lumbering, and having a rather nasty disposition. I would not want that in a cloud. Also, as an adjective, grizzly means 'showing characteristics of age, especially having grey or white hair'. While the name may sound cool, it is actually ill fitting. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Industry and Cloud Standards Member, IBM Academy of Technology IBM Software Group, Standards Strategy email: chris...@us.ibm.com Twitter: christo4ferris phone: +1 508 234 2986 -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: - To: Gabriel Hurley gabriel.hur...@nebula.com From: Mark Collier Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net Date: 07/03/2012 09:46PM Cc: openstack@lists.launchpad.net \(openstack@lists.launchpad.net\) openstack@lists.launchpad.net, Thierry Carrez thie...@openstack.org Subject: Re: [Openstack] OpenStack G naming poll +1 grizzly On Jul 3, 2012, at 7:45 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: +1 on #8220;close enough to an arbitrary territory and also a great name#8221;. ;-) Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html Food for thought. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net ] On Behalf Of Brian Waldon Sent: Tuesday, July 03, 2012 4:50 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Cc: Thierry Carrez Subject: Re: [Openstack] OpenStack G naming poll TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Andrew Hutchings - LinuxJedi - http
Re: [Openstack] OpenStack G naming poll
That's a good point. I think at this stage just having grizzly on the ballot is a fair next step. On Jul 5, 2012, at 5:42 AM, Christopher B Ferris chris...@us.ibm.com wrote: -1 Gazelle seems to carry more of the characteristics we would want (nimble, quick). Grizzly carries rather grim connotations of mauling, lumbering, and having a rather nasty disposition. I would not want that in a cloud. Also, as an adjective, grizzly means 'showing characteristics of age, especially having grey or white hair'. While the name may sound cool, it is actually ill fitting. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Industry and Cloud Standards Member, IBM Academy of Technology IBM Software Group, Standards Strategy email: chris...@us.ibm.com Twitter: christo4ferris phone: +1 508 234 2986 -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: - To: Gabriel Hurley gabriel.hur...@nebula.com From: Mark Collier Sent by: openstack-bounces+chrisfer=us.ibm@lists.launchpad.net Date: 07/03/2012 09:46PM Cc: openstack@lists.launchpad.net\(openstack@lists.launchpad.net\) openstack@lists.launchpad.net, ThierryCarrez thie...@openstack.org Subject: Re: [Openstack] OpenStack G naming poll +1 grizzly On Jul 3, 2012, at 7:45 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: +1 on #8220;close enough to an arbitrary territory and also a great name#8221;. ;-) Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html Food for thought. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net ] On Behalf Of Brian Waldon Sent: Tuesday, July 03, 2012 4:50 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Cc: Thierry Carrez Subject: Re: [Openstack] OpenStack G naming poll TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
Mark Collier wrote: That's a good point. I think at this stage just having grizzly on the ballot is a fair next step. Due to limitations in the Launchpad poll system you can't modify (or cancel) a poll so I had to create a second poll about prefering Grizzly over anything else that would be chosen by the normal poll. See https://lists.launchpad.net/openstack/msg14199.html for details. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
+1 to Grizzly I have already voted. :) From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of Thierry Carrez [thie...@openstack.org] Sent: Thursday, July 05, 2012 4:50 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] OpenStack G naming poll Mark Collier wrote: That's a good point. I think at this stage just having grizzly on the ballot is a fair next step. Due to limitations in the Launchpad poll system you can't modify (or cancel) a poll so I had to create a second poll about prefering Grizzly over anything else that would be chosen by the normal poll. See https://lists.launchpad.net/openstack/msg14199.html for details. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp http://www.csscorp.com/common/email-disclaimer.php ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
Done :-) Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 4 juil. 2012 à 00:20, Thierry Carrez a écrit :Yes, it's that time of the year again... time for us to choose the nameof the next OpenStack release !This time, cities and counties in California (San Diego, CA being thelocation of the G design summit)I set up a poll with the available options (based on our current rulesof naming) at:https://launchpad.net/~openstack/+poll/g-release-namingPoll is accessible to all members of ~openstack group in Launchpad, andends next Tuesday, 21:30 UTC. Please cast your vote!I'm aware that a subversive movement wants to try to amend the rules sothat another name option becomes available. Since we can't stop (ormodify) the poll now that it's been launched, if that movement reachescritical mass, we may organize a second round of polling :)-- Thierry Carrez (ttx)Release Manager, OpenStack___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
James E. Blair wrote: Brian Waldon brian.wal...@rackspace.com writes: TL;DR - Screw the rules, let's call the next release 'Grizzly' [...] I will join your Bear Flag Revolt. OK, OK, Jim's flag convinced me, I absolutely need a T-shirt with that. So I set up a /second/ poll that basically says, ignore the result of the other one and go for Grizzly: https://launchpad.net/~openstack/+poll/g-stands-for-grizzly Launchpad polls need to be created 12 hours before they open (sucks) so it's not available yet (opens at 20:00 UTC today), and will end at the same date as the other one. Combining the two results we should be able to have a winner ! We'll advertise both starting tomorrow on blogs/Twitter/whatever-is-cool-today :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
Brian Waldon wrote: On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote: At the g summit, we'd tell everyone where the next summit is: At the g summit, we'd vote and announce the name of h We wouldn't have to spend half the cycle saying h, or whatever when we mean we're going to defer that crazy idea until next time I wouldn't have had to use the letter g by itself twice just above here. Fantastic idea. I haven't been involved in choosing the next location, so I'm not sure how hard it would be to choose it that far in advance. Maybe somebody can comment on how doable this is? It's definitely doable (and desirable). Actually that's the plan for the next one: close the date and location deal before the summit so that we can announce the next one during the summit itself. So we would definitely vote in person (like we did for Cactus at the Bexar summit), so much funnier than a Launchpad poll. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
On Wed, Jul 04, 2012 at 10:02:46AM +0200, Thierry Carrez wrote: Brian Waldon wrote: On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote: At the g summit, we'd tell everyone where the next summit is: At the g summit, we'd vote and announce the name of h We wouldn't have to spend half the cycle saying h, or whatever when we mean we're going to defer that crazy idea until next time I wouldn't have had to use the letter g by itself twice just above here. Fantastic idea. I haven't been involved in choosing the next location, so I'm not sure how hard it would be to choose it that far in advance. Maybe somebody can comment on how doable this is? It's definitely doable (and desirable). Actually that's the plan for the next one: close the date and location deal before the summit so that we can announce the next one during the summit itself. So we would definitely vote in person (like we did for Cactus at the Bexar summit), so much funnier than a Launchpad poll. I'd be against doing a vote in person at the summit on the basis that this would exclude a large portion of the community who are unable to attend :-( A online poll is fully inclusive of the OpenStack community. I think the same point applies more broadly to any important decisions related to the project, for which the community is ultimately responsible. Meeting people face-to-face for technical presentations / discussions / debates is a productive way of examining difficult issues, but those who are unfortunate enough to not attend summits can feel very isolated. This leads to people feeling there is a 2-tier community. To counter this, IMHO, it is important to communicate important decisions resulting from f-2-f meetings to the community provide a means for them to add any relevant feedback influence decisions. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
On 07/03/2012 04:50 PM, Brian Waldon wrote: TL;DR - Screw the rules, let's call the next release 'Grizzly' Do it! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
+1 for Grizzly On Jul 3, 2012 8:02 PM, Brian Waldon brian.wal...@rackspace.com wrote: TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with '*Gazelle*'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
+1 on close enough to an arbitrary territory and also a great name. ;-) Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html Food for thought. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Brian Waldon Sent: Tuesday, July 03, 2012 4:50 PM To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Cc: Thierry Carrez Subject: Re: [Openstack] OpenStack G naming poll TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
tl;dr - Screw the rules, I agree Let's at least add it to the poll. Also - I think we should further amend the rules such that we select the NEXT release by the summit for the current release. That means two things: At the g summit, we'd tell everyone where the next summit is: At the g summit, we'd vote and announce the name of h We wouldn't have to spend half the cycle saying h, or whatever when we mean we're going to defer that crazy idea until next time I wouldn't have had to use the letter g by itself twice just above here. On 07/03/2012 06:50 PM, Brian Waldon wrote: TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with '/Gazelle/'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
On 07/03/2012 07:29 PM, Brian Waldon wrote: On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote: tl;dr - Screw the rules, I agree Let's at least add it to the poll. Also - I think we should further amend the rules such that we select the NEXT release by the summit for the current release. That means two things: At the g summit, we'd tell everyone where the next summit is: At the g summit, we'd vote and announce the name of h We wouldn't have to spend half the cycle saying h, or whatever when we mean we're going to defer that crazy idea until next time I wouldn't have had to use the letter g by itself twice just above here. Fantastic idea. I haven't been involved in choosing the next location, so I'm not sure how hard it would be to choose it that far in advance. Maybe somebody can comment on how doable this is? I actually think it's HARDER to not choose it that far in advance, because the longer you wait, the more places are booked already. Although it's not exactly the same - linux conf australia always announces the location of the next conference at the current conference - and those are yearly. Also, they have a rotating set of host teams... so basically a team from a town puts in a proposal to linux.au saying we'd like to host the next one, here's what we're going to do, here's where we're going to have it, blah blah blah - and then one of them gets selected, and then they're the poor sods that have to actually run the darned thing. So to stick my nose WAY in where it doesn't belong, once we have the foundation - what if we move to a model of having folks propose that they'd like to host the design summit? We can make a CFP-style deadline, and people can all pitch their location, and one can get chosen and announced by Thierry at a closing session or whatnot. That way if I wanted to get together with some other folks and say hey guys, I've got 10 rooms that NYU has donated, and I'll provide these facilities - then great, or if mercado libre wanted to say zomg - we totally going to bring you all to the Shearton WTC in Sao Paulo - or NTT was all dude, we've got a thousand rooms in the middle of Tokyo or Rackspace went I don't know if anybody noticed, but we bought a shopping mall a few years ago and it's got conference rooms ... the folks can sit in a room, look at the proposals, say things like wow, I really don't want to sit in the castle all week when I sit there all week anyway - but drinking with Monty in the Lower East Side at a bar that has freezer they'll lock you in with a bottle of vodka sounds like a great way to plan the Houston release (that's how-ston for all you Texans) -- it would almost be like distributed development with code review. Of course, if that flys I guess I'm going to have to figure out how to take everyone to Mehanata... Monty ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
+1 grizzly On Jul 3, 2012, at 7:45 PM, Gabriel Hurley gabriel.hur...@nebula.commailto:gabriel.hur...@nebula.com wrote: +1 on “close enough to an arbitrary territory and also a great name”. ;-) Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html Food for thought. - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.netmailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.netmailto:bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of Brian Waldon Sent: Tuesday, July 03, 2012 4:50 PM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Cc: Thierry Carrez Subject: Re: [Openstack] OpenStack G naming poll TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. Brian On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
On 07/03/2012 07:33 PM, James E. Blair wrote: Brian Waldon brian.wal...@rackspace.com writes: TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. I will join your Bear Flag Revolt. Best. Picture. Ever. We have a G winner... and honestly, if that's not the t-shirt then I'm going to have my own bear flag revolt. Grizzly FTW We could amend the rules to add official symbols of the territory in question. Despite being one of the most recognized symbols of California, named the state animal, and appearing on the state flag, the Grizzly bear (Ursus californicus) has been extinct here since 1922. [1] http://en.wikipedia.org/wiki/California_Republic#Bear_Flag_Revolt -Jim Though as a Firesign Theatre fan, I like Goshen too. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
I would like to come out as strongly pro-Grizzly. I wonder if this release name would make Thierry the moma grizzly: http://en.wikipedia.org/wiki/Mama_grizzly dan On Wed, Jul 4, 2012 at 1:33 AM, James E. Blair cor...@inaugust.com wrote: Brian Waldon brian.wal...@rackspace.com writes: TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with 'Gazelle'. I will join your Bear Flag Revolt. We could amend the rules to add official symbols of the territory in question. Despite being one of the most recognized symbols of California, named the state animal, and appearing on the state flag, the Grizzly bear (Ursus californicus) has been extinct here since 1922. [1] http://en.wikipedia.org/wiki/California_Republic#Bear_Flag_Revolt -Jim Though as a Firesign Theatre fan, I like Goshen too. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack G naming poll
Grizzly is better than people making who is john galt jokes. +1 to grizzly. On Tue, Jul 3, 2012 at 5:51 PM, Mark Collier mark.coll...@rackspace.comwrote: +1 grizzly On Jul 3, 2012, at 7:45 PM, Gabriel Hurley gabriel.hur...@nebula.com wrote: +1 on “close enough to an arbitrary territory and also a great name”. ;-) ** ** Also, the Grizzly is the California state animal: http://www.statesymbolsusa.org/California/animal_grizzly_bear.html ** ** Food for thought. ** ** - Gabriel ** ** *From:* openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On Behalf Of *Brian Waldon *Sent:* Tuesday, July 03, 2012 4:50 PM *To:* openstack@lists.launchpad.net (openstack@lists.launchpad.net) *Cc:* Thierry Carrez *Subject:* Re: [Openstack] OpenStack G naming poll ** ** TL;DR - Screw the rules, let's call the next release 'Grizzly' ** ** As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name being 'Grizzly'. The rules clearly state that a release name must represent a city or county near the corresponding design summit and be comprised of a single word of ten characters or less - the problem here being that 'Grizzly' is actually 'Grizzly Flats.' Having already polled a small subset of the community, I feel like there would be enough support for 'Grizzly' to win if it were on the ballot. As I'm more interested in selecting a suitable name than accurately representing some arbitrary territory, I'd love to either permanently amend the rules to make this acceptable or grant an exception in this one case. As Thierry said, if this reaches critical mass, we will figure out what to do. Otherwise, I'll shut up and deal with '*Gazelle*'. ** ** Brian ** ** ** ** On Jul 3, 2012, at 3:20 PM, Thierry Carrez wrote: Yes, it's that time of the year again... time for us to choose the name of the next OpenStack release ! This time, cities and counties in California (San Diego, CA being the location of the G design summit) I set up a poll with the available options (based on our current rules of naming) at: https://launchpad.net/~openstack/+poll/g-release-naminghttps://launchpad.net/%7Eopenstack/+poll/g-release-naming Poll is accessible to all members of ~openstack group in Launchpad, and ends next Tuesday, 21:30 UTC. Please cast your vote! I'm aware that a subversive movement wants to try to amend the rules so that another name option becomes available. Since we can't stop (or modify) the poll now that it's been launched, if that movement reaches critical mass, we may organize a second round of polling :) -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ** ** ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
