Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (athena.apache.org: domain of bimargulies@gmail.com
 designates 209.85.220.20 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=bUGIFxRCWQkzLn0CnIgJ1hg5q2hSKxjjT42ENpl9MdFC8aOWxUVmuREvfhpAyD127e
         BDf3bBzuZ0xOPu5urkUsvkDHI7T0JuXLCCjEJsaUefamof78sxQvkZq4UliXRTLL2g+F
         Juc/67JL9Ig+RnAHR/znSjBEzAMcF6SUVmf8g=
Message-ID: <61b5d9410811260453w46cd9bc2k310671e927c61fb@mail.gmail.com>
Date: Wed, 26 Nov 2008 07:53:07 -0500
From: "Benson Margulies" <bimargulies@gmail.com>
To: legal-discuss@apache.org
Subject: Re: Use of proprietary binaries
In-Reply-To: <3DC1628F-C87C-4A9B-B418-EBF061826E56@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <72c1350f0811211235t49f6d78al546ae1fe5f7ba958@mail.gmail.com>
	 <4929D317.8030208@rowe-clan.net>
	 <72c1350f0811240730v51e860c2v796dad66886f8f94@mail.gmail.com>
	 <2d12b2f00811251252x1d3fe1edqffe5196d249a7c34@mail.gmail.com>
	 <DEAF1074-6A95-421A-8A7B-EF317274EDFC@SUN.com>
	 <13F42DAB-56C8-47AB-A6D8-5A11C93C643A@gbiv.com>
	 <61b5d9410811251849r550661aav262b6c295fba9682@mail.gmail.com>
	 <D4834401-9B2E-451B-998A-9530FDEEF6C0@pobox.com>
	 <61b5d9410811260428qa6c9215m3db429a47f8c82b0@mail.gmail.com>
	 <3DC1628F-C87C-4A9B-B418-EBF061826E56@pobox.com>

I'm myself a bit befuddled by Hen's merging of the two threads into
one discussion of the idea of a read-only repository. If it helps
clarify, my somewhat impassioned message on this thread resulted from
the following bit of email billiards:

1) I post about w3c test cases on another thread.
2) OP of this thread posts on OpenJPA Jar
3) Hen posts to both suggesting read-only repo
4) Someone posts negative reaction to (3), perhaps more focussed on
OpenJPA, perhaps not, on this thread.
5) I post response very much focussed on w3c test cases.

So, sorry for any incremental confusion. I don't purport to have
anything to contribute on the OpenJPA front.

On Wed, Nov 26, 2008 at 7:38 AM, Geir Magnusson Jr. <geir@pobox.com> wrote:
> any hope you could un-hijack for clarity?
>
> On Nov 26, 2008, at 7:28 AM, Benson Margulies wrote:
>
>> I semi-hijacked this thread onto the subject of the W3C schema test
>> cases. The JAR question applies to the original topic of OpenJPA, and
>> the OP of that will presumably comment.
>>
>> On Wed, Nov 26, 2008 at 6:50 AM, Geir Magnusson Jr. <geir@pobox.com>
>> wrote:
>>>
>>> it's my understanding that this jar is needed to build the project?
>>>
>>> On Nov 25, 2008, at 9:49 PM, Benson Margulies wrote:
>>>
>>>> There are plenty of 'open source' license that are unacceptable for
>>>> materials in Apache repos, so restating the requirement for open
>>>> source does not strike me as adding much to the content here. Like
>>>> most discussions on this list, this is about the nuances of what
>>>> soi-disant open source licenses are acceptable for what Apache
>>>> purposes.
>>>>
>>>> When someone publishes a set of test cases and makes them freely
>>>> available, freely redistributable, but not freely modifiable, then
>>>> Hen's proposal is to set up infrastructure to store them read-only.
>>>>
>>>> We don't want to modify these. The whole point is to be able to
>>>> measure compliance against them as they are.
>>>>
>>>> As a reductio argument, consider the TCKs. They aren't even remotely
>>>> 'open source', but we store them in restricted repos because it is
>>>> essential to the efficient development of projects that need to be
>>>> tested against them.
>>>>
>>>> Here we have something less nasty by far than a TCK. I think that
>>>> there's an argument that these could be checked into ordinary repos
>>>> with some guidelines, but the idea of a special RO repo struck me as a
>>>> good compromise between avoiding the crazy 'download in every build'
>>>> process while reducing the risk that we would facilitate some
>>>> violation of the license.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Nov 25, 2008 at 6:45 PM, Roy T. Fielding <fielding@gbiv.com>
>>>> wrote:
>>>>>
>>>>> On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:
>>>>>
>>>>>> With respect, I think we are putting the cart before the horse.
>>>>>>
>>>>>> At issue is whether artifacts with unacceptable licenses can appear in
>>>>>> Apache public svn repositories.
>>>>>
>>>>> They can't.  Only open source is allowed in Apache's public svn.
>>>>>
>>>>> ....Roy
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> DISCLAIMER: Discussions on this list are informational and educational
>>>>> only.  Statements made on this list are not privileged, do not
>>>>> constitute legal advice, and do not necessarily reflect the opinions
>>>>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>>>>> official ASF policies and documents.
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> DISCLAIMER: Discussions on this list are informational and educational
>>>> only.  Statements made on this list are not privileged, do not
>>>> constitute legal advice, and do not necessarily reflect the opinions
>>>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>>>> official ASF policies and documents.
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> DISCLAIMER: Discussions on this list are informational and educational
>>> only.  Statements made on this list are not privileged, do not
>>> constitute legal advice, and do not necessarily reflect the opinions
>>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>>> official ASF policies and documents.
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> DISCLAIMER: Discussions on this list are informational and educational
>> only.  Statements made on this list are not privileged, do not
>> constitute legal advice, and do not necessarily reflect the opinions
>> and policies of the ASF.  See <http://www.apache.org/licenses/> for
>> official ASF policies and documents.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only.  Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF.  See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org