[JSR348-139] prices of licenses to be disclosed in the license terms Created: 21/Sep/11  Updated: 21/Sep/11  Resolved: 21/Sep/11

Status: Closed
Project: jsr348
Component/s: Process Doc
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: sean_sheedy Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Process Document review

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

289 - Require prices of all licenses to be disclosed in the license.

PC> If you insist on opening up this can-of-worms please open a separate issue. I predict that we won't be able to resolve this before Final Draft. (What we have now is a reasonable compromise. Let's see how it works in practice.)

SS> the text currently allows "reasonable" increase in price, which implies that the price is known to begin with. A change to the document requiring that prices be disclosed in the license provides necessary clarity allowing EG members to join an EG without first going through a price negotiation with the spec lead. This coupled with the requirement that an EG vote unanimously to approve a license helps ensure that a surprise "price increase" near the end of a JSR doesn't harm any particular EG member who has already made her contributions.

Comment by pcurran [ 21/Sep/11 ]

The current wording states that "complete copies of the proposed Specification, RI and TCK licenses" must be disclosed.

It doesn't say "complete copies of the proposed Specification, RI and TCK licenses must be disclosed but it's OK to keep the pricing secret."

We have this covered already...

Generated at Fri Feb 24 13:45:29 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.