At its first ever meeting in Toronto, members of the governing body of the Java Community Process (JCP) had what it called a series of face-to-face meetings this week to discuss such things as the future of Java and the pace and complexity of development. Also on the agenda: examining ways that open source development in Java can continue without being inhibited by the JCP.
The JCP, which is an open organization that holds the responsibility for the development of Java, usually tries to dispel with the teleconferences and never-ending phone calls among executives and meets in person every three or four months.
Under a committee that will be established by executive committee member Geir Magnusson, vice-president, Apache Software Foundation, the JCP will seek to define questions around whether or not Java Specification Requests (JSRs) — which are the actual descriptions of proposed and final specifications for the Java platform that move through various review and approval processes — allows the use of open source licenses.
At a session with the media after two days of meetings at Research in Motion Ltd. in Mississauga, Onno Kluyt, director of the JCP Program Management Office, said the JCP doesn’t prescribe a specific business model, but said the executive committee asked Magnusson to spearhead a group to monitor the open source issue. He said it isn’t the first time that open source has been discussed at the executive level.
Magnusson said the committee is still in the preliminary stages, but will look at ensuring that the JCP is compatible with what the open source community does.
Executive committee members hail from Sun Microsystems Inc., the creator of Java, Borland Corp., Apache and Fujitsu.
JCP.next, or the term the committee uses to outline the future direction of the JCP program, was a hot issue this week, according to Aaron Williams, manager, JCP PMO.
The group looks at what is next for the JCP, what changes can be made to the process and because the meeting follows the heels of the annual JavaOne conference, held this year in San Francisco, Williams said the meeting also touched on a post mortem of the event.
"It’s really a high-level view of what’s happening," he said.
Every year there are around 40 JSRs submitted to the community process and it takes an average of 450 days for a request to become a specification, Williams said.
Within the development community, programmers and Java-enabled organizations have been asking for a long time if the pace of that process can be shortened and Williams said that period of time is being reduced.
Time to market is a big issue for organizations, and if it is taking longer to get specs approved then it will take more time for companies to get their goods out the door, so getting the JSR creation time as efficient as possible, but keeping it as a collaborative effort is on the radar for the executive committee, he added.