[Catalog-sig] please add trove classifier for OpenStack
Doug Hellmann
doug.hellmann at gmail.com
Wed Oct 17 14:07:55 CEST 2012
On Oct 15, 2012, at 2:18 PM, Doug Hellmann wrote:
>
> On Oct 15, 2012, at 8:51 AM, Martin v. Löwis wrote:
>
>> Am 13.10.12 12:32, schrieb Doug Hellmann:
>>>
>>>> What packages are these specifically? Preferably, I'd like to
>>>> learn about packages that are already registered at this very
>>>> point.
>>>
>>> In addition to some packages we are preparing for imminent release,
>>> there are several client libraries (python-quantumclient,
>>> python-novaclient, etc.). I found a good number via a text search
>>> (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search).
>>> There is also a project within OpenStack to pull out some of the code
>>> common to the various federated projects to make it easier to share,
>>> and I anticipate those libraries being listed on PyPI and tagged with
>>> this new classifier as well.
>>
>> I see. ISTM that OpenStack isn't really a framework for many of these
>> packages, in the sense of
>>
>> http://en.wikipedia.org/wiki/Software_framework
>>
>> (i.e. software that can be plugged into to create applications); instead, many of the Python libraries seem to use OpenStack in
>> a client-server manner.
>
> Hmm, yes, you could be right.
>
>> If the purpose is primarily to find OpenStack-related code,
>> Environment::OpenStack or Topic::Internet::OpenStack might be
>> more appropriate. OTOH, I know next to nothing about OpenStack,
>> so a second opinion from an expert would be appreciated.
>
> I like "Environment::OpenStack" for the clients, and it could work for the other pieces, too. I'll ask around a bit and see what others have to say.
I've talked to a few of the leaders on the infrastructure team for the project and they agree that "Environment::OpenStack" makes the most sense for a broader range of packages, so we would like to use that.
Thanks,
Doug
More information about the Catalog-SIG
mailing list