Open Stack

Yeah, I am too waiting for the ballot. The 'F' release was the craziest one
with 20+ candidates. I favor to vote on a subset of all the names we have
came up with so far. Seven is not bad, but we need a rule to pick 7. If we
adhere to the official naming convention, we probably have six with one or
two from "Other Suggestions." Of course, I think we have to wait for the
committee to come up with the candidates.

John


On Fri, May 10, 2013 at 11:30 AM, John Hebert <johnalexhebert at gmail.com>wrote:

> I agree. The naming convention should not be a barrier to adoption of the
> new release. However, we should consider a name that has significance for
> the hosting community. Naming releases alphabetically is a convenience for
> speakers of Western languages, and the Openstack community is global. I
> don't think a slight deviation from previous naming convention will confuse
> anyone.
>
> It has been pointed out the Hong Kong Openstack summit could attract
> thousands of new developers, and so the name of the release should be
> something that this new community can easily identify. I'm sure a large
> number of Openstack community members wondered what the heck "Bexar" meant
> at first (I'm from San Antonio). :)
>
> In short, I think we should defer to the suggestions made by our hosts in
> Hong Kong and China.
>
> I move we set a deadline to pick the most popular 7 names (a common lucky
> number (七, Pinyin <https://en.wikipedia.org/wiki/Pinyin>: qī) symbolizes
> "togetherness" - wikipedia.org) and then vote soon on them after.
>
> John Hebert
>
> On Fri, May 10, 2013 at 8:24 AM, Eric Windisch <eric at cloudscaling.com>wrote:
>
>> Extending the rules to those things of cultural or political significance
>> would have established precedence with the 'Grizzly exception'.
>>
>> If such an exception were useful in naming this release, I'd suggest it
>> become a standard part of the naming scheme.
>> On May 10, 2013 6:40 AM, "Matt Joyce" <matt.joyce at cloudscaling.com>
>> wrote:
>>
>>> Alternatively... we name it after a kung fu movie.
>>>
>>> Invincible Fist for instance was a Shaw Brothers film.  Hong Kong is
>>> famous for it's Kung Fu films =P
>>>
>>>
>>> On Thu, May 9, 2013 at 8:57 PM, Wang, Shane <shane.wang at intel.com>wrote:
>>>
>>>>   If the next release summit is going to be held in “Japan”, it should
>>>> be easier to give a nameJ****
>>>>
>>>> ** **
>>>>
>>>> --****
>>>>
>>>> Shane Wang****
>>>>
>>>> *From:* Openstack [mailto:openstack-bounces+shane.wang=
>>>> intel.com at lists.launchpad.net] *On Behalf Of *Rajesh Vellanki
>>>> *Sent:* Friday, May 10, 2013 3:50 AM
>>>> *To:* Atul Jha; Matt Joyce; John Wong
>>>>
>>>> *Cc:* Thierry Carrez; openstack at lists.launchpad.net
>>>> *Subject:* Re: [Openstack] I release naming (calling APAC community)***
>>>> *
>>>>
>>>>  ** **
>>>>
>>>> +1 ****
>>>>
>>>> ** **
>>>>
>>>> Rajesh****
>>>>  ------------------------------
>>>>
>>>> *From:* Openstack [openstack-bounces+rvellank=
>>>> rackspace.com at lists.launchpad.net] on behalf of Atul Jha [
>>>> Atul.Jha at csscorp.com]
>>>> *Sent:* Thursday, May 09, 2013 2:31 PM
>>>> *To:* Matt Joyce; John Wong
>>>> *Cc:* Thierry Carrez; openstack at lists.launchpad.net
>>>> *Subject:* Re: [Openstack] I release naming (calling APAC community)***
>>>> *
>>>>
>>>> Hi all,
>>>>
>>>> I was too late to respond here i would love to see next release name as
>>>> "India".  I am saying because India is in APAC still i have need to find
>>>> out rule book for release.
>>>>
>>>> Just my 1$ suggestion. :)
>>>>
>>>> Cheers!!
>>>>
>>>> Atul ****
>>>>  ------------------------------
>>>>
>>>> *From:* Openstack [openstack-bounces+atul.jha=
>>>> csscorp.com at lists.launchpad.net] on behalf of Matt Joyce [
>>>> matt.joyce at cloudscaling.com]
>>>> *Sent:* Friday, May 10, 2013 12:58 AM
>>>> *To:* John Wong
>>>> *Cc:* Thierry Carrez; openstack at lists.launchpad.net
>>>> *Subject:* Re: [Openstack] I release naming (calling APAC community)***
>>>> *
>>>>
>>>> 'Impossible' might be a good name... seeing as how impossible it is
>>>> becoming to find a word beginning with I in the region.****
>>>>
>>>> ** **
>>>>
>>>> On Thu, May 9, 2013 at 12:04 PM, John Wong <gokoproject at gmail.com>
>>>> wrote:****
>>>>
>>>> Good point. A long time ago we used to call Beijing as Peking, but
>>>> the journalists now will always pick up the pinyin version: Beijing. Since
>>>> we are after I, we are pretty much down to either Ichang or Ili. Should
>>>> either one be chosen, I think that we should document the pinyin version as
>>>> well. The difference of Y and I is due to historical difference, which we
>>>> are all familiar with. For example, there are more Wong than Wang, Chan
>>>> than Chen in HK. ****
>>>>
>>>> ** **
>>>>
>>>> John****
>>>>
>>>> ** **
>>>>
>>>> On Thu, May 9, 2013 at 2:21 PM, Yi Yang <yyos1999 at gmail.com> wrote:****
>>>>
>>>> AS the official translation of the citiy names are Yichang and Yili, we
>>>> are facing a risk to pick up a Chinese city name that most Chinese won't
>>>> recognize.
>>>>
>>>> If we really have to choose a city, IMO, Yichang (ichang) would be a
>>>> better choice, as the Yili(ili) is more than 2300 miles away from Hong
>>>> Kong, while Yichang (ichang) is (only) 600 miles away.
>>>>
>>>> Just my $.02
>>>>
>>>> Yi ****
>>>>
>>>>
>>>>
>>>>
>>>> On 5/6/13 5:00 AM, Thierry Carrez wrote:****
>>>>
>>>> Jacob Godin wrote:****
>>>>
>>>> +1 Ili****
>>>>
>>>> Thanks for all the suggestions ! We probably have enough place names so
>>>> that we don't need to extend the naming rules to things that are not
>>>> place names.
>>>>
>>>> So far, the only suggestion that fits in our strict naming rules is
>>>> "Ili" (a city or county in the country/state where the design summit is
>>>> held, single word of 10 characters or less). To have more than one
>>>> option, we'll probably extend the rules to include other places (like
>>>> street names) in Hong Kong itself.
>>>>
>>>> We'll go through name checks and set up a vote soon, I'll keep you
>>>> posted.****
>>>>
>>>> ** **
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack at lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp****
>>>>
>>>> ** **
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack at 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 at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130512/a5ff92b0/attachment.html>