commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: [all] preparing initial commit
Date Tue, 18 May 2010 05:38:11 GMT
On Mon, May 17, 2010 at 11:21 AM, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
> On Sun, May 16, 2010 at 11:25 PM, Jacob Beard <jbeard4@cs.mcgill.ca> wrote:
>> Hi,
>>
>> I'm currently working to prepare the initial commit for my Google
>> Summer of Code project. I have a quick question regarding external
>> libraries. My project currently uses a few libraries which are
>> licensed under liberal, non-copyleft licenses. A list of these
>> libraries and their associated licenses is as follows:
>>
>> Mozilla Rhino - MPL
>> Dojo JavaScript toolkit - BSD/AFL dual license
>> Selenium - Apache 2.0 License
>> js-beautify - something a bit non-standard:
>> http://github.com/einars/js-beautify/blob/master/license.txt
>> json2 - Public Domain
>>
> <snip/>
>
> I'll first address the licenses and then get to the how to include the
> libraries bit.
>
> You may have seen the following categorization of licenses we use
> (Category A is generally easier to incorporate than B):
>
>  http://www.apache.org/legal/3party.html#category-a
>
>  http://www.apache.org/legal/3party.html#category-b
>
> Given that, the above list you have looks OK:
>  * Assuming we'll only depend on Rhino binaries
>  * The js-beautify license seems reasonable, we may have to ping the
> ASF Legal Affairs committee for a definite answer

js-beautify license == MIT.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message