Java community process program

Java community process program

The JCP gives you a chance to have your own work become an official component of the Java platform and to offer suggestions for improving and growing the technology. Either way, everyone in the Java community benefits from your participation. That’s one of the reasons the JCP is open to everyone.

• Observer
• Registered user
• Associate Member
• Partner Member
• Full Member

• a visual guide to Participation in the JCP by Key Events
• a list of privileges for each type of Member
• a flowchart showing which Membership applies (reproduced graphically below)
• a list of participant roles in the JCP

1. all specifications developed using the JCP (Early Draft Reviews, Public Review Drafts, Proposed Final Drafts, Final Releases)
2. all proposals for new or revised specifications (JSR Reviews)
3. all proposed error corrections and changes to existing specifications (Maintenance Review Drafts)
4. all Expert Group communications for JCP 2.8 and above JSRs
5. a public Issue Tracker for all JCP 2.8 and above JSRs
6. a public archive of all working documents for JCP 2.8 and above JSRs

An Observer becomes a registered user by registering an account on jcp.org. You retain all the Observer privileges, but registered users can also create a watch list of JSRs, apply to become a Member of the JCP, nominate to participate on a JSR as an Expert Group Member, and/or nominate to participate on a JSR as a Contributor (though one must be a Member to be accepted as Expert Group Member or Contributor).
There are three types of Membership in the JCP that registered users may apply to become: Associate Members, Partner Members, and JCP Members. Each applies to a particular type of participation, and are described in the following paragraphs. Please use the appropriate contact alias if you have any questions.

There are three types of JCP Membership, each of which is explained in the following sections. Note that if a person wishes to participate under more than one Membership, each Membership requires the use of a distinct user account/registration.

Associate Members are individuals who wish to be listed as Contributors to one or more JSRs, but who sign the Associate Membership Agreement rather than the Java Specification Participation Agreement. Associate Members can be Contributors to JSRs’ Expert Groups, can attend JCP Member events, and can vote in the annual Executive Committee elections for the two Associate seats. These privileges are displayed in the Membership Classes chart. Please use the appropriate contact alias if you have any questions.

Partner Members are Java user groups and other non-profit organizations who wish to promote Java and encourage developer participation in JCP activities. Partner Members sign the Partner Membership Agreement rather than the Java Specification Participation Agreement. Partner Members can serve on the Executive Committee, can attend JCP Member events, and can vote in the annual Executive Committee elections for the ratified and elected seats. These privileges are displayed in the Membership Classes chart. Registered users who wish to represent an existing Partner Member should request to be associated with that Partner Membership: log in, click «My Profile,» then click «request Member association.» On the resulting form, select your organization from the list and click «submit.» Once the Partner Member confirms it, your account will be given Partner Member privileges. Please use the appropriate contact alias if you have any questions.

Full Members are organizations or individuals who sign the Java Specification Participation Agreement. Full Members can serve on the Executive Committee, vote in the annual Executive Committee elections for the ratified and elected seats, can be listed as Contributors to JSRs, can serve on JSRs’ Expert Groups, can attend JCP Member events, and can lead JSRs. These privileges are displayed in the Membership Classes chart. Representing a Full Member Registered users who wish to represent their Full Member employers should request to be associated with that Full Membership: log in, click «My Profile,» then click «request Member association.» On the resulting form, select your organization from the list and click «submit.» Once the Full Member confirms it, your account will be given Full Member privileges. If you are an individual Full Member and you wish to instead represent your Full Member employer, you need to first register a new account on jcp.org, using the e-mail address associated with the employer (the old account will not be used). Then you can follow the same process as for registered users in the previous paragraph. In this case, please also send mail to admin @jcp.org with the subject line «Replace individual membership with [name of employer]’s membership.» Please use the appropriate contact alias if you have any questions.

There are no fees for JCP Membership. JCP Members can participate in a variety of roles:

Any Associate Member or Full Member can nominate a person to be a Contributor on a JSR’s Expert Groups. A Contributor is publicly recognized as having made contributions to a JSR.

1. actively shape the content and direction of new and revised Java specifications (Expert Group),
2. review comments from Members and the Public and use them to improve the quality of a specification (Community Review,Public Review),
3. a JCP Member on an Expert Group may assume responsibility for maintaining a specification after it is written, taking on the Maintenance Lead role (Maintenance Lead).

Any Full Member can submit a proposal for a new JSR. Once the JSR is approved by the Executive Committee, the Member begins to lead the JSR, with one or more representatives of that Member acting as Specification Lead(s).

1. choose the other Members of the Expert Group,
2. guide the work of the Expert Group on the content and direction of the Java specification,
3. provide the Reference Implementation for the JSR,
4. are responsible for completing the Technology Compatibility Kit,
5. usually become the Maintenance Lead of JSRs they direct to Final Release,
6. produce the milestones of the JSR to be posted on jcp.org (Early Draft Review, Public Review, Proposed Final Draft, et cetera)

1. review and vote to approve or reject new JSR proposals,
2. review and vote to approve or reject Public Review drafts,
3. review and vote to approve or reject Final Approval Ballots,
4. review and vote to approve or reject Maintenance Reviews,
5. review and provide guidance on licensing terms of JSRs,
6. decide appeals of first-level TCK test challenges,
7. decide when JSRs that have not made sufficient progress through the JCP be withdrawn,
8. collaborate on revisions to the JCP and the JSPA

Depending on the JSRs that you plan to participate in there are two different agreements that you need to sign. The so-called JSPA 2 is for submitting your JSR proposals and for participating in JSRs that use JCP 2.5, 2.6, 2.7, 2.8-2.10. The so-called JSPA 1 is for participation in JSRs that use JCP 1.0 or 2.1. You can request this document by contacting the PMO. On each JSR page it says which JCP version it uses. Broadly speaking, all of the different JCP versions fall into three types: JSRs without an Executive Committee (JCP 1.0), JSRs with an Executive Committee (2.0-2.7), and JSRs with an Executive Committee and new transparency requirements (2.8+).

Note that JCP 2.8 and above JSRs are required to operate in a fairly different and distinct manner from earlier JSRs, both in terms of transparency but also in terms of ballot timing/duration and the operation of the Executive Committee. For an overview of JCP 2.8 and above changes, please see the section of the Spec Lead Guide that talks about JCP 2.8 and above.

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

jcp-org/jcp

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

Welcome to the Java Community Process (JCP) project

This is the public project for general discussions about JCP program. Primarily it is used for reporting progress on milestone postings.

Источник

Java community process program

The JCP program holds the responsibility for the development of Java technology. As an open, inclusive organization of active members and non-member public input, it primarily guides the development and approval of Java technical specifications. Anyone can register and join the JCP and have a part in its process, and you don’t even have to join to contribute as a public participant.

The work of the Java Community under the JCP program helps to ensure Java technology’s standard of stability and cross-platform compatibility, enabling it to operate on hundreds of millions of devices, from desktop computers to consumer electronics to industrial robots.

Just as important, the JCP program continually grows the platform’s specification portfolio to meet the emerging technology needs of developers and organizations globally who depend on Java technology.

Everything you need to know about submitting and reviewing Java Specification Requests, including all current requests, sorted by their stage in the review process.
Go to JSR Overview

If you haven’t done so, register for the site, then login and create your personalized watch list, termed “My JSRs”, participate in the message board discussions, review your profile and others participating under your JCP Membership (if you represent a JCP member) under “My Profile”.

Stay on top of the latest changes that are shaping the JCP’s technology, organization and procedures. View the latest JSR updates and the JCP program calendar.
Go to Updates

• Timeline View Take a look at the overall schedule of events for the Java Specification Request (JSR) process
• Glossary The JCP is built on a specific language of its own, and here are definitions to the terms you will need to know.

The JCP has gone through many revisions for improvement since its founding on December 8, 1998. The most current and important procedures for working with the JCP is available at The Java Community Process Program. The Java Community Process Program page is a good reference for anyone who plans to become a JCP Member and wants to review the process and procedures in detail. Go to JCP Procedures Overview

In the About JCP section there are also links to a current list of JCP program members, information on the Executive Committee (EC), the annual elections and the home of Programs & Awards.

Here are answers to the questions we receive most often.

Like to get involved? Anyone can join the JCP and have a part in its process, and you don’t even have to join to contribute as a public participant. Here are the pages that will help you become a member of the JCP and register for the site.
Go to Participation Overview

Here you will find a collection of helpful documents and guides, including training, the Spec Lead Guide, JCP Datasheet, Whitepapers, the TCK Tools & Info, and multimedia content.
Go to List of Resources

Read the latest on What’s Being Said about the JCP, catch this month’s news in the JCP PMO Newsletter, read the Press Releases, News Stories, and Success Stories.
Go to Press Overview

Источник