On Fri, Jun 17, 2011 at 9:35 AM, Zygmunt Krynicki < zygmunt.krynicki@canonical.com> wrote:

Hi.

I was wondering if anyone would object to namespace cleanup of our python projects.

I think it probably only makes sense to have Linaro in the name if there is something specific to Linaro about it. I think for most of these, they could be generally used by anyone, so it makes more sense to leave that out.

For "linaro-django-pagination" This project is a fork of dead/unmaintained django-pagination. The upstream author has rejected my requests to hand over ownership.

Is he interested in the changes you made as a patch, rather than a full takeover of the project? What are the main differences? If it's so different that it warrants a whole new project name, then we should name it something that makes it more clear what the difference is, rather than just "good". If it's not that different, then it would be better for us to work with the current django-pagination project and see how we can merge our changes.

Thanks, Paul Larson

On Fri, 17 Jun 2011 16:35:07 +0200, Zygmunt Krynicki zygmunt.krynicki@canonical.com wrote:

Hi.

I was wondering if anyone would object to namespace cleanup of our python projects.

Here is my proposed list of changes:

For "linaro-django-pagination" This project is a fork of dead/unmaintained django-pagination. The upstream author has rejected my requests to hand over ownership. Proposed names: -> django-good-pagination -> django-linaro-pagination

"good" seems a bit prejudicial :) I think django-linaro-pagination is OK here: it expresses that it's a fork of django-pagination that's being driven forward by linaro. Also I can't think of anything better.

For "linaro-django-xmlrpc" This project is a generic-purpose, written-from-scratch, XML-RPC component for django. There are numerous similar projects out there, including django-xmlrpc Proposed names: -> django-secure-xmlrpc -> django-web-api (if we include JSON-RPC/ajax in the future) -> django-linaro-xmlrpc

Hmm. django-authenticated-apis? I don't like the word 'secure' :) but I think we could support json-rpc easily enough, and probably should. I don't know what you mean by ajax -- as users of linaro-django-xmlrpc will raise xmlrpclib.Faults, we really need a protocol that can has such an idea.

For "linaro-json": This project started as a huge collection of tools for JSON but was later on refocused on one important thing - schema validation. Proposed names: -> json-schema-validator -> json-schema (still unused on pypi :-)

I don't know the project, but from your description both these names sound ok.

For "linaro-dashboard-bundle" This is the library that encapsulates the official dashboard bundle (that sounds important) schema and assorted tools. Since now we have LAVA I wanted to take the chance and give it a better name Proposed names: -> lava-bundle -> lava-dashboard-bundle -> lava-test-container

So this project contains data to be used with what is now linaro-json? Certainly a name including "lava" makes sense. "lava-bundle-tools"? I guess it is dashboard specific to some extent, but I don't see us introducing another bundle concept in LAVA.

Cheers, mwh