Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Naming the specifications

I can tell you there are conversations between Oracle and Eclipse about the use of Java.  I'm not a member of either organization (as you know), but I do hear about the discussions.  There is no "definitive statement" about the use or non-use of Java yet, but it will be required at some point.  I think we go ahead with this branding exercise to get a solid list of alternatives.  The pending Java trademark discussions between Oracle and Eclipse will definitely have a play on our culled list of options.  And, we'll have to use this "definitive statement" as the reason for removing some of the suggestions from consideration.

Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

From:        Mark Little <mlittle@xxxxxxxxxx>
To:        EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Date:        11/15/2017 07:02 AM
Subject:        Re: [ee4j-pmc] Naming the specifications
Sent by:        ee4j-pmc-bounces@xxxxxxxxxxx


On Wed, 15 Nov 2017 at 10:59, Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
Happy to help manage the process.


Point 2 below – we need to all agree some specified criteria that must be met.

I for one would also like something that lends itself to a striking pictorial logo design. Ideally a single noun or proper noun e.g. Foo or 1 adjective and 1 noun e.g. Big Foo; Small Foo; Red Foo; Foo Fighters! Avoiding acronyms.


Some contingency planning on what happens if all suggested names do not lend themselves to effective distinctive branding would also be useful.


I also think we need a definitive statement, while outlining the selection criteria, that the use of “Java” in the name is not allowed and the reasons why otherwise there will be a lot of debate in the community on why including it is best. While I’m happy to take the flack as a member of the PMC it would be helpful to state that it is out of our hands with clear legal reasons. I am assuming therefore that the Eclipse Foundation has requested licensing the Java trademark for this specific purpose and this has been refused or is not commercially viable.





From: ee4j-pmc-bounces@xxxxxxxxxxx[mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
13 November 2017 21:43

[ee4j-pmc] Naming the specifications


Greetings EE4J PMC Members!


We need a new brand name for the set of specifications that implemented by open source projects that fall under the Eclipse EE4J top level project. 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 (the EE4J community) need a brand name for this set of specifications. This brand name will also act the certification mark that can be used by implementations which are compatible with those specifications. 


With this in mind, we (the Eclipse Foundation) need the EE4J PMC to manage the process that we will initiate. We will be posting more details to describe the process and constraints shortly.


At a high level, the process will be as follows:

  1. Members of the community will be invited to enter their nominations (we'll open a channel for this soon);
  2. At the end of the nomination period, the names suggested by the community will be reviewed by the PMC, who will identify those names which meet the specified criteria; 
  3. That subset of names will put to a community vote using the CIVS system (this will provide a ranked set of choices); and
  4. The results of the vote will be delivered to the Executive Director of the Eclipse Management Organization who will engage in the required legal and trademark searches to ensure that the names are available for use;
Note that 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.


Please voice your concerns.






Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation
ee4j-pmc mailing list

To change your delivery options, retrieve your password, or unsubscribe from this list, visit
ee4j-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top