February 5, 2018
The EE.next working group will drive the evolution and broad adoption of technologies derived from or related to the Eclipse Enterprise for Java (EE4J) project. Eclipse Enterprise for Java (EE4J) is an open source initiative to create technical specifications, implementations of those APIs, and technology compatibility kits for Java runtimes that enable development, deployment, and management of server-side and cloud-native applications. EE4J is based on the JavaTM Platform, Enterprise Edition (Java EE) standards, and uses Java EE 8 as the baseline for creating new specifications and implementations.
Eclipse Foundation projects will provide technical implementations of API specifications and TCKs. The working group will:
All Members must be parties to the Eclipse Foundation Membership Agreement, including the requirement set forth in Section 2.2 to follow the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the Intellectual Property and Anti-Trust Policies.
In the event of any conflict between the terms set forth in this Working Group's Charter and the Eclipse Foundation Bylaws, Membership Agreement, Eclipse Development Process, Eclipse Industry Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, process, or policy shall take precedence.
An entity must be at least a Solutions Member of the Eclipse Foundation, have executed the EE.next Participation Agreement once defined, and adhere to the requirements set forth in this Charter to participate.
There are four classes of EE.next membership - Strategic, Influencer, Participant, and Committer. Each of these classes is described in detail below.
The fees associated with each of these EE.next membership classes is shown in the tables in Schedule A. These are annual fees, and are established by the EE.next Steering Committee, and will be updated in this charter document accordingly.
The fees associated with membership in the Eclipse Foundation are separate from any EE.next membership fees, and are decided as described in the Eclipse Bylaws and detailed in the Eclipse Membership Agreement.
Strategic Members are organizations that view enterprise Java technology as strategic to their organization and are investing significant resources to sustain and shape the activities of this working group.
Strategic Members of the EE.next working group must be a Strategic Member of the Eclipse Foundation, and have a minimum of 4 developers participating on EE4J projects.
Influencer Members are typically organizations that view enterprise Java technology as a critical part of their organization's business operations. These organizations want to support the development and evolution of the enterprise Java technology ecosystem.
Influencer Members of the EE.next working group must be an Enterprise or Strategic Members of the Eclipse Foundation.
Participant Members are typically organizations that deliver products or services based on enterprise Java technology. These organizations want to participate in the development of the enterprise Java technology ecosystem.
Participant Members of the EE.next working group must be Solutions, Enterprise, or Strategic Members of the Eclipse Foundation.
Committer Members are individuals who through a process of meritocracy defined by the Eclipse Development Process are able to contribute and commit code to the Eclipse Foundation projects included in the scope of this working group. Committers may be members by virtue of working for a member organization, or may choose to complete the membership process independently if they are not. For further explanation and details, see the Eclipse Committer Membership page. To be a Committer Member of this EE.Next working group, they must also be covered by the EE.Next Participation Agreement once defined either via their employer, or in their personal capacity.
|Strategic Member||Influencer Member||Participant Member||Committer Member|
|Member of the Steering Committee||Appointed||Elected||Elected||Elected|
|Member of the Specification Committee||Appointed||Elected||Elected||Elected|
|Member of the Marketing Committee||Appointed||Elected||Elected||Elected|
|Member of the Enterprise Requirements Committee||Appointed||Appointed||N/A||N/A|
All matters related to Membership in the Eclipse Foundation and this EE.Next working group will be governed by the Eclipse Foundation Bylaws, Membership Agreement and Eclipse Working Group Process. These matters include, without limitation, delinquency, payment of dues, termination, resignation, reinstatement, and assignment.
Members who resign, or otherwise terminate their membership in the working group, lose their rights to access and use any private assets and data of the working group after the effective date of the termination.
This EE.Next working group is designed as:
In order to implement these principles, the following governance bodies have been defined (each a "Body"):
Steering Committee members are required to:
The Steering Committee meets at least twice a year.
Specification Committee members are required to:
The Specification Committee meets at least once per quarter.
The Marketing and Brand Committee members are required to:
Marketing Committee meets at least once per quarter.
The purpose of the Enterprise Requirements Committee is to provide Influencer members with insight and input into the current state and future roadmap of the working group, and to articulate their defined requirements as a means of formalizing recommendations and other input to the working group. Having Influencer Members fully participating in the working group leads to more direct, open, and transparent conversations between Influencer and Strategic members, and allows each of these stakeholders to create a common vision and roadmap.
It is expected that on an annual basis, Influencer Members shall have the opportunity to participate in the EE.Next Influencer Member Summit, where they will meet to study, review, and comment on the state of enterprise Java, and to gain insights important to their specific business operations. Strategic members are also expected to attend the Influencer Member Summit to provide their input and perspective.
By creating this committee and formalizing the Summit process, Influencer members shall gain early insight and be able to influence the state of the industry.
Enterprise Requirements Committee members are expected to:
The Enterprise Requirements Committee meets at least once per quarter.
The Enterprise Requirements Committee meets face to face on an annual basis at the EE.Next Influencer Member Summit.
The dispositions below apply to all governance bodies for this working group, unless otherwise specified. For all matters related to membership action, including without limitation: meetings, quorum, voting, electronic voting action without meeting, vacancy, resignation or removal, the terms set forth in Section 6 of the Eclipse Foundation Bylaws apply.
A representative shall be deemed to be in Good Standing, and thus eligible to vote on issues coming before the Body they participate in, if the representative has attended (in person or telephonically) a minimum of three (3) of the last four (4) Body meetings (if there have been at least four meetings). Appointed representatives on the Body may be replaced by the Member organization they are representing at any time by providing written notice to the Steering Committee. In the event a Body member is unavailable to attend or participate in a meeting of the Body, they may send a representative and may vote by proxy, which shall be included in determining whether the representative is in Good Standing. As per the Eclipse Foundation Bylaws, a representative shall be immediately removed from the Body upon the termination of the membership of such representative’s Member organization.
For actions (i) requesting that the Eclipse Foundation Board of Directors approve a specification license; (ii) approving specifications for adoption; (iii) amending the terms of the working group’s Participation agreement; (iv) approving or changing the name of the working group; and (v) approving changes to annual Member contribution requirements; any such actions must be approved by no less than two-thirds (2/3) of the representatives in Good Standing represented at a committee meeting at which a quorum is present.
This section only applies to the Steering Committee, Specification Committee, and the Marketing Committee.
All representatives shall hold office until their respective successors are appointed or elected, as applicable. There shall be no prohibition on re-election or re-designation of any representative following the completion of that representative’s term of office.
Strategic Members Representatives shall serve in such capacity on committees until the earlier of their removal by their respective appointing Member organization or as otherwise provided for in this Charter.
Elected representatives shall each serve one-year terms and shall be elected to serve from April 1 to March 31 of each calendar year, or until their respective successors are elected and qualified, or as otherwise provided for in this Charter. Procedures governing elections of Representatives may be established pursuant to resolutions of the Steering Committee provided that such resolutions are not inconsistent with any provision of this Charter.
All meetings may be held at any place that has been designated from time-to-time by resolution of the corresponding Body. All meetings may be held remotely using phone calls, video calls or any other means as designated from time-to-time by resolution of the corresponding Body.
No Body meeting will be deemed to have been validly held unless a notice of same has been provided to each of the representative in Good Standing at least thirty (30) calendar days prior to such meeting, which notice will identify all potential actions to be undertaken by the Body at the Body meeting. No representative will be intentionally excluded from Body meetings and all representatives shall receive notice of the meeting as specified above; however, Body meetings need not be delayed or rescheduled merely because one or more of the representatives cannot attend or participate so long as at least a quorum of the Body is represented at the Body meeting. Electronic voting shall be permitted in conjunction with any and all meetings of the Body the subject matter of which requires a vote of the Body to be delayed until each such representative in attendance thereat has conferred with his or her respective Member organization as set forth in Section Voting above.
The Body may undertake an action only if it was identified in a Body Meeting notice or otherwise identified in a notice of special meeting.
The Body may invite any member to any of its meetings. These invited attendees have no right of vote.
To be established by the EE.next Steering Committee. The fees for all classes of EE.next membership are $0 for calendar 2018.
1 The name EE.next is subject to change. For example, the brand name to replace “Java EE” has not yet been selected.
Back to the top