Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
MIME-Version: 1.0
From: Sean Owen <srowen@apache.org>
Date: Wed, 14 Sep 2016 09:21:35 +0000
Message-ID: <CAEccTyyh30rAzWkgTzZP0V28UvRsHO-76yCDJZEqYsZ6Vqs0ZQ@mail.gmail.com>
Subject: Is Spark Kinesis (non-assembly) module distributable via Maven?
To: legal-discuss@apache.org
Cc: "private@spark.apache.org" <private@spark.apache.org>
Content-Type: multipart/alternative; boundary=047d7bb0428411a478053c7442a7
archived-at: Wed, 14 Sep 2016 09:21:49 -0000

--047d7bb0428411a478053c7442a7
Content-Type: text/plain; charset=UTF-8

Hello legal-discuss@,

On behalf of Spark I'm writing to ask for opinions on the additional
question raised at
https://issues.apache.org/jira/browse/LEGAL-198?focusedCommentId=15471529&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15471529
.


In brief, Spark has several optional modules that are not distributed as
part of the main binary release. One of them is "Spark Kinesis", which
contains integration code for Amazon's Kinesis. (Note: here we are not
talking about the Kinesis _assembly_ module.) This module is built and
distributed as a binary artifact in Maven, however.

It does not itself contain any source or binary code from the Amazon
Kinesis client. However, this optional Spark Kinesis module requires the
Kinesis client of course. And, the Kinesis client is licensed under the
Amazon Software License, which is Category X.


http://www.apache.org/legal/resolved.html#prohibited says:
-----
CAN APACHE PROJECTS RELY ON COMPONENTS UNDER PROHIBITED LICENSES?
Apache projects cannot distribute any such components. As with the previous
question on platforms, the component can be relied on if the component's
licence terms do not affect the Apache product's licensing. For example,
using a GPL'ed tool during the build is OK.

CAN APACHE PROJECTS RELY ON COMPONENTS WHOSE LICENSING AFFECTS THE APACHE
PRODUCT?
Apache projects cannot distribute any such components. However, if the
component is only needed for optional features, a project can provide the
user with instructions on how to obtain and install the non-included work.
Optional means that the component is not required for standard use of the
product or for the product to achieve a desirable level of quality. The
question to ask yourself in this situation is:

"Will the majority of users want to use my product without adding the
optional components?"
-----

https://issues.apache.org/jira/browse/LEGAL-198 discusses closely-related
but not identical scenarios. For example, there the question is whether ASF
projects can distribute the recompiled binary code of a Category X
component, and that's not allowed.

Here, the licensing does affect the product (it is not just a build
dependency).

I see an argument for and against allowing publishing of Spark Kinesis in
Maven.

FOR:

Spark Kinesis is optional with respect to Spark, and thus so is Kinesis
client. Publishing it via Maven constitutes providing "instructions on how
to obtain and install the non-included work", Kinesis client.

AGAINST:

Spark Kinesis is a software product from the ASF in and of itself. If it
relies non-optionally on a Category X component, it may not be distributed.


Is there any view on which is more accurate in this context?
If the latter, does this forbid releasing Spark Kinesis in source form too?


Best,
Sean

--047d7bb0428411a478053c7442a7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello legal-discuss@,</div><div><br></div><div>On beh=
alf of Spark I&#39;m writing to ask for opinions on the additional question=
 raised at <a href=3D"https://issues.apache.org/jira/browse/LEGAL-198?focus=
edCommentId=3D15471529&amp;page=3Dcom.atlassian.jira.plugin.system.issuetab=
panels:comment-tabpanel#comment-15471529">https://issues.apache.org/jira/br=
owse/LEGAL-198?focusedCommentId=3D15471529&amp;page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:comment-tabpanel#comment-15471529</a> .</div><di=
v><br></div><div><br></div><div>In brief, Spark has several optional module=
s that are not distributed as part of the main binary release. One of them =
is &quot;Spark Kinesis&quot;, which contains integration code for Amazon=
9;s Kinesis. (Note: here we are not talking about the Kinesis _assembly_ mo=
dule.) This module is built and distributed as a binary artifact in Maven, =
however.=C2=A0</div><div><br></div><div>It does not itself contain any sour=
ce or binary code from the Amazon Kinesis client. However, this optional Sp=
ark Kinesis module requires the Kinesis client of course. And, the Kinesis =
client is licensed under the Amazon Software License, which is Category X.<=
/div><div><br></div><div><br></div><div><a href=3D"http://www.apache.org/le=
gal/resolved.html#prohibited">http://www.apache.org/legal/resolved.html#pro=
hibited</a> says:</div><div>-----</div><div>CAN APACHE PROJECTS RELY ON COM=
PONENTS UNDER PROHIBITED LICENSES?</div><div>Apache projects cannot distrib=
ute any such components. As with the previous question on platforms, the co=
mponent can be relied on if the component&#39;s licence terms do not affect=
 the Apache product&#39;s licensing. For example, using a GPL&#39;ed tool d=
uring the build is OK.</div><div><br></div><div>CAN APACHE PROJECTS RELY ON=
 COMPONENTS WHOSE LICENSING AFFECTS THE APACHE PRODUCT?</div><div>Apache pr=
ojects cannot distribute any such components. However, if the component is =
only needed for optional features, a project can provide the user with inst=
ructions on how to obtain and install the non-included work. Optional means=
 that the component is not required for standard use of the product or for =
the product to achieve a desirable level of quality. The question to ask yo=
urself in this situation is:</div><div><br></div><div>&quot;Will the majori=
ty of users want to use my product without adding the optional components?&=
quot;</div><div>-----</div><div><br></div><div><a href=3D"https://issues.ap=
ache.org/jira/browse/LEGAL-198">https://issues.apache.org/jira/browse/LEGAL=
-198</a> discusses closely-related but not identical scenarios. For example=
, there the question is whether ASF projects can distribute the recompiled =
binary code of a Category X component, and that&#39;s not allowed.</div><di=
v><br></div><div>Here, the licensing does affect the product (it is not jus=
t a build dependency).</div><div><br></div><div>I see an argument for and a=
gainst allowing publishing of Spark Kinesis in Maven.</div><div><br></div><=
div>FOR:</div><div><br></div><div>Spark Kinesis is optional with respect to=
 Spark, and thus so is Kinesis client. Publishing it via Maven constitutes =
providing &quot;instructions on how to obtain and install the non-included =
work&quot;, Kinesis client.</div><div><br></div><div>AGAINST:</div><div><br=
></div><div>Spark Kinesis is a software product from the ASF in and of itse=
lf. If it relies non-optionally on a Category X component, it may not be di=
stributed.</div><div><br></div><div><br></div><div>Is there any view on whi=
ch is more accurate in this context?</div><div>If the latter, does this for=
bid releasing Spark Kinesis in source form too?</div><div><br></div><div><b=
r></div><div>Best,</div><div>Sean</div><div><br></div></div>

--047d7bb0428411a478053c7442a7--