Brand Name Selection

[waynebeaton]

We need a new brand name for the set of specifications that will be created by the new community process. This brand name will also become a certification mark in the industry for compatible, independent implementations. The open source projects that fall under the Eclipse EE4J top level project will be one such implementation. In short, we need a new name to replace “Java EE”. Much like the OpenJDK project implements the Java SE Platform specification, the EE4J projects will provide implementations of a set of specifications that we today call Java EE: we need a brand name for this set of specifications.

With this in mind, we are initiating a community process to select the brand name. This process will be managed by the EE4J Project Management Committee (“PMC”) with assistance from the Eclipse Management Organization (“EMO”). The name that is selected by this process must pass legal and other trademark searches to ensure that the names are available for use. As a result, it is possible that the favoured selection will not be the ultimate choice. The final decision will be made by the EMO Executive Director (“EMO(ED)”) in consultation with the PMC.

The process is described in greater detail below.

Nominations

Names can be nominated by anyone in the community via this GitHub Issue record.

Nominations will be open from November 15 until November 30, 2017 (UPDATED; note that the date had been incorrectly specified as November, 2018)

Naming Guidelines

All suggested names must conform to the following:

• They must conform to Oracle’s trademark usage guidelines. Amongst other things this means that the name cannot start with the word “Java”.
• They must conform to the Eclipse Foundation trademark guidelines.
• They must not be obscene, sexist, racist, controversial, etc., and they must not be frivolous (e.g. we’re not going to choose Boaty McBoatface or the like.)

Any suggested names which fail to meet the above criteria will be rejected.

Name Selection Process

The process will be executed as follows:

1. Members of the community will be invited to enter their nominations into the specified channel;
2. At the end of the nomination period, the names suggested by the community will be reviewed by the PMC to identify those which meet the criteria specified in the by the naming guidelines (depending on response, the PMC may decide to further reduce the list to a manageable size);
3. The PMC will then initiate a community vote using the CIVS system (which will produce an overall ranking of the choices); and
4. The results of the vote will be delivered to the EMO(ED) who will engage in the required legal and other trademark searches to ensure that the names are available for use, and consult with the PMC to make the final decision.

Since we have no idea what sort of community response to expect, it is difficult to time box anything other than the initial nomination process. But this will be an open and transparent process, and we invite the community to engage in all aspects of it. There is a great deal of legal, marketing, and community thought that goes into selecting an industry brand, so it’s important that we get this right. This may take a little time.

[gesker]

Perhaps using the "Open" prefix be useful in communicating an alignment with OpenJDK?

"Open" + 3 capital letters? E.g: EEJ, JEE, ESJ, etc.

The posts/discussion by @smsilva and @YoshiEnVerde above seemed reasonable: Open Enterprise Specs for Java (OpenESJ or OpenES4J) so +1 to them

And, this might be a plus in educating customers and non-technical managers quickly regarding the change. E.g. "We're coding to implementation FillInTheBlankContainer of OpenXYZ # on top of OpenJDK #..."

[jkbrock]

Coff EE ?

[Daniel-Dos]

Following the @psgrove suggestion template, another way would be:

OEJ -> Open Extensions for Java

Whatever the name chosen, it has to convey the message that it is still "Java EE" just with another name, so as not to have confusion of a new version of technology, just my opinion.

[manikmagar]

Perhaps for simplicity, or perhaps because they don't feel like promoting the Eclipse Foundation in their products.

@kjjaeger Probably marketing or organizational politics, I can't speak for that :smile:

[norswap]

SILE

Officially "Superb Interfaces for the Legacy Enterprise" Officiously "Suck It Larry Ellison"

[gbourant]

EJEE -> Eclipse Java EE -> Eclipse Java Enterprise Edition

[jeffzhang]

EE4J is great. J2EE->EE4J, looks like evolution (2->4 and change)

[steinsag]

Eclipse in the name is an absolute no-go as it could be easily mixed up with Eclipse IDE.

EE4J doesn't make any sense, because it is not the "Enterprise Edition FOR Java", but "Of Java".

Java should be in the name. Open should be in the name. Artificial names like ZEE are hard to market and it would take years to educate people on what's behind.

So Open Java Edition|Framework|Extensions|API, Open Java Enterprise Edition (OJEE), etc. are all fine with me.

[Ravisankar-Challa]

Eclipse should not be part of the name. People think it is just like Eclipse IDE. +1 for Open JEE(Java Enterprise Edition)

[yevster]

How about "JEnt" for "Java Enterprise" (pronounced same as "Gent")? Easy to say, easy to remember.

[antonarhipov]

"Eclipse Java Enterprise Framework" or "Eclipse Enterprise Java Framework"

[viktorcitaku]

+1 for “OpenEE” or “OpenJEE”

[rhuan080]

@Ravisankar-Challa, its a good question. The people can think it is only to Eclipse IDE. But, the Eclipse Foundation must be quoted. We must think about that.

[Daniel-Dos]

OJEE/OpenJEE looks very good, easy to pronounce and is similar to what we are accustomed to.

[YoshiEnVerde]

@steinsag @yevster What we're going to be doing here is not Java Anything, or Anything of Java. Java belongs to Oracle, and they keep an iron grip on that.

What we'll be working on, hopefully for years to come, is a set of specifications, compatibility kits, and implementations (and anything else we come up later on) to use with Java, to enhance the base Java specification.

That's why we need to use that pesky for in the names, because what we're doing is NOT (legally) Java in any way or form. It's something to add on top of Java, to enhance it.

Once again, I think most posters haven't taken the time to read the links in the OP about what we are allowed to use for the names.

[YoshiEnVerde]

Anything that will make it look as if these specs (or the implementations that come out of them) are in any way part of Java will slam against the Oracle legal wall.

We need to learn to dissociate the Java brand from the Java language. Java, as an Oracle brand, is the platform that allows for creation and execution of code in the Java language. This includes (but is not limited to) the specs for the language itself, the specs for the JVM, and the specs for the standard APIs.

What we're building here will be a separate set of API specs, plus all the surrounding mechanisms needed to implement, validate, certify and maintain those specs, their implementations, and any further specs that we might include.

[radcortez]

A little hard to follow all the participation with so many comments, but it's great to see :)

OpenEE would be my pick. Keeps alignment with OpenJDK, keeps EE in the name and reflect that EE is now Open.

[fernandor777]

+1 to OpenEE JEESUS made my day xD

[fernandor777]

But OpenEE was already taken https://www.openee.io :(

[radcortez]

@fernandor777 how about open.ee? :P

[manikmagar]

Oh man! This could be bad :(

On Nov 15, 2017, at 5:24 PM, Fernando Miño notifications@github.com wrote:

But OpenEE was already taken https://www.openee.io :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[patilca]

How about Eclipse JEEP (Eclipse Java extensions for Enterprise Platforms) ? Could also use a picture of a Jeep for logo?

[fernandor777]

@radcortez My concern is about trademark: "OpenEE's mission is to enable the energy efficiency marketplace of the future by transforming normalized metered energy savings into a procurable distributed energy resource."

[dcominottim]

Great effort from everyone! As I had previously suggested in the javaee-guardians mailing list,

• Eclipse Open Standards for Java or Eclipse OS4J (originally proposed as Eclipse OSJ)

For those who are interested in the reasoning, here is the link to the original email:

https://groups.google.com/d/msg/javaee-guardians/RA4jEvFfmAs/OT-QVP0dAQAJ

[fernandor777]

Initials are a legacy and old habit, nowadays names are most used: Meteor, Sinatra, Django, Express, etc. So why not pick a representative name instead ugly initials (JEE)? For (bad) example: Bee.io, Swarm.io, EEtc...

[tskaufma]

Since these are Specifications normally bundled with Application Servers, what about Application Server Specifications? Logo could be a donkey, would show they are hard working and dependable.

[Emily-Jiang]

My 1st pick is OpenJEE, which follows the same name convention of OpenJ9, and it clearly says Java. My 2nd pick is OpenEE. I like "Open" in the name.

[struberg]

+1 for OpenEE

reason: the 'Open' part emphases a clear change to the current situation. And the 'EE' part is familiar to all of us, tech folks and managers. So we should keep it

[crucoba]

OpenEJS — Open Enterprise Java Specifications

[kevinhooke]

OpenEDK (Enterprise Dev Kit) or OpenEJDK (Enterprise Java Dev Kit) to complement OpenJDK

[kjjaeger]

I would be ok with the full name being something like Eclipse OpenEE, as long as vendors are allowed the option of just calling their implementations OpenEE compliant (no Eclipse in front) kind of like MicroProfile.

[kjjaeger]

If people really hate abbreviations we could just call it Eclipse WebProfile or WebProfile for short.

[m-reza-rahman]

I must also admit if retaining the EE acronym is a goal (which is legitimate enough as probably the safest renaming path), Eclipse Open EE (Enterprise Extensions for Java?) is pretty compelling.

[juneau001]

I like Eclipse Open EE if it is available for use. I also really like Eclipse JOE (Java Open Extensions).

[juneau001]

When the open sourcing was first announced, we had some discussions over naming. I remarked that I liked the name "Deft" if the community had to choose an entirely new name.

[ghost]

+1 for OpenEE

[rarguello]

+1 for “OpenEE”

[ghazyami]

OpenJXF = Open Java Extensions Framework

[rugi]

Omnia Profile.

[iamdvr]

Name without eclipse word would better for future

[sgulci]

Please don't use Enterprise on naming it is not what it is, Open Java Extension (or API) can be good

[lprimak]

Summer... I kid I kid

[kthoms]

EMOJEE = Eclipse Modular Open Java Enterprise Extensions

[vlumi]

Not being a fan of coffee, I always prefer tea (or TEE?). Timeless enterprise architecture/edition?

[kwakeroni]

+1 for OpenJEE - which aligns nicely with OpenJDK (as mentioned before)

[ttoine]

+I for Open JEE.

But if we want to be compliant with Eclipse Foundation branding rules, we should add Eclipse before. So: Eclipse Open JEE.

[crucoba]

1. OpenJEK: Open Java Extensions Kit

2. OpenJFK: Open Java Facilities Kit

El 16 nov. 2017 10:00 a. m., "Antoine THOMAS" notifications@github.com escribió:

+I for Open JEE. Question, what about "Open EJE" -> Open Eclipse Java for Entreprise.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/eclipse-ee4j/ee4j/issues/1#issuecomment-344857842, or mute the thread https://github.com/notifications/unsubscribe-auth/AIJZT5OWG5Dnk0_XCnQJY0GqWnT1vx_Lks5s2_mzgaJpZM4QfLeR .

[jakubnabrdalik]

BOGUS: bunch of good, useful specifications

[keilw]

@juneau001 The mascot could be called "Deft Punk"? ;-)

[gersonZaragocin]

I agree with stopping use of Eclipse and Enterprise words but the meaning of Edition is meaningless also. What we are going to name is a Specification or API's set. So maybe Open Java Specification OJS is a suited one. That along with versioning year and month scheme will give us something like OJS 18.04 for instances of the specs