Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » Eclipse Project Naming Framework (EPNF)
Eclipse Project Naming Framework (EPNF) [message #14376] Sat, 29 January 2005 02:09 Go to next message
Ed Burnette is currently offline Ed Burnette
Messages: 279
Registered: July 2009
Senior Member
Can anything be done about the acronym proliferation and general naming
chaos in Eclipse projects, especially new ones? We've got ETF (eclipse trust
framework), PTP (parallel tools platform), BIRT (business intel and
reporting tools), TPTP (test&performance tools platform), WTP (web tools
platform), ERCP (embeded rich client platform), EMF (eclipse modeling
framework), VE (visual editor), ECF (eclipse communications framework), AJDT
(aspectJ development tools), CME (concern manipulation environment), GMT
(generative model transformer), OMELET (open modeling environment with links
for extensions and transformations :-), WSVT (web service validation tools),
WST (web standard tools), JST (java standard tools), ERD (eclipse report
designer), WRD (web report designer), ERE (eclipse report engine), ECE
(eclipse charting engine), etc., etc..

We've got some project names starting with "Eclipse" and some not. Some
ending with "Framework" and some ending with "Platform" and some ending with
"Tools" and some not ending with anything special. Not to mention the ones
that combine two or more of these conventions. If many projects are the
"Eclipse X Framework" or "X Tools Platform" it leads to a lot of very
similar sounding names and acronyms, redundancy, and confusion.

One alternative would be to use simple words in the project names and their
corresponding package and newsgroup names. Not to pick on any one project,
but for example instead of "ETF" (Eclipse Trust Framework), I'd suggest
something like "Trust", with a package/plug-in name "org.eclipse.trust.*"
and newsgroup "eclipse.technology.trust". The words could be obviously
meaningful (for example, Platform, Update, Security, Trust, etc.) or more
like code names (Equinox, Pollinate), or somewhere in between (JFace). In
addition to being easier to read and remember I think a good name can give a
project more character and charm.

--
Ed Burnette
www.eclipsepowered.org
Re: Eclipse Project Naming Framework (EPNF) [message #14403 is a reply to message #14376] Sat, 29 January 2005 03:24 Go to previous messageGo to next message
Genady Beryozkin is currently offline Genady Beryozkin
Messages: 410
Registered: July 2009
Senior Member
+1


Ed Burnette wrote:

>Can anything be done about the acronym proliferation and general naming
>chaos in Eclipse projects, especially new ones? We've got ETF (eclipse trust
>framework), PTP (parallel tools platform), BIRT (business intel and
>reporting tools), TPTP (test&performance tools platform), WTP (web tools
>platform), ERCP (embeded rich client platform), EMF (eclipse modeling
>framework), VE (visual editor), ECF (eclipse communications framework), AJDT
>(aspectJ development tools), CME (concern manipulation environment), GMT
>(generative model transformer), OMELET (open modeling environment with links
>for extensions and transformations :-), WSVT (web service validation tools),
>WST (web standard tools), JST (java standard tools), ERD (eclipse report
>designer), WRD (web report designer), ERE (eclipse report engine), ECE
>(eclipse charting engine), etc., etc..
>
>We've got some project names starting with "Eclipse" and some not. Some
>ending with "Framework" and some ending with "Platform" and some ending with
>"Tools" and some not ending with anything special. Not to mention the ones
>that combine two or more of these conventions. If many projects are the
>"Eclipse X Framework" or "X Tools Platform" it leads to a lot of very
>similar sounding names and acronyms, redundancy, and confusion.
>
>One alternative would be to use simple words in the project names and their
>corresponding package and newsgroup names. Not to pick on any one project,
>but for example instead of "ETF" (Eclipse Trust Framework), I'd suggest
>something like "Trust", with a package/plug-in name "org.eclipse.trust.*"
>and newsgroup "eclipse.technology.trust". The words could be obviously
>meaningful (for example, Platform, Update, Security, Trust, etc.) or more
>like code names (Equinox, Pollinate), or somewhere in between (JFace). In
>addition to being easier to read and remember I think a good name can give a
>project more character and charm.
>
>
>
Re: Eclipse Project Naming Framework (EPNF) [message #14460 is a reply to message #14376] Sun, 30 January 2005 21:29 Go to previous message
Mike Milinkovich is currently offline Mike Milinkovich
Messages: 258
Registered: July 2009
Senior Member
I've never actually thought about this as a problem. But reading your post
does make me realize that it's not pretty out there.

Let me think about what we can do. I doubt that we can change history. But
we could certainly do a better job going forward.

/mike

"Ed Burnette" <ed.burnette@sas.com> wrote in message
news:ctfcqk$p0i$1@www.eclipse.org...
> Can anything be done about the acronym proliferation and general naming
> chaos in Eclipse projects, especially new ones? We've got ETF (eclipse
> trust
> framework), PTP (parallel tools platform), BIRT (business intel and
> reporting tools), TPTP (test&performance tools platform), WTP (web tools
> platform), ERCP (embeded rich client platform), EMF (eclipse modeling
> framework), VE (visual editor), ECF (eclipse communications framework),
> AJDT
> (aspectJ development tools), CME (concern manipulation environment), GMT
> (generative model transformer), OMELET (open modeling environment with
> links
> for extensions and transformations :-), WSVT (web service validation
> tools),
> WST (web standard tools), JST (java standard tools), ERD (eclipse report
> designer), WRD (web report designer), ERE (eclipse report engine), ECE
> (eclipse charting engine), etc., etc..
>
> We've got some project names starting with "Eclipse" and some not. Some
> ending with "Framework" and some ending with "Platform" and some ending
> with
> "Tools" and some not ending with anything special. Not to mention the ones
> that combine two or more of these conventions. If many projects are the
> "Eclipse X Framework" or "X Tools Platform" it leads to a lot of very
> similar sounding names and acronyms, redundancy, and confusion.
>
> One alternative would be to use simple words in the project names and
> their
> corresponding package and newsgroup names. Not to pick on any one project,
> but for example instead of "ETF" (Eclipse Trust Framework), I'd suggest
> something like "Trust", with a package/plug-in name "org.eclipse.trust.*"
> and newsgroup "eclipse.technology.trust". The words could be obviously
> meaningful (for example, Platform, Update, Security, Trust, etc.) or more
> like code names (Equinox, Pollinate), or somewhere in between (JFace). In
> addition to being easier to read and remember I think a good name can give
> a
> project more character and charm.
>
> --
> Ed Burnette
> www.eclipsepowered.org
>
>
Previous Topic:Eclipse Themes and Priorities
Next Topic:I want to find previous eclipse council documents.
Goto Forum:
  


Current Time: Sat Aug 30 16:28:44 EDT 2014

Powered by FUDForum. Page generated in 0.14039 seconds