← Back to team overview

openstack team mailing list archive

Re: I release naming (calling APAC community)

 

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@xxxxxxxxx> 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<https://launchpad.net/~openstack>
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>

Follow ups

References