| | JCP 2.6 is the most transparent and accessible iteration in the program's evolution to date, said the JCP Management Office and the Executive Committees in a statement. This latest version will enable both JCP and non-JCP members to contribute their input to an early review Java Specification Review (JSR) cycle, thereby opening the doors to developers to get more involved. | Lawyers for the concerned company said they cannot be sure the results of the process are legally pure, said Patrick Curran, chair of the Java Community Process (JCP), during a panel session on open standards development at the QCon conference in San Francisco on Wednesday afternoon. The JCP serves as the process for updating Java standards. Curran would not name the company. | Now, over a year after his appearance at JavaOne, Hunter says he has abandoned his own Java standardization work, and critics are saying that the Java Community Process (JCP) that Sun uses to create Java standards is losing momentum as vendors find success in defining their own de facto Java standards. | As of March 9, 2004, the Java Community Process (JCP) is operating under a new set of rules designed to encourage more participation by a broader range of developers and simplify the process of creating compatible Java technology APIs. The JCP program is the open community process used to develop and revise Java technology specifications, reference implementations (RIs), and technology compatibility kits (TCKs) since 1998. Today, more than 230 publicly submitted Java Specification Requests (JSRs) are in development through the JCP, with 46 percent in the final stages, and the organization has grown to more than 700 company and individual members. Better yet, operating under its new provisions, known as JCP 2.6, the JCP is now a more inclusive, accessible, and responsive organization for all, ready for growth in many new directions. | Sean Sheedy was recently elected a JCP ME Executive Committee and is soliciting feedback on what developers think the EC should be addressing. | In similar ways, JCP 2.6 encourages more community members to be involved in the JSR process. Offering a relatively quick review period -- hopefully several months earlier than the current average -- will open the opportunities for broader public participation. | As of March 9, 2004, the Java Community Process (JCP) is operating under a new set of rules designed to encourage more participation by a broader range of developers and simplify the process of creating compatible Java technology APIs. Better yet, operating under its new provisions, known as JCP 2.6, the JCP is now a more inclusive, accessible, and responsive organization for all, ready for growth in many new directions. | | Have an opinion about the individual's role in developing Java standards? Discuss this article in the Articles Forum topic, Should More Individuals Join the JCP?. | This JSR will not itself define any new features or enhancements; it will, rather, enumerate features and enhancements defined in other JSRs or through the JCP maintenance process. It is expected that most of the effort in the Mustang release will be toward product quality (bug fixing) and stability, with relatively less work going into new APIs and other kinds of features. | Welcome to the JCP Watch. This column hopes to inspire all Java developers to participate in defining the future of the Java platform by taking an active part in the JCP. This column will cover individual Java Specification Requests (JSR's) submitted to the JCP and explain each in simple, lucid terms. The intent is to equip developers with adequate background information and knowledge to analyze the JSR, provide feedback and collaborate with other members of the community to shape the direction of the Java platform. | Earlier this month, the Program Office of the JCP announced a new version of the Java Community Process, JCP 2.6 (JSR 215: http://www.jcp.org/en/jsr/detail?id=215). The changes were based on collective feedback of the Java community and the Program Office has made some significant alterations to make the whole process of developing Java Technology Specifications more community focused, transparent and efficient. | You probably remember back in those distant days at school, learning about how a bill becomes a law (don't worry, there aren't any tests here!). Well, in many ways the Java Community Process is similar. The JCP defines how an idea for changes to the Java API becomes a specification request, is fleshed out into a specification, and is then reviewed and refined, until it is implemented. Let's look at how this process works. |
|