[news.eclipse.technology.ecomm] Project Names (was Re: An abstract confe

[Li-Te <li-te_cheng@xxxxxxxxxx>]

Hi Scott,

Scott Lewis wrote:
> BTW, I think it's probably going to make sense to change the name of 
> this project to something like 'Eclipse Communications Framework' or 
> 'ecf' rather than 'ecomm'.  Obviously, at this stage of the project it's 
> a good time to get such names nailed down, and I admit to a certain lack 
> of creativity on my part for ecomm.

Except for EMF, I think most of the other Eclipse project names don't 
have the word "Eclipse" in them (e.g. GEF, BIRT, RCP, SWT, ADJT, JDT, 
VE, etc), so I would drop "Eclipse" from the name.

Also, many Eclipse project names are fairly descriptive (Graphical 
Editing Framework, Visual Editor, Standard Widget Toolkit, Concern 
Manipulation Environment, etc). Although personally I do like the 
cool-sounding names like Hyades, Stellation, Koi, etc, I'd follow the 
majority - and people will (hopefully) immediately understand what the 
project is about in a descriptive name.

Among the "descriptively named" projects (e.g. SWT, AJDT, GEF, etc), I 
don't see any Eclipse projects with acronyms longer than 4 characters, 
so maybe 4 words maximum would be a good target.

Finally, choosing a descriptive name could be a useful exercise to help 
understand the essence of this project.  Choosing words involves 
reflecting on the core goals and scope of this project.

Here's one core goal: There seems to be a strong desire to have 
alternative implementations and you want to encourage your audience to 
not only use this framework, but create their own alternate 
implementations with it (given the discussions about P2P versus 
server-client, SIP, XMPP, etc).  This suggests, something like 
"extensible", "interface", "abstract", etc should be part of the name of 
this project.

"Communications" sounds fine (it might be confused with "business 
communications" = "advertising", but that's okay).  Same for 
"Framework", given the heavy discusson about APIs and alternate 
implementations.

So, I'd go for a name something like "Extensible Communications 
Framework (ECF or XCF)"...

This is probably a lot of overkill for just a name, but that's my two 
cents. :)

Best,

Li-Te