JSR358-92: Create a standard Community TCK License

apastsya commented 9 years ago

Jira issue originally created by user pcurran:

Create a standard Community TCK License modeled on the OpenJDK Community TCK License Agreement (OCTLA).

This license would grant access to the TCK to all participants in a JSR's collaborative RI-development project.

apastsya commented 7 years ago

Comment created by heathervc:

At the January JCP EC Meeting, EC Members were encouraged to add their comments for discussion here.

apastsya commented 7 years ago

Comment created by ivar_grimstad:

This would definitely be a good thing as it would simplify the choosing of appropriate license for the spec leads. It should be compliant with existing popular open source licenses and use as simple language as possible to make it understandable for non-open-source-expert-lawyers.

apastsya commented 7 years ago

Comment created by simonis:

The OCTLA has several shortcomings:

it only allows certification of the GPLv2 licensed OpenJDK code (but not of any independent implementation)
communication about the TCK and its contents is only allowed between signers of the OCTLA
signing the OCTLA is a manual process which requires approval from Oracle and can last several weeks to several month
Java SE TCKs under OCTLA are only available for released version of Java SE

It would be desirable to simplify the access to the Java SE TCK trough a simple click-through license which allows open communication about its contents. Early access versions of the TCK should be made available to the community in the same way like early access builds of the Java SE reference implementation are already made available. Notice that this already happens for commercial Java licensees, but not for the broader community so this is a legal/business and not a technical problem.

jcp-org / jsr358

JSR358-92: Create a standard Community TCK License #63