An Eclipse Foundation working group is a special-purpose consortia of Eclipse Members interested in supporting a technology domain. They are intended to complement the activities of a collection of Eclipse Foundation open source projects. Open source projects are excellent for many things, but they typically do not do a great job with activities such as marketing, branding, specification and compliance processes, and the like.
Joining is straightforward. All members may subscribe to the Jakarta.EEfirstname.lastname@example.org working group mailing list. To join the working group, your company representative can simply send an email to this list declaring your commitment to participate. There are no fees in 2018 to participate.
Committer members are also welcome to join. More information regarding committer membership, see the Eclipse Committer Membership page.
The current members are listed here.
Eclipse Foundation projects are self-governing meritocracies that set their own technical agendas and plans. The Project Management Committee for an Eclipse top-level project oversees the day-to-day activities of its projects through activities such as reviewing and approving plans, accepting new projects, approving releases, managing committer elections, and the like.
Working groups and their steering committees are intended to complement the work happening in the open source projects with activities that lead to greater adoption, market presence, and momentum. Specifically the role of the working group is to foster the creation and growth of the ecosystem that surrounds the projects.
Working groups do not direct the activities of the projects or their PMC. They are intended to be peer organizations that work in close collaboration with one another.
The projects manage their technical direction. The PMC may elect to coordinate the activities of multiple projects to facilitate the release of software platforms, for example.
Because the creation of roadmaps and long term release plans can require market analysis, requirements gathering, and resource commitments from member companies, the working group may sponsor complementary activities to generate these plans. However, ultimately it is up to the projects to agree to implement these plans or roadmaps. The best way for a working group to influence the direction of the open source projects is to ensure that they have adequate resources. This can take the form of developer contributions, or under the Member Funded Initiatives programs, working groups can pool funds to contract developers to implement the features they desire.
Because the Java EE ecosystem is a big place, and we want to ensure that there are roles for all of the players in it. We see the roles of the various member classes to roughly align as follows:
The Jakarta EE working group will be the successor organization to the JCP for the family of technologies formerly known as Java EE. It has several features that make it a worthy successor to the JCP:
No, not really. The JCP EC always had two mixed roles: as a technical body overseeing the specification process, and as an ecosystem governance body promoting Java ME, SE, and EE. In Jakarta EE the Steering Committee will be the overall ecosystem governance body. The Jakarta EE Specification Committee will focus solely on the development and smooth operation of the technical specification process.
That is actually a decision which will be made by the EE4J PMC, not the working group. However, it is a goal of the people and organizations working on creating this working group that the Java EE community move to more of a code-first culture. We anticipate and hope that the EE4J PMC will embrace the incubation of technologies under its banner. Once a technology has been successfully implemented and adopted by at least some in the industry, it can then propose that a specification be created for it.
There are four committees comprising the Jakarta EE governance structure - the Steering Committee, the Specification Committee, the Marketing and Brand Committee, and the Enterprise Requirements Committee. A summary of the make-up of each of the committees is in the table below.
|Strategic Member||Enterprise Member||Participant Member||Committer Member||Guest Member|
|Member of the Steering Committee||Appointed||Elected||Elected||Elected||N/A|
|Member of the Specification Committee||Appointed||Elected||Elected||Elected||Invitation Only|
|Member of the Marketing Committee||Appointed||Elected||Elected||Elected||Invitation Only|
|Member of the Enterprise Requirements Committee||Appointed||Appointed||N/A||N/A||N/A|
Back to the top