www-jcp-open mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [Draft] New ASF/JCP Policies
Date Sat, 30 Jun 2007 02:23:17 GMT

On Jun 29, 2007, at 7:17 PM, Jeff Genender wrote:

> Geir Magnusson Jr. wrote:
>> On Jun 29, 2007, at 7:06 PM, Justin Erenkrantz wrote:
>>> On 6/29/07, Jeff Genender <jgenender@apache.org> wrote:
>>>> Well...ultimately I think thats for Sun to decide.  They call them
>>>> different names and they appear to have a different terms of  
>>>> use, thus
>>>> they are different, no?  Do other Apache projects that pass TCKs  
>>>> have
>>>> the same restrictions on licensing as using a JCK?  If so, then  
>>>> we have
>>>> a really big problem on our hands...if not, then there is a  
>>>> difference?
>>> They are the same in the sense that the spec lead can place whatever
>>> terms on the TCK that they like pursuant to the terms of the JSPA  
>>> and
>>> other agreements.  In the J2SE case (which has a JCK - but from a
>>> legal perspective, it is much the same as a TCK), Sun - as the spec
>>> lead - put additional restrictions on the test suite that we believe
>>> are in conflict with their other agreements with us.  -- justin
>> Agreed.
>> It's a TCK.  There's no special carve out in the JSPA for the TCK for
>> Java SE.
>> Java SE is a spec like any other spec.  It has a number, an expert
>> group, a spec lead and is governed by the JSPA.
>> It shouldn't be treated any differently than other TCKs.
> Ok...are there different licenses attached to it, or does it fall  
> under
> our agreement with Sun?  That really is the answer on whether they are
> different or not.  I am asking out of being slightly ignorant, so take
> it for what its worth ;-)

It's irrelevant with respect to the idea of pushing NDAs over the side.

To answer the question, it's being offered under a license that we  
won't accept. OTOH, the BEA TCK that we use (I forget which JSR) is a  
model license (IMO) with no NDA requirements or restrictive terms.


>> geir

View raw message