 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 364: Broadening JCP Membership
JCP version in use: 2.11 Java Specification Participation Agreement version in use: 2.0 Description: This aims to broaden JCP participation by defining new membership classes, changing existing membership categories, enabling participation by the community, and ensuring the appropriate Intellectual Property commitments from JCP Members. Expert Group Transparency: Public Project Page Public Communications Issue Tracking Team
The following information has been updated from the original proposal.
2019.05.09:
2014.07.11: 2.14 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:A java.net project will host all communication mechanisms. The home-page of this project will contain pointers to the mailing-lists, Wiki, document archive, discussion forum, and issue tracker, and will explain how members of the public can observe and participate in the activities of the Expert Group. - Is the schedule for the JSR publicly available, current, and updated regularly? Yes, we are on schedule. - Can the public read and/or write to a wiki for the JSR? Yes, our wiki is the home page of our java.net project: https://java.net/projects/jcpnext4/pages/Home - Is there a publicly accessible discussion board for the JSR that you read and respond to regularly? Yes: https://java.net/projects/jcpnext4/lists - Have you spoken at conferences and events about the JSR recently? Yes, GeeCon in Poland and Devoxx UK - Are you using open-source processes for the development of the RI and/or the TCK? Not applicable. - What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA? https://www.java.net/javanet-web-site-terms-use - What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state. https://java.net/jira/browse/JCPNEXT4
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification Submitting Member: Oracle America, Inc. Name of Contact Person: Heather Vancura E-Mail Address: heather.vancura Telephone Number: +1 831 239 8177 Fax Number: - Specification Lead: Heather Vancura E-Mail Address: heather.vancura Telephone Number: +1 831 239 8177 Fax Number: - Initial Expert Group Membership: The EC will form the Expert Group: https://jcp.org/en/participation/committee Supporting this JSR: ARM
Section 2: Request
2.1 Please describe the proposed Specification:This JSR will make changes to the Process Document, and the Executive Committee's Standing Rules, introduce new classes of membership along with a corresponding contributor agreement, and a strengthened employer Intellectual Property commitment. In addition to broadening participation, this JSR has goals of further improving the organization's processes, correcting problems that have become apparent over recent years, and clarifying language to reduce ambiguity. There may be additional changes to this JSR based on the progress of JSR 358, A major revision of the Java Community Process. The updated version of the Process Document will apply to all new JSRs commenced after its completion and to future Maintenance Releases of existing JSRs. The Executive Committee intends to strongly encourage - though it cannot require - that it should also be adopted by in-progress JSRs. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)This JSR will address all Java platform editions. 2.3 The Executive Committees would like to ensure JSR submitters think about how their proposed technology relates to all of the Java platform editions. Please provide details here for which platform editions are being targeted by this JSR, and how this JSR has considered the relationship with the other platform editions.Not applicable. 2.4 What need of the Java community will be addressed by the proposed specification?This JSR will pull the membership and participation related discussions out of JSR 358, and focus on the next version of the JCP program, while the JSR 358 EG continues to work on the more significant changes to the JCP and the JSPA. Since opportunities to modify the JSPA are rare, the Expert Group for JSR 358 will take whatever time is necessary to thoroughly review and modify this critical document. In the meantime, this JSR will focus on the membership and participation areas that can be addressed and bring them to completion, prior to the major revision of the JSPA through JSR 358. 2.5 Why isn't this need met by existing specifications?See above. 2.6 Please give a short description of the underlying technology or technologies:Not applicable. 2.7 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)Not applicable. 2.8 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?Not applicable. 2.9 Are there any security issues that cannot be addressed by the current security model?Not applicable. 2.10 Are there any internationalization or localization issues?Not applicable. 2.11 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?This JSR will produce a new version of the JCP Process document, a contributor-type of Membership agreement, a strengthened employer Intellectual Property commitment, and a revision of the EC Standing Rules. As explained in section 2.2 the new version of the Process Document will not replace the existing ones but they will deprecate them. The new version of the Standing Rules will immediately replace the existing version. 2.12 Please describe the anticipated schedule for the development of this specification.JSR submittal: April 2014 Early Draft Review: June 2014 Public Draft Review: September 2014 Proposed Final Draft: November 2014 Final Approval Ballot: December 2014 2.13 Please describe the anticipated working model for the Expert Group working on developing this specification.The EC will form the Expert Group for this JSR. Heather VanCura will act as Spec Lead with assistance from the JCP Chair, Patrick Curran, and the PMO will provide administrative assistance as necessary. In addition to working on this JSR during regularly-scheduled EC meetings, additional teleconferences will be scheduled as necessary. Since it is likely that only a subset of EC members will attend these additional meetings, their results will be reported back to the full Executive Committees for review and approval. In addition to teleconferences and face-to-face meetings, the Expert Group will make extensive use of email and collaborative tools such a Wiki and issue-tracker, as explained in the next section. 2.14 Provide detailed answers to the transparency checklist, making sure to include URLs as appropriate:A java.net project will host all communication mechanisms. The home-page of this project will contain pointers to the mailing-lists, Wiki, document archive, discussion forum, and issue tracker, and will explain how members of the public can observe and participate in the activities of the Expert Group. - Is the schedule for the JSR publicly available, current, and updated regularly? The document archive will contain a copy of the schedule, which will be updated as necessary. - Can the public read and/or write to a wiki for the JSR? We will use the Wiki as a one-way channel of communication (from the EG to the public.) The public will be able to read all our documents, and to respond with comments via the public mailing-list. - Is there a publicly accessible discussion board for the JSR that you read and respond to regularly? We will provide a discussion forum, but the experience of JSR 348 suggests that the public would prefer to use the mailing-list. - Have you spoken at conferences and events about the JSR recently? We have discussed at several conferences the general idea of broadening participation in the JCP. - Are you using open-source processes for the development of the RI and/or the TCK? Not applicable. - What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA? The standard java.net Terms of Use will apply. - Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR? It will point to the project home-page for the JSR, which will in turn provide all necessary information about the communication mechanisms used by the Expert Group. Note that this section has been updated from this original proposal.
2.15 Please describe how the RI and TCK will de delivered, i.e. as part of a profile or platform edition, or stand-alone, or both. Include version information for the profile or platform in your answer.Not applicable. 2.16 Please state the rationale if previous versions are available stand-alone and you are now proposing in 2.13 to only deliver RI and TCK as part of a profile or platform edition (See sections 1.1.5 and 1.1.6 of the JCP 2 document).Not applicable. 2.17 Please provide a description of the business terms for the Specification, RI and TCK that will apply when this JSR is final.Not applicable. 2.18 Please describe the communications channel you have established for the public to observe Expert Group deliberations, provide feedback, and view archives of all Expert Group communications.The Expert Group will conduct business on the experts@jcpnext4.java.net mailing list. All mail sent to this alias will be copied to the observers@jcpnext4.java.net to which members of the public may subscribe for reading and writing. 2.19 What is the URL of the Issue Tracker that the public can read, and how does the public log issues in the Issue Tracker?A JIRA issue tracker (https://java.net/jira/browse/JCPNEXT4) will be used. The public will be able to log issues directly into the issue-tracker. 2.20 Please provide the location of the publicly accessible document archive you have created for the Expert Group.Documents will be archived at https://java.net/projects/jcpnext4/downloads. The observers mailing list will be archived at https://java.net/projects/jcpnext4/lists/observers-mailing-list/archive. Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.The Proposal from the March 2014 EC Meeting 3.2 Explanation of how these items might be used as a starting point for the work.The documents referenced above describe the current structure and operation of the JCP and form the basis for evolving the rules of the community. The proposal from the March 2014 EC Meeting describes the proposed path forward with the JSR. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
