Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.236 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Mon, 29 Apr 2013 10:58:26 -0700
Subject: Re: Are we supposed to include okhttp source in Cordova-Android?
Thread-Topic: Are we supposed to include okhttp source in Cordova-Android?
Thread-Index: Ac5FAyicpjmjT6aXSNCeYYKZyUOF/w==
Message-ID: <CDA40273.1DC35%fil@adobe.com>
In-Reply-To: 
 <CAK_TSXK=PYm=B3Un1VD4ndtr9YXiPL35mM8z_Fj127OwoPossQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Joe and I just looked at this.

The relevant apache policies (I believe) are "treatment of third party
works" [1] and "what are required third-party notices?" [2].

TL;DR: read the notice/license files of source being added into our
project, if the NOTICE file specifies to include a bit about the work,
copy that over to OUR NOTICE file. If the license differs from APL (but is
compatible), then we should add that license to our LICENSE file as well.

[1] http://www.apache.org/legal/src-headers.html#3party
[2] http://apache.org/legal/resolved.html#required-third-party-notices

On 4/29/13 10:54 AM, "Ian Clelland" <iclelland@google.com> wrote:

>I'm not a lawyer, and this is not legal advice ;) but OkHTTP is
>apache-licensed, as is Cordova, and I believe that the terms of the Apache
>license allow us to embed it for distribution.
>
>There's probably someone in Apache who is far more qualified than I to say
>what we can and should do, though.
>
>
>On Mon, Apr 29, 2013 at 1:49 PM, Joe Bowser <bowserj@gmail.com> wrote:
>
>> Hey
>>
>> I saw that okhttp was added, but I don't know if including the source
>> and as such re-distributing it this way is correct or not.  Is there
>> someone around to clarify whether it's OK for us to use the library in
>> this way in the project or not, or whether we have to do what we do
>> with commons-codec?
>>
>> Anyone know the correct answer?
>>
>> Joe
>>