JCP.next, JSR 348 -- Towards a New Version of the Java Community Process
By Janice J. Heiss on Oct 17, 2011
The main improvements, at this stage, involve gaining greater transparency by requiring, rather than suggesting, that all development is done on open mailing lists and issue trackers. Furthermore, the recruiting process for Expert Group members will be publicly viewable, and ways to disclose TCK testing process results will be investigated - currently, the public is rarely aware of the results of the TCK testing process. All of these developments are designed to result in a more public, open, accessible and transparent JCP.
JSR 348 passed through a Pubic Review Ballot in mid-September with results for the SE/EE Executive Community showing 14 YES votes, one Abstain (Google) and one non-vote (VMWare). Oracle expects the initial version of JSR 348 to be concluded in October 2011, offering simple changes that will be quickly implemented. A subsequent second JSR, to be filed soon afterward, will tackle more complex issues, including any changes required to the Java Specification Participation Agreement (JSPA).
The JSPA is defined by the JCP as "a one-year, renewable agreement between you [[the participant in the agreement]] and Oracle America. It entitles you to review and comment on JSRs during the Community Review period - after they are initially approved by their sponsoring Expert Group and before they are open for Public Review. The agreement carries an annual fee, depending on your Member category."
The success of the Java community depends upon an open and transparent JCP, so JCP.next is worthy of our praise and attention.
With
considerable enthusiasm I attended “The Road to Java EE 7: Is It All
About the Cloud?” (23423) session, a panel of EE experts, late Wednesday
morning at JavaOne 2011. I always find Java EE developers and architects to be among
the smartest people around. Last year’s Java EE panel session, covered
on
