karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Third-Party Licensing Policy
Date Fri, 10 Jan 2014 04:44:08 GMT

It's a difference between inclusion, usage, and reference.

For instance, GPL license is a intrusive license. It means that any 
software that use a code under GPL has to be itself under the GPL 
license. That's why you can't use GPL in a Apache project. It's the case 
for usage, inclusion or reference.
LGPL is a bit permissive in the cave of reference. LGPL is a Category X 
for inclusion and usage. It means that it's not possible to use LGPL if 
the project embeds some jar under LGPL, or ship some code (like 
copy/paste) under LGPL. However, if you just reference the project 
without embedding it, and it's an user action to actually download and 
add the LGPL jar, it's fine.

Regarding your question:
1/ category A
2/ category A
3/ category A and B
4/ category A and B (and we have to "publish" the changes)
5/ all
6/ category A and B


On 01/09/2014 11:35 PM, Krzysztof Sobkowiak wrote:
> Hi
> I have some licensing questions.
> I have found following page http://www.apache.org/legal/3party.html
> which defines 3 categories of third party licenses. According to this
> page LGPL v2.1 is category X, but further remark says, the
> LGPL-v2.1-licensed work can be listed as system requirements but can not
> be included  by Apache products. I'm not good in licensing but I try to
> understand it.  Is the category of LGPL really B (and the page should be
> corrected) or is the LGP category X.  In the second case, can we still
> list Hibernate in Karaf features (e.g. using the remark about listing of
> system requirements)?
> Assume following use cases of third-party work usage:
> 1. reference 3rd-party library as (maven) dependency and use the classes
> in ASF code
> 2. reference 3rd-party library as (maven) dependency and use the classes
> only in ASF configuration files (e.g. blueprint.xml)
> 3. include/copy some unmodified 3rd-party code (e.g. some classes) in
> ASF project
> 4. include/copy some 3rd-party code (e.g. some classes) in ASF project
> and modify it
> 5. list some 3rd-party libraries in Karaf features, but not include them
> as binaries in one of the Karaf distributions
> 6. list some 3rd-party libraries in Karaf features, and  include them as
> binaries in one of the Karaf distributions in system repository
> Could anybody please answer which of above points are allowed for
> following 3rd-party works
> a. category A as the whole category - I assume, all above use cases are
> allowed in this category, is it ok?
> b. category B as the whole category
> c. category X as the whole category
> d. LGPL
> e. GPL
> f. EPL
> I have chosen Karaf as sample ASF project, but it could be any other ASF
> project, e.g. ServiceMix or Aries
> Do the rules from the page mentioned above apply only for ASF projects
> or for any project licensed under Apache License?
> Best regards
> Krzysztof
> On 03.01.2014 11:51, Jean-Baptiste Onofré wrote:
>> LGPL is category B (not X), so we can reference it but not "include"
>> it: it's what we do.
>> FYI, in Karaf 3.0.0, I've already added a hibernate feature.
>> Regards
>> JB
>> On 01/03/2014 11:46 AM, Freeman Fang wrote:
>>> Though it's a very useful feature, I'm not sure if we can add it in
>>> Karaf, as Hibernate is under LGPL license, can we?
>>> -------------
>>> Freeman(Yue) Fang
>>> Red Hat, Inc.
>>> FuseSource is now part of Red Hat
> --
> Krzysztof Sobkowiak
> JEE & OSS Architect | Technical Architect @ Capgemini
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <mailto:krzys.sobkowiak@gmail.com> |
> Twitter: @KSobkowiak

Jean-Baptiste Onofré
Talend - http://www.talend.com

View raw message