1 |
jpp |
1.1 |
From marvin@rectangular.com Mon Mar 23 01:37:59 2009 |
2 |
|
|
Received: by norkia.v3.sk (Postfix, from userid 99) id 718E880147; Mon, 23 |
3 |
|
|
Mar 2009 01:37:59 +0100 (CET) |
4 |
|
|
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on norkia.v3.sk |
5 |
|
|
X-Spam-Level: |
6 |
|
|
X-Spam-Status: No, score=0.1 required=5.0 tests=RDNS_NONE autolearn=no |
7 |
|
|
version=3.2.5 |
8 |
|
|
X-Greylist: delayed 2343 by SQLgrey-1.7.5 |
9 |
|
|
Received: from rectangular.com (unknown [68.116.38.202]) (using TLSv1 with |
10 |
|
|
cipher AES256-SHA (256/256 bits)) (No client certificate requested) by |
11 |
|
|
norkia.v3.sk (Postfix) with ESMTP id 8320C80148 for <lkundrak@v3.sk>; Mon, |
12 |
|
|
23 Mar 2009 00:37:50 +0000 (UTC) |
13 |
|
|
Received: from marvin by rectangular.com with local (Exim 4.63) |
14 |
|
|
(envelope-from <marvin@rectangular.com>) id 1LlXbT-0000Zw-2E for |
15 |
|
|
lkundrak@v3.sk; Sun, 22 Mar 2009 17:01:19 -0700 |
16 |
|
|
Date: Sun, 22 Mar 2009 17:01:19 -0700 |
17 |
|
|
To: Lubomir Rintel <lkundrak@v3.sk> |
18 |
|
|
Subject: FW: [Re: KinoSearch licensing and Fedora] |
19 |
|
|
Message-ID: <20090323000118.GA2217@rectangular.com> |
20 |
|
|
MIME-Version: 1.0 |
21 |
|
|
Content-Type: text/plain; charset=us-ascii |
22 |
|
|
Content-Disposition: inline |
23 |
|
|
User-Agent: Mutt/1.5.13 (2006-08-11) |
24 |
|
|
From: Marvin Humphrey <marvin@rectangular.com> |
25 |
|
|
X-Evolution-Source: imap://lkundrak%40v3.sk@mail.v3.sk/ |
26 |
|
|
Content-Transfer-Encoding: 8bit |
27 |
|
|
|
28 |
|
|
Lubomir, |
29 |
|
|
|
30 |
|
|
Here you go... |
31 |
|
|
|
32 |
|
|
Marvin Humphrey |
33 |
|
|
|
34 |
|
|
----- Forwarded message from marvin ----- |
35 |
|
|
|
36 |
|
|
To: Ian Burrell <ianburrell@gmail.com> |
37 |
|
|
Subject: Re: KinoSearch licensing and Fedora |
38 |
|
|
|
39 |
|
|
On Tue, Feb 10, 2009 at 04:21:04PM -0800, Ian Burrell wrote: |
40 |
|
|
> I am trying to package KinoSearch for Fedora. There were some |
41 |
|
|
> questions in the review[1] about the licensing. My understanding is |
42 |
|
|
> that KinoSearch is licensed under the GPL or Aristic. My impression |
43 |
|
|
> is that it doesn't contain any code licensed under ASL 2.0. |
44 |
|
|
|
45 |
|
|
Correct. It is all either original code or derived code, and all licensed |
46 |
|
|
under GPL or Artistic. I've been quite conscientious about never copying and |
47 |
|
|
pasting anything directly from Lucene, including documentation and comments. |
48 |
|
|
That allows me to claim a separate copyright and distribute the project under |
49 |
|
|
different but compatible licensing terms. |
50 |
|
|
|
51 |
|
|
> But that since it was derived from Lucene, it has to include the Apache |
52 |
|
|
> license text. |
53 |
|
|
|
54 |
|
|
That's correct, as per ASL 2.0 section 4.1. |
55 |
|
|
|
56 |
|
|
> Is this right? Is everything in KinoSearch licensed as "GPL+ or |
57 |
|
|
> Artistic"? Does the Apache license need to be included in the binary |
58 |
|
|
> package to satisfy the ASL? |
59 |
|
|
|
60 |
|
|
IANAL but... |
61 |
|
|
|
62 |
|
|
I think so. I've always assumed that derivations/redistributions of |
63 |
|
|
derivations still need to maintain compatibility with the license terms of the |
64 |
|
|
original -- otherwise the original author would quickly lose control of their |
65 |
|
|
work. It seems to me that you need to determine whether the GPLv3 your |
66 |
|
|
derivative work will be distributed under is compatible with both the |
67 |
|
|
KinoSearch license terms (which it obviously is) and the Lucene license terms |
68 |
|
|
-- which ought to be the case so long as you include that file and the |
69 |
|
|
existing notice embedded in the KinoSearch documentation. |
70 |
|
|
|
71 |
|
|
Best, |
72 |
|
|
|
73 |
|
|
Marvin Humphrey |
74 |
|
|
|
75 |
|
|
----- End forwarded message ----- |