Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of t.p.ellison@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=BPMU3ATk1UcvoSwXqtgIAcMMA2WdVXMCgTa97Wra6+eSyB8b3xTyUmrKaMPQYPsaXnRLqGicD+EK+pfDqGzOgzuL3Pe2HfImH/dRU3Hj4XX9YsrR/CoyQegCie/9+05MEEmYRdchb954/l1HQzNb0fPfmOn9oyQw94yZOm31Lrg=
Message-ID: <46A7B472.9090708@gmail.com>
Date: Wed, 25 Jul 2007 21:37:06 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 2.0.0.5 (Windows/20070716)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [buildtest2] Shall we Integrate mauve to BTI 2.0
References: <94d710af0707250657q29e73da0g123ae60306dab2ca@mail.gmail.com>
	 <c30d70960707250724l5222d16ev3221f226e46271a7@mail.gmail.com>
	 <46A76E82.30600@gmail.com>
 <c30d70960707251009t48c5564ma30445207c160253@mail.gmail.com>
In-Reply-To: <c30d70960707251009t48c5564ma30445207c160253@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Alexei Fedotov wrote:
> I'm trying to understand the link [1] you've send. Do I understand
> correctly the paragraph "YOU MAY include code within the Apache
> product necessary to achieve compatibility with a prohibited work
> [...]" applies to this case?

Well the whole document applies to our project, but in particular we
should be mindful of the scenarios that describe how we can interact
with Mauve code.

http://people.apache.org/~cliffs/3party.html#options-scenarios

Regards,
Tim

> 
> [1] http://people.apache.org/~cliffs/3party.html
> 
> On 7/25/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
>> Alexei Fedotov wrote:
>> > Hello Sean,
>> >
>> > Disclaimer: I'm not a lawyer. :-)
>>
>> Me neither, and when we are done discussing we might want to do a
>> gut-check with the legal discuss mailing list to ensure they approve our
>> proposed actions...that said...
>>
>> > Mauve has a pure GPL license [1]. Executing mauve tests is
>> > establishing a dynamic link between Harmony VM an these tests. For me
>> > this means that the linking infrastructure is tainted with GPL and
>> > cannot be a part of BTI. In other words, if you commit such
>> > infrastructure into Apache repository, the link may help FSF to claim
>> > that Harmony VM links to GPL-ed code and should be re-licensed under
>> > GPL.
>> >
>> > All, please correct me if I'm wrong. Thanks.
>>
>> There is no intent to redistribute the tests from Harmony, just enable
>> them for the end user.  There is an analogy with the performance
>> infrastructure we just voted on which has adapters to SPEC benchmarks
>> that are not part of Harmony.
>>
>> Regards,
>> Tim
>>
> 
>