Issue Details (XML | Word | Printable)

Key: JSR358-7
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: sean_sheedy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
jsr358

can't change license after contribution made if contributor objects to license

Created: 21/Sep/11 02:54 PM   Updated: 08/Apr/14 07:47 PM
Component/s: Licensing
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: pcurran and sean_sheedy


 Description  « Hide

Process Document review

line numbers: JCP-2.8-21SEP2011-Redlined.pdf

205-207 - are contradictory. 205 requires Terms of Use to be provided so that "prospective EG members can judge whether they are compatible with the JSPA" but 207 allows the EG to change its collaboration tools after the EC begins. An EC member who believes the new tools' Terms of Use are not compatible with the JSPA has no recourse - after the IP cow is out of the barn - if they are in a minority (in fact no rules are provided for deciding how an EG can switch tools. Without rules the spec lead could do this dictatorially.

PC> What are you suggesting? That EGs must be locked into their original choice of collaboration tools - and that moreover the terms of use for these tools must be cast in stone - for the possibly multiple-year lifetime of the JSR? This isn't reasonable. Please make a specific suggestion in a separate issue.

SS> Suggest adding clause requiring unanimous vote of EC and past/present EG members to approve changes in licenses.



pcurran added a comment - 22/Sep/11 12:55 PM

As with http://java.net/jira/browse/JSR348-137 it's too late to resolve this. I've marked it Deferred.