Open Stack

I'd like to propose we just use numbers for versioning our software. Both
random words and the year.cadence scheme are irritating in their own
special way.

Why not make it Openstack 13.0 and let the downstream distributions play in
the minefield that is naming software projects.

 - Michael

On Wed, Jul 8, 2015 at 3:50 PM, Michael Micucci <micucci at midokura.com>
wrote:

> Dear all,
>
> #4 was Mitaka (三鷹, meaning "three hawks"), I believe?
>
> Mitaka is a very beautiful city, if I may say so (I lived there, so I'm a
> bit biased :)), with Inokashira Park, a zoo, and many walking trails.
> Plus, the Ghibli Museum is there, which celebrates a very famous and
> well-loved animation studio throughout the world, with a similar pedigree
> to Disney in the U.S.A. (such as Spirited Away, Howl's Moving Castle,
> Nausicaa and the Valley of the Wind, My Neighbor Totoro, among many other
> great films)  With animation being a world-wide export from Japan, it seems
> like a nice (and current) thing to celebrate.
>
> I'd like to support Iwamoto-san's proposal in the interest of peace and
> cooperation between our international communities, and suggest we switch to
> "Mitaka."
>
> I just hope there are no legal problems with this name as well. :)
>
> Sincerely,
>
> Michael Micucci
>
>
>
> On 07/08/2015 02:31 PM, IWAMOTO Toshihiro wrote:
>
>> It is totally understandable that the combination of "Japan" and
>> "Meiji" recalls harsh history to some people, especially in East Asia.
>> As a Japanese, I'm sorry for that.
>>
>> I think the release naming process should not cause such friction.
>> Could we just select some other neutral candidate name instead?
>>
>> At Wed, 08 Jul 2015 04:40:58 +0000,
>> Jaesuk Ahn wrote:
>>
>>> Dear OpenStack Community,
>>>
>>> As Clint mentioned, there is some historical background regarding the
>>> name
>>> of "Meiji".
>>>
>>> I have been aware of the potential problem with "Meiji", however, I have
>>> not raise my voice here since it was not the top of the list.
>>> However, with current situation, IMHO, it is better to present my concern
>>> over this name.
>>>
>>> It was briefly mentioned in the previous email thread.
>>> Once again, please understand that the name "Meiji" can create some
>>> historical debate in East Asia, especially in Korea. Under the name of
>>> Emperor Meiji, Japan forcefully colonized Korea. Lots of people in Korea
>>> suffered during the colonization. Furthermore, this history is not the
>>> one
>>> only exists on the book. This is actually very recent event in terms of
>>> history.
>>>
>>> FYI, there is a wiki entry:
>>> https://en.wikipedia.org/wiki/Korea_under_Japanese_rule
>>> If you look at "legacy" section in the above wiki entry, you will
>>> understand what I am referring to.
>>>
>>> I am not saying the word "Meiji" is bad in general. I just want to state
>>> that this word can cause very negative feeling to some people in East
>>> Asia.
>>>
>>> I totally value the community's process and rules. I recognize that
>>> process
>>> to select "Meiji" itself was not the problem at all.
>>> However, I am sincerely asking the community to acknowledge my concern
>>> over
>>> this name, and please put some effort as a community to avoid any
>>> unnecessary debate.
>>>
>>> Thank you.
>>>
>>> Best wishes for everyone here in the community.
>>>
>>>
>>> Jaesuk Ahn, Ph.D.
>>> member of OpenStack Community and OpenStack Korea User Group.
>>>
>>>
>>>
>>>
>>> On Wed, Jul 8, 2015 at 2:24 AM Clint Byrum <clint at fewbar.com> wrote:
>>>
>>>  http://afe.easia.columbia.edu/main_pop/kpct/kp_meiji.htm
>>>>
>>>> There's a summary of what Meiji might mean to historians. I'm not sure
>>>> if
>>>> OpenStack needs to be too concerned about this, but I believe this is
>>>> what
>>>> Ian is referring to as "historical and political debates in East Asia."
>>>>
>>>> Seems like a hot-button name for OpenStack to adopt.
>>>>
>>>> Excerpts from Ian Y. Choi's message of 2015-07-07 05:40:52 -0700:
>>>>
>>>>> Hello,
>>>>>
>>>>> I think the third name 'Meiji' may arise some historical and political
>>>>> debates in East Asia, as far as I know.
>>>>>
>>>>> Could you share what significant identified problems are on the first
>>>>> two
>>>>> selected from our election?
>>>>>
>>>>>
>>>>> With many thanks,
>>>>>
>>>>> /Ian
>>>>>
>>>>> On Tue, Jul 7, 2015 at 8:55 PM, Masayuki Igawa <
>>>>> masayuki.igawa at gmail.com
>>>>>
>>>>> wrote:
>>>>>
>>>>>  Hi,
>>>>>> # I'm a native Japanese speaker :-)
>>>>>>
>>>>>> 2015年7月7日(火) 20:33 Amrith Kumar <amrith at tesora.com>:
>>>>>>
>>>>>>  Maybe this (the google answer)?
>>>>>>>
>>>>>>> www.youtube.com/watch?v=Qvw0A12aOGQ
>>>>>>>
>>>>>>
>>>>>> Yeah, this is correct pronunciation.
>>>>>>
>>>>>>
>>>>>>  But someone who is a native Japanese speaker should confirm.
>>>>>>>
>>>>>>>  https://www.youtube.com/watch?v=D9vwge557hY
>>>>>> I think this is a casual version and Japanese people are familiar with
>>>>>> this.
>>>>>>
>>>>>> Thanks,
>>>>>> -- Masayuki Igawa
>>>>>>
>>>>>>
>>>>>>  -amrith
>>>>>>>
>>>>>>> P.S. the yahoo answer suggests that you pronounce it as "Meh - gee"
>>>>>>>
>>>>>> with
>>>>
>>>>> the emphasis on the "meh" ;)
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Matthias Runge [mailto:mrunge at redhat.com]
>>>>>>> Sent: Tuesday, July 07, 2015 6:08 AM
>>>>>>> To: openstack-dev at lists.openstack.org
>>>>>>> Subject: Re: [openstack-dev] OpenStack Meiji (明治) - Our next release
>>>>>>>
>>>>>> name
>>>>
>>>>> has been selected
>>>>>>>
>>>>>>> On Mon, Jul 06, 2015 at 11:48:13PM -0400, Monty Taylor wrote:
>>>>>>>
>>>>>>>> significant identified problems... but the third in the list, Meiji
>>>>>>>>
>>>>>>> (明
>>>>
>>>>> 治) is clear.
>>>>>>>>
>>>>>>>> So please join me in welcoming the latest name to our family ... and
>>>>>>>> if you, like me, are not a native Japanese speaker, in learning two
>>>>>>>> new characters.
>>>>>>>>
>>>>>>> Could someone provide a hint please, how to pronounce this properly?
>>>>>>> --
>>>>>>> Matthias Runge <mrunge at redhat.com>
>>>>>>>
>>>>>>>
>>>>>>>
>>>> __________________________________________________________________________
>>>>
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>> Unsubscribe:
>>>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>
>>>>>>>
>>>> __________________________________________________________________________
>>>>
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>>> Unsubscribe:
>>>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>>
>>>>>>>  --
>>>>>> -- Masayuki Igawa
>>>>>>
>>>>>>
>>>>>>
>>>> __________________________________________________________________________
>>>>
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>>> Unsubscribe:
>>>>>>
>>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>>
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>>>
>>>>>>
>>>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150708/f241be76/attachment.html>