OpenJDK Web Site Terms of Use: FAQ

To allow work on specifications for Java SE JSRs to take place in the OpenJDK Community, right alongside the work on their reference implementations, in a way that satisfies the transparency requirements of version 2.8 of the Java Community Process (JSR 348).

The existing document was designed to cover contributions of code rather than specification material, and the latter must be governed by a different kind of license.

No, not at all! The JCP remains the governing body for the Java programming language, the Java virtual machine, and all Java SE APIs. This change merely allows work on Java SE JSRs to be done directly in the OpenJDK Community, in the most convenient and transparent way possible.

The principal changes are that JSR Expert Groups must hold their discussions on a public mailing list, they must use a public issue-tracking mechanism to record and track their progress, and they must publish their working documents for all to see.

No, but going forward all active Oracle-led Java SE JSRs with open-source reference implementations will be hosted here.

The active JSRs related to Java SE currently led by Oracle are:

• JSR 335: Lambda Expressions
• JSR 337: Java SE 8

Yes, as soon as practical.

The JSR 335 Spec Lead, Brian Goetz, will do that if the EG members agree to it.

Absolutely! The best way to initiate that is to propose an OpenJDK Project for your JSR's prototype and eventual reference implementation. Detailed guidance on how to host JSR work related to an OpenJDK Project will be available soon.

No, but if they want to make material contributions to a JSR then they will need to do so.

A list of OCA signatories is available here.

No, all SCA signatories are now considered OCA signatories.

Yes.

No, but if you want to become a member of the JCP then you'll have to sign the JSPA.

No, they will continue to be licensed under terms similar to those used for Java SE 7.

No! There will be no click-through agreements for JSR materials hosted in the OpenJDK Community.

The content on JSR EG mailing lists, which will now be public, will be licensed for comment and evaluation purposes only.

You may download and evaluate such materials, you may post comments on the materials back to locations that have the same terms (e.g., JSR EG mailing lists, web pages, issue trackers, and Mercurial repositories), and you may post modified versions of the materials to those locations. You may not use the materials in any other way.

Yes, that's correct.

The terms applicable to a mailing list will be displayed on the list's main page and also sent to all new subscribers. The terms applicable to an OpenJDK web page or issue will be displayed at the bottom of the page. The terms applicable to a Mercurial repository will be available in the LICENSE file at the root of the repository or, if appropriate, in the root of its containing forest.

No, please don't do that.

Some people will consider these terms to be less than ideal. Existing contractual obligations, however, require the use of these terms.

No, that section is about licenses for code rather than for specification material.

No, but the JCK remains available at no charge for OpenJDK-derived implementations under the terms of the OpenJDK Community TCK License Agreement (OCTLA).

Send your question to the general discussion list. (You'll need to subscribe first, otherwise your message will be discarded as spam.) We'll do our best to respond to all questions, but please understand that questions of a legal nature may require extra time to answer.