Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of simon@webmink.com designates
 74.125.82.43 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Question related derivative code based on our Apache licensed
 code
From: Simon Phipps <simon@webmink.com>
In-Reply-To: <4F044D22.80303@googlemail.com>
Date: Wed, 4 Jan 2012 14:17:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DDF5FA3-990F-47F6-AB61-21F7C2C7FCF2@webmink.com>
References: <4F04398A.4080701@googlemail.com>
 <71222C9A-8295-4C19-A91E-FE678CF1E5B2@webmink.com>
 <4F044D22.80303@googlemail.com>
To: ooo-dev@incubator.apache.org


On 4 Jan 2012, at 12:59, J=FCrgen Schmidt wrote:

> On 1/4/12 1:08 PM, Simon Phipps wrote:
>> My personal opinions on this, naturally:
>>=20
>> On 4 Jan 2012, at 11:35, J=FCrgen Schmidt wrote:
>>=20
>>> In detail if a derivative project merge our now Apache licensed code =
with their code that was based on the former Oracle licensed LGPL code. =
This code becomes automatically Apache licensed, correct?
>>=20
>> Probably not, no. The existing LGPLv3 licensed code remains LGPLv3 =
licensed, and as a requirement of the LGPLv3 the new code added to it =
has to be made available under the LGPLv3 as well. As a consequence, the =
resulting modified work will be licensed under LGPLv3. The Apache code =
that was added remains under the Apache license too (which is OK since =
there is no conflict between the terms of the AL and LGPLv3).
>>=20
> are you sure?

Pretty sure, yes. Rob and Ross appear to agree.

> For me this special situation seems to be a little bit different. =
Either you go forward with the old code and the old license header and =
can't merge to the new code. Or you move forward with the new one and =
keep the new license headers and put your change on a different license. =
Where you would make the difference which code is from which code base. =
For me it sounds practical impossible because the many thousand files =
with more or less the same code.
>=20
>=20
> It is really a special situation, isn't it. It would be interesting to =
hear what a lawyer things about it.
>=20
> Juergen
>=20
>=20
>>> If yes, does it mean that we can use the changes on this code in our =
code as well if it is publicly available?
>>=20
>> No.
>>=20
>>=20
>> S.
>=20