Open Stack

On 10/01/2013 11:45 AM, Thomas Goirand wrote:
> On 10/01/2013 10:02 PM, Jonathan Dowland wrote:
>> On Tue, Oct 01, 2013 at 09:45:17PM +0800, Thomas Goirand wrote:
>>> Since I have already uploaded python-troveclient (currently waiting in
>>> the FTP master's NEW queue), OpenStack troveclient will be in Sid, but
>>> if some day, someone wants to upload TroveClient from
>>> http://dev.yourtrove.com, then we have a problem.
>> …
>>> Is it too late to fix this?

I don't think it's a problem. Two reasons:

a) libtrove-java having its source package named trove is a bug. the
upstream project is called trove4j, that's what their source package
should have been called. We can't be held accountable for that.

b) We got to python-troveclient first. We win. (sorry that's rude, but
we _did_ get into the queue first. That's the reason that pip is
"python-pip" in debian, because there is a pip tool in perl. TroveClient
released last january and dev.yourtrove.com is unresponsive.

I DO agree that we need to be careful with them, and I think that a fair
list of things to check when looking for a name are:

PyPI
Launchpad
debian
fedora

We might need some follow up from fedora and debian folks about HOW
people should search for names and what things should be considered in
conflict. Remember that most of our 1200 devs do not have any idea how
debian packaging works. Those of us who _do_ need to give very short and
succinct guidelines, such as:

The package name should not conflict with source or binary package names
in Debian. You can search for those by ...

However, again, in this case I think it's fine, and I do not think we
need to rename trove beceause there happens to be a package called trove4j.

>> Ask ftp masters to reject the package and re-upload with the source
>> package renamed to have an openstack prefix/suffix/infix.
> 
> Thanks but no thanks. I need to have the python namespace (eg, the
> egg-info and such) to match the package name, otherwise there will be no
> correct automatic ${python:Depends} substitution.
> 
> FYI, the message was more addressed to the OpenStack community, rather
> than -devel...
> 
> On 10/01/2013 10:53 PM, Michael Basnight wrote:
>> Well this sucks.
> 
> Indeed!
> 
>> Im not sure im a fan of renaming it because of the
>> previous existence of a package.
> 
> Well, I wonder how the Trove name was chosen. Clearly, it was done
> without any good policy in place.
> 
>> Renaming is not fun.
> 
> It sure isn't. Quantum -> Neutron was hell for everyone. Though luckily,
> Trove isn't that big (yet).
> 
>> Ill let the more experienced openstack peoples help decide on this...
> 
> Same over here. Though for this not to happen again, I think the
> OpenStack projects needs to set some rules for project name choice.
> 
> Thomas
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>