On 06/02/2016 06:29 AM, 秀才 wrote: > i suggest a name Zun :) > please see the reference: https://en.wikipedia.org/wiki/Zun
It's available on pypi and launchpad. I especially love that one of the important examples is the "Four-goat square Zun" https://en.wikipedia.org/wiki/Zun#Four-goat_square_Zun I don't get a vote - but I vote for this one. > ------------------ Original ------------------ > *From: * "Rochelle Grober";<rochelle.gro...@huawei.com>; > *Date: * Thu, Jun 2, 2016 09:47 AM > *To: * "OpenStack Development Mailing List (not for usage > questions)"<openstack-dev@lists.openstack.org>; > *Cc: * "Haruhiko Katou"<har-ka...@ts.jp.nec.com>; > *Subject: * Re: [openstack-dev] [higgins] Should we rename "Higgins"? > > Well, you could stick with the wine bottle analogy and go with a bigger > size: > > Jeroboam > Methuselah > Salmanazar > Balthazar > Nabuchadnezzar > > --Rocky > > -----Original Message----- > From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] > Sent: Wednesday, June 01, 2016 3:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Cc: Haruhiko Katou > Subject: Re: [openstack-dev] [higgins] Should we rename "Higgins"? > > Thanks Shu for providing suggestions. > > I wanted the new name to be related to containers as Magnum is also > synonym for containers. So I have few options here. > > 1. Casket > 2. Canister > 3. Cistern > 4. Hutch > > All above options are free to be taken on pypi and Launchpad. > Thoughts? > > Regards > Madhuri > > -----Original Message----- > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] > Sent: Wednesday, June 1, 2016 11:11 AM > To: openstack-dev@lists.openstack.org > Cc: Haruhiko Katou <har-ka...@ts.jp.nec.com> > Subject: Re: [openstack-dev] [higgins] Should we rename "Higgins"? > > I found container related names and checked whether other project uses. > > https://en.wikipedia.org/wiki/Straddle_carrier > https://en.wikipedia.org/wiki/Suezmax > https://en.wikipedia.org/wiki/Twistlock > > These words are not used by other project on PYPI and Launchpad. > > ex.) > https://pypi.python.org/pypi/straddle > https://launchpad.net/straddle > > > However the chance of renaming in N cycle will be done by Infra-team on > this Friday, we would not meet the deadline. So.... > > 1. use 'Higgins' ('python-higgins' for package name) 2. consider other > name for next renaming chance (after a half year) > > Thoughts? > > > Regards, > Shu > > >> -----Original Message----- >> From: Hongbin Lu [mailto:hongbin...@huawei.com] >> Sent: Wednesday, June 01, 2016 11:37 AM >> To: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [higgins] Should we rename "Higgins"? >> >> Shu, >> >> According to the feedback from the last team meeting, Gatling doesn't >> seem to be a suitable name. Are you able to find an alternative name? >> >> Best regards, >> Hongbin >> >> > -----Original Message----- >> > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] >> > Sent: May-24-16 4:30 AM >> > To: openstack-dev@lists.openstack.org >> > Cc: Haruhiko Katou >> > Subject: [openstack-dev] [higgins] Should we rename "Higgins"? >> > >> > Hi all, >> > >> > Unfortunately "higgins" is used by media server project on Launchpad >> > and CI software on PYPI. Now, we use "python-higgins" for our >> > project on Launchpad. >> > >> > IMO, we should rename project to prevent increasing points to patch. >> > >> > How about "Gatling"? It's only association from Magnum. It's not >> > used on both Launchpad and PYPI. >> > Is there any idea? >> > >> > Renaming opportunity will come (it seems only twice in a year) on >> > Friday, June 3rd. Few projects will rename on this date. >> > http://markmail.org/thread/ia3o3vz7mzmjxmcx >> > >> > And if project name issue will be fixed, I'd like to propose UI >> > subproject. >> > >> > Thanks, >> > Shu >> > >> > >> > >> ______________________________________________________________________ >> _ >> > ___ >> > 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 >> >> ______________________________________________________________________ >> ____ >> 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 > > __________________________________________________________________________ > 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 > > __________________________________________________________________________ > 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 > > __________________________________________________________________________ > 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 > > > __________________________________________________________________________ > 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 > __________________________________________________________________________ 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