[JSR358-48] A goal of RI/TCK IP working group should be access to the RI/TCK by community Created: 11/Jan/13  Updated: 02/Apr/15

Status: Open
Project: jsr358
Component/s: Intellectual Property, Licensing, Participation
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: starksm64 Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

One goal we would like to see more explicitly stated is that access to both the RI and TCK is to be granted freely (as in beer) to all community members. This would not necessarily include the right to declare an implementation as compatible or use any branding right. Dealing with the separation between the right to access and use the RI/TCK versus the support, certification cost recovery and branding have to be dealt with as separate concerns.



 Comments   
Comment by steven_g_harris [ 11/Jan/13 ]

I suggest we push for this as a requirement for all new JSRs and grandfather-in (if the Spec Lead wants) the existing and maintenance ones. This allows Oracle to keep its existing JCK in closed source form, but forces everyone, including Oracle, to do things openly on new JSRs. Thus, as SE and EE move forward, they will become more open as component JSRs are forced to be open. And if Oracle as spec lead on SE and EE can't deal with it, then they can just not include any of the new component JSRs that are open. Choose: open or don't include it in an umbrella spec.

Comment by lightguard [ 22/Feb/13 ]

You're saying all previous JSRs and their TCKs will remain closed, but future ones will be open?

Comment by pcurran [ 02/Apr/15 ]

We agreed on a compromise long ago: collaborative development processes and open-source licensing for RIs, and a Community TCK License for TCKs.

Generated at Mon Feb 27 15:54:41 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.