Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Wed, 22 Jun 2016 16:01:01 +0000 (UTC)
From: "Robert Metzger (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.12704304.1396026625000.26207.1466611261062@Atlassian.JIRA>
In-Reply-To: <JIRA.12704304.1396026625000@Atlassian.JIRA>
References: <JIRA.12704304.1396026625000@Atlassian.JIRA> <JIRA.12704304.1396026625109@arcas>
Subject: [jira] [Commented] (LEGAL-198) Amazon Software License
 compatibility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 22 Jun 2016 16:01:03 -0000


    [ https://issues.apache.org/jira/browse/LEGAL-198?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15344=
602#comment-15344602 ]=20

Robert Metzger commented on LEGAL-198:
--------------------------------------

I have another question on this issue, regarding the binary redistribution =
of code licensed under the AmazonSL.

Similar to Apache Spark, Apache Flink recently added a Kinesis connector as=
 an optional module into our repository.
If users want to use the Kinesis connector, they have to build it from sour=
ce, using a special flag on the maven command.

Flink soon plans to release a new version, containing the Kinesis connector=
. I wonder if we can distribute the maven artifacts (binaries) of the optio=
nal module to maven central, as part of the release.
Since Kinesis is using Google protobuf V2.6.1, but Flink depends on protobu=
f 2.5.0, we need to relocate ("shade") the protobuf version used by Kinesis=
 into a different namespace. This effectively means that one maven artifact=
 the Flink project deploys to maven central contains binaries licensed unde=
r the AmazonSL.

From above discussions, I got that in Spark's case its okay to link to Amaz=
onSL licensed software, because the linking happens on the user side. In th=
e case I've described, we would redistribute modified binaries of a restric=
ted use license as part of an Apache release.

I guess the likelihood that we can not release the artifact like this is cl=
ose to 99%, but I still wanted to ask, because this issue is causing me a l=
ot of trouble, and this solution would be the easiest one for me.

> Amazon Software License compatibility
> -------------------------------------
>
>                 Key: LEGAL-198
>                 URL: https://issues.apache.org/jira/browse/LEGAL-198
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Matei Zaharia
>
> We recently received a patch to add support for the Amazon Kinesis data s=
ource in Apache Spark, which uses the following library: https://github.com=
/awslabs/amazon-kinesis-client licensed under the Amazon Software License: =
https://aws.amazon.com/asl/. Would it be okay to have a Maven dependency on=
 this library in an Apache project? From a quick look at the license, it se=
ems reasonable, but I=E2=80=99d like to double-check. The one restriction t=
hat may be strange is "3.3 Use Limitation. The Work and any derivative work=
s thereof only may be used or intended for use with the web services, compu=
ting platforms or applications provided by Amazon.com, Inc. or its affiliat=
es, including Amazon Web Services, Inc.=E2=80=9D. However, it also says "de=
rivative works shall not include works that remain separable from, or merel=
y link (or bind by name) to the interfaces of, the Work", so I'm not sure o=
ur project would be a derivative work.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org