Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Short names and URLs
If the web sites for all the EE4J projects were under http://www.eclipse.org/ee4j/, that would at least make the naming consistent.  Ditto https://projects.eclipse.org/projects/ee4j/.  Is there some reason not to do that?

Wayne Beaton wrote on 12/13/17 02:33 PM:
The project space is absolutely a hierarchy. e.g. look at the "Related Links" on the right of https://projects.eclipse.org/projects/ecd

I tend to argue against making a hierarchy any deeper than <root>/<tlp>/<project> because making it deeper adds work that doesn't add value.

We can make the website hierarchical. We tend not to do this because it makes restructuring harder (e.g. moving to a different Top Level Project requires a URL change). But we can do it.

But we can certainly make the website http://www.eclipse.org/ee4j/jms if that's desired.

Wayne

On Wed, Dec 13, 2017 at 5:23 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
In the cases where the official project name is of the form "Eclipse Project for Wombat", then using http://www.elcipse.org/ee4j-wombat and http://projects.elipse.org/projects/ee4j.wombat seems reasonable, as long as it's applied consistently to all projects of that form.

We should probably start updating our Project spreadsheet with the repository names, and add another column for the short name.  Some of the existing repo names probably don't make sense as short names in the larger context of the flat Eclipse namespace.  We might need to add an "ee4j" prefix to more of these names.  Is that going to be a problem if it makes the names more unpredictable?

It's too bad the Eclipse project and web site namespace isn't a hierarchy...


Wayne Beaton wrote on 12/13/17 02:04 PM:
We have a notion of a "short name" for Eclipse projects that is, effectively, the machine or technical name for the project. The short name is used in website URLs (e.g. http://www.eclipse.org/egit or http://download.eclipse.org/webtools). 

The project's full id is the id of the parent project with the short name appended (e.g. tools.buildship). The full id is used in the "project info" page (e.g. http://projects.eclipse.org/projects/tools.buildship) and when interacting with the Eclipse IP Team. 

We also also use the short name as a repository prefix. So, we'll have paths like:

...

As with project names, my understanding is that we have to be sensitive to trademarks in URLs. In places where the short name will not otherwise be qualified, we'll prepend "ee4j-" to the short name.

e.g. Eclipse Project for JMS will have the short name "jms" and id "ee4j.jms". The custom website URL will be:


I'm concerned that this makes the URL way less obvious (i.e. hard to guess) than I'd like. Most people, however, will probably be looking for the Git repo, and--of course--search will work.

But we'll keep the other URLs as sane as we can. 

e.g.


Does this make sense?

Wayne

--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation


_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top