This is an overview presentation about JCP organization, its roles, process, and output. With a detailed explanation of each group role and their output. In addition, to encourage community to participate in JCP, and being valuable members and experience input to the community. Agenda: http://egjug.org/page/java_ee_7_8_and_beyond

1. http://about.me/mohamedtaman

3. A Systems Architect & Design supervisor @ “e-finance”.
JCP, Executive Committee, Expert Group Member,
responsible for JSRs revision, evaluation, RI testing and
evangelist the new technologies specifications & JCP process
standardization.
Board member of “Oracle Egypt Architect Club”.
A frequent Speaker (JavaOne, Devoxx, Oracle Days, Tunis
JUG Day, jMaghreb, JEEConf & JDC... etc),
Consultant, Trainer, Blogger, & articles writer, books author
and tech. reviewer.
Regularly posts on my blog , and also on DZone & JCG
community.

5. Won The 11’s JCP annual award as outstanding Adopt-a-JSR participant

6. •
•
•
•
•
•
•
•
What is JCP (Java Community Process).
Who maintains JCP process?
JCP organization chart.
JCP.next.2 (JSR 355).
How JSR is developed.
Lifecycle of JSR, and its process.
What are Adopt-a-JSR & OpenJDK programs?
Being effective member in the community.
•
•
•
•
•
•
Promote your JUG.
Role of the JUG and leaders.
What is the benefits returned to you.
Where we are now and what is needed from you.
Success Story with MoroccoJUG.
Formation of EGJUG JCP activities program Group.

11. One ring to rule them all, one ring to find them,
One ring to bring them all and in the darkness bind them.

13. 
Established in 1998

A control center for developing standard
technical specifications for Java
technology.

Manages JSR lifecycle. The core output of
the JCP.

14. • PMO members.
• Executive committee Group.
• Group of Individuals (JCPs), Corporates,
JUGs.

15. • Java Specification Request:
– A single version of a Java Specification.
– Lead by a single leader called Spec Lead who
forms and manages a Expert Group (The
team who helping on the specification)

16. 1. Specification
– Detail document talks about the Spec. The real idea, its
components, integration with other components if any.
2. Reference Implementation (RI)
– Complete implementation of the spec. as proof of concept
(POC).
3. Technology Compatibility Kit (TCK)
– The working examples of the RI against Spec. Proof of the
working. And release the specification as final spec.

17. Is the TCK Correct?
Does the RI Confirm?
TCK
RI
Is the specification
unambiguous?
Spec.
Can you build an
implementation?

19. SE/ME EC
Combined
ME EC
JCP
Executive
Committee

20. • Because Java is One Platform and because we expect Java ME
and Java SE to converge over time, JSR 355 was introduced to
merge the two Executive Committees into one.
• This JSR will reduce the number of EC members to 25 and will
keep the same ratio (2:1) of ratified and elected seats.
– It makes no other significant changes to our processes.
• The JSR was completed in August 2012.
• Implementation began during the October 2012 annual JCP
elections and is completed in October 2013, during this year’s
elections.

21. JCP
Executive
Committee

22. • JCP Chair
– Leads the organization and manages the PMO.
• Program Management Office (PMO)
– Manages day-to-day operations of the organization.
• Executive Committees
– Define JCP governance, processes, and contractual terms of
membership.
– Vote on JSRs at defined stages through the process.
• Expert Groups
– Create JSRs (write the spec, develop the RI and TCK).
• Members
– Review specs, may participate in Expert Groups, vote in Executive
Committee elections

23. •
One Executive Committees.
•
EC has 25 members.
•
Oracle has a permanent seat on EC.
•
10 of the other 15 seats are ratified by Oracle.
•
Oracle nominates a candidate; the entire JCP membership approves
via ballot.
•
The remaining 5 seats are elected (any JCP member may nominate
themselves.)
•
Yearly elections reconfirm or replace one-third of the members.
•
ECs meet ~monthly by phone, 3 times a year face-to-face.
•
EC meeting minutes are public.

24. • The Executive Committee is expected to:
– Select JSRs for development within the JCP.
– Approve draft specifications for Public Review.
– Give final approval to completed Specifications and
their associated RIs and TCKs.
– Decide appeals of first-level TCK test challenges.
– Review and approve maintenance releases.
– Approve transfer of maintenance duties between
Members.
– Provide guidance to the PMO.

25. • Ratified Seats
– Serving a two-year term: Red Hat, Sociedade de Usuários da
Tecnologia Java - SouJava, IBM, Intel, Ericsson, Credit Suisse,
Fujitsu and Hewlett-Packard.
– Serving a one-year term: Gemalto M2M, Software AG, SAP,
Freescale, Goldman Sachs, Nokia, V2COM and TOTVS
• Open Election Seats
– Serving a two-year term: Eclipse Foundation, Twitter, London
Java Community and CloudBees
– Serving a one-year term: ARM, Azul Systems, Werner Keil and
MoroccoJUG (Represented by Me)

26. • The individual or institutional owner who drives the JSR.
– Recruits and organizes the activities of the Expert Group.
– Responsible for delivering the Spec, RI, and TCK.
• Intellectual Property rights to the technology incorporated
in the JSR accrue to the Spec Lead.
– Subject to obligations incurred under the JSPA.
• The Spec Lead is free to define the terms under which the
RI, and TCK will be licensed.
– Subject to obligations incurred under the JSPA.
• Oracle is the Spec Lead for the three existing Platforms:
Java ME, Java SE, and Java EE.

27. • The Expert Group is recruited and led by the Spec Lead.
– All members of the JCP are eligible to join.
– Participation by all interested parties is encouraged and
desirable.
– The EG works as a team to define the JSR and to develop the
Spec, RI, and TCK.
• The EG is free to define its own working style.
– When and how often it meets, how it makes decisions...
• Transparency is strongly encouraged.
– EGs must explain their transparency strategy..
• Public aliases, public issue list, Wikis, blogs...
– EGs must respond publicly to comments.

28. • Modifying JSPA document, to be more simple, evolve and
updated, with the following goals:
– IP policy, licensing, and open-source.
– The role of individual members in the JCP.
• Maintain compatibility guarantees.
• Embrace open-source licensing and development processes.
• Simplify IP-flow and licensing models.
• Enable even more openness, transparency, and participation.

29. Transparency
Are the keys of
new JCP
Strategy
openness
Community
participation

30. • Adopt-a-JSR is an initiative by JUG leaders to
encourage JUG members to get involved in a
JSR and to evangelize that JSR to their JUG and
the wider Java community, in order to increase
grass roots participation.
• Java EE 8 is scheduled to release in 2015 and
would love help from your JUG to adopt a JSR.
• As part of the Adopt-A-JSR program, I am trying
to gather interests in these APIs, and provide
these feedback to the Expert Group.

31. • There are 2 adopt programs out there:
• Adopt-a-JSR:
– for single JSR contribution under
– any platform, Java SE, ME, EE, or/and
Embedded.
– More info.
https://java.net/projects/adoptajsr/pages/Home
• Adopt-OpenJDK.
– Focuses totally on JDK JSRs.
– More info.
https://java.net/projects/adoptopenjdk/pages/Adop
tOpenJDK

32. Anyone who willing to spend their experience and time for the
community can join.
• As a non-member:
– Participate in OpenJDK, or Glassfish project.
– Review specifications and provide feedback.
– Test, play with RI and evangelist the technology.
• As a member:
– Sign JSPA.
(http://www.jcp.org/aboutJava/communityprocess/JSPA2.pdf)
– Vote on election.
– Join an expert group.
– Lead a JSR.
– Runs for EC.

33. •
•
•
•
•
•
•
Altruism.
Gain a wide Experience.
Fame and fortune.
Very Good point in your C.V.
Working with international members.
Learn process and etiquettes.
Socialize with java experts and leaders.

34. • Active Participation in the community
(consume & contribute both)
• At least 2 years of experience.
• Contributor in any project is a plus!
• Presented at least 2 JSRs (not yet final) in
JUG meeting.
• Must follow the JCP JSPA (will be provided
once a member is considered.)

35. • Primary Contact : Is me (Mohamed Taman)
via mohamed.taman@egjug.org mail.
• Responsible for:
– Motivate members to participate in JCP
– Encourage members to reviewing and provide
feedback.
– Guide members to join JSRs.
– Manage team for outstanding output to
community.

36. • Adopt WebSocket, JAX-RS, and JSON-P specifications.
• Participate in FishCAT program.
• Evangelist the JSRs and technologies in many conferences.
• Becomes MoroccoJUG member.
• Translate the Adopt-a-JSR Arabic page.
• Won JCP 11’s annual award for outstanding A-a-JSR participant.
• Joined 3 JSRs Expert Group.
• Become an EC member for elected seats.

37. See you in upcoming events

38. • http://jcp.org/en/participation/committee
• http://jcp.org/en/jsr/detail?id=355
• http://jcp.org/en/whatsnew/elections
• http://www.jcp.org/aboutJava/communityprocess/JSPA
2.pdf
• http://www.slideshare.net/JugChennai/jcp-the-jcp-andthe-future-of-java-by-heather-vancura-manager-jcpprogram-javaone-hyderabad