Re: [udig-devel] namespace policy

[Jody Garnett <jody.garnett@xxxxxxxxx>]

On 17/04/2010, at 5:05 PM, andrea antonello wrote:

As professor Rigon pointed out he needs to have code to point to in
his publications. If the code starts with the name of a different
company than his, that will not work. I can understand that and I can
understand that this will be the problem also for other companies.

Thinking. Community plugin is obviously appropriate. If Dr Rigon wants to donate his code to the project and have it merged into the existing project is the only point at which matters at all. Donated code should be merged or otherwise integrated and meet the project QA guidelines.

Can you proceed in a community plugin? I am mostly concerned with merging code into existing plugins and defining the api in a consistent fashion.

Also I learned exactly fom you that the uDig users are developers, not
unly gis users, since udig is an sdk. So they see what happens in the
code, not in the about of the application, which they will never open.

Indeed; so what are the options:

- plugin name

- package name

- @author tags

- branding contributions

The "net.refractions.udig.catalog.grass" package did not make sense to you? I figured it was contributing the grass format to the catalog; here is another idea of breaking things down:

Plugin  *net.refractions.catalog.grass":

- net.refractions.catalog.grass.Activator - plugin activator

- com.hydrologis.jgrass - implementation

Still seems a bit inconsistent.

So I once again propose 2 things:
1) the contributor chooses the base namespace and the non-company part follows strict guidelines
or
2) udig gets a generic namspace (I would wonder what refractions think about it, don't think they would agree)

If you are interested in something neutral the best long term solution would be to join the eclipse foundation and use an "org.eclipse.udig" or "org.eclipse.gis.uidg" package and plugin names.

But as I said, first let's find a solution for the namespace.

If you are interested in something neutral the best long term solution would be to join the eclipse foundation and use an "org.eclipse.udig" or "org.eclipse.gis.uidg" package and plugin names.

Jody