Re: [cross-project-issues-dev] Question about theBranding requirement fo

[Wayne Beaton <wayne@xxxxxxxxxxx>]

FWIW, to avoid trademark infringement issues, it's "Java development 
tools" (lower case)

Wayne

Thomas Hallgren wrote:
> I like the second alternative better and would go even furhter and skip the 
> abbreviations. Use:
>
> Eclipse - Platform
> Eclipse - Java Development Tools
> Eclipse - Plugin Development Environment
> Eclipse - Model Framework Technology
>
> We have a constantly increasing number of acronyms. GEF, EMF, PDE, JDT, ECF, 
> CDT, P2, STP, DTP, PTP, DSDP, GMT, M2M, to name just a few. Some starts with an 
> E to denote Eclipse, others don't. Personally, I find it harder and harder to 
> remember what they all stand for. What do they add to the mix aside from added 
> confusion? If branding is an issue, why not task all projects to come up with a 
> good name? Mylyn, Subversive, Babel, Dash, Orbit, Higgins, AspectJ, Tigerstripe, 
> etc. I find them much easier to remember.
>
> Regards,
> Thomas Hallgren
>
> Mik Kersten wrote:
> >
> > Yup, that one is always a challenge.  Seems like in this case we can punt on 
> > it and say that projects should follow what shows up in the metadata listing, 
> > but avoid having the term “Eclipse” show up twice.  This affects both Eclipse 
> > Project projects and those like EMFT.  That would imply:
> >
> > ·         Eclipse Project – Platform
> >
> > ·         Eclipse Project – Java Development Tools (JDT)
> >
> > ·         Eclipse Project – Plugin Development Environment (PDE)
> >
> > ·         Eclipse EMF – Model Framework Technology (EMFT)
> >
> > ·         Eclipse RT – Eclipse Communications Framework (ECF)
> >
> >  
> >
> > Alternatively with the Eclipse Project we could take the example of the 
> > special package naming, making the projects show up as:
> >
> > ·         Eclipse – Platform
> >
> > ·         Eclipse – Java Development Tools (JDT)
> >
> > ·         Eclipse EMF – Model Framework Technology (EMFT)
> >
> > ·         …
> >
> >  
> >
> > Mik
> >
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>