You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Fabio Aiub Sperotto <fa...@gmail.com> on 2013/01/17 16:51:38 UTC
Licenses: using Jena with other project
Hello guys,
I don't know where send this question. I´m using Jena like a base framework
to my programming library (project is a master dissertation). My library
will be free software. But, can I spread my project under GNU-GPL license
and keeping de jena packages under Apache license?
Will I have conflict licenses? If yes, how cai i spread my work using Jena?
(I'm not modifying Jena, just using your several methods).
(Soon all project will be uploaded in Github)
--
Fabio Aiub Sperotto
Mestrando em Modelagem Computacional
about.me/fabiosperotto
www.twitter.com/fabio_gk
Re: Licenses: using Jena with other project
Posted by Fabio Aiub Sperotto <fa...@gmail.com>.
Andy,
I forgot to mention that my library will use the binaries, the source code
of Jena is not available, but the project home page, a mention of Jena will
be written. My work is derived from Jena.
Very cool your understanding and for me it makes sense that "virus effect".
I think we need to get back to my planning, read very well the Apache
license and probably leave it under the Apache license.
2013/1/17 Andy Seaborne <an...@apache.org>
> On 17/01/13 19:37, Fabio Aiub Sperotto wrote:
>
>> Thanks Andy,
>>
>> In your link from Apache Software Foundation we can read:
>>
>> "Apache 2 software can therefore be included in GPLv3 projects, because
>> the
>> GPLv3 license accepts our software into GPLv3 works. However, GPLv3
>> software cannot be included in Apache projects. The licenses are
>> incompatible in one direction only, and it is a result of ASF's licensing
>> philosophy and the GPLv3 authors' interpretation of copyright law."
>>
>> I'm not lawyer too :-(
>>
>> But, is compatible in one direction, and this is my direction. Jena under
>> Apache, my .jar library in GPLv3. So I can use GPLv3 in my project,
>> someone
>> disagree?
>>
>
> That is my understanding; also includes if you use source code from Jena,
> not just the binaries.
>
> A combined work ("the product") of a project that has ASL and GPLv3
> components will have to ship as GPLv3 - the GPL "virus" effect. That some
> things it gathers together are ASL, BSD and some others does not matter.
> The source code of the project has to fit with GPLv3.
>
> ASF (legal entity, the non-profit foundation) only licenses its
> "products", e.g. jena, under ASL. The Jena project can't use, depend on, or
> reship GPL code, nor choose a different license (there is a small corner
> case of optional implementations of interfaces).
>
>
>
>> or
>>
>> Can I keep all under Apache license? But I don't know how this will be
>> affect the project in the future.
>>
>
> It will depend on what your project depends on. You can use the Apache
> License independent of Apache - there are instructions at the end of
>
> http://www.apache.org/**licenses/LICENSE-2.0#apply<http://www.apache.org/licenses/LICENSE-2.0#apply>
>
> For the future, I recommend keeping a detailed record of any code you
> accept from others in case you need to get back to them later. You are a
> long way ahead of many open source endeavours who do somewhat ignore legal
> issues. Yes, they are a bit of a cost/nuisance sometimes but that is the
> way the world is.
>
> <insert disclaimer="IANAL"/>
>
> Andy
>
>
--
Fabio Aiub Sperotto
Mestrando em Modelagem Computacional
about.me/fabiosperotto
www.twitter.com/fabio_gk
Re: Licenses: using Jena with other project
Posted by Andy Seaborne <an...@apache.org>.
On 17/01/13 19:37, Fabio Aiub Sperotto wrote:
> Thanks Andy,
>
> In your link from Apache Software Foundation we can read:
>
> "Apache 2 software can therefore be included in GPLv3 projects, because the
> GPLv3 license accepts our software into GPLv3 works. However, GPLv3
> software cannot be included in Apache projects. The licenses are
> incompatible in one direction only, and it is a result of ASF's licensing
> philosophy and the GPLv3 authors' interpretation of copyright law."
>
> I'm not lawyer too :-(
>
> But, is compatible in one direction, and this is my direction. Jena under
> Apache, my .jar library in GPLv3. So I can use GPLv3 in my project, someone
> disagree?
That is my understanding; also includes if you use source code from
Jena, not just the binaries.
A combined work ("the product") of a project that has ASL and GPLv3
components will have to ship as GPLv3 - the GPL "virus" effect. That
some things it gathers together are ASL, BSD and some others does not
matter. The source code of the project has to fit with GPLv3.
ASF (legal entity, the non-profit foundation) only licenses its
"products", e.g. jena, under ASL. The Jena project can't use, depend on,
or reship GPL code, nor choose a different license (there is a small
corner case of optional implementations of interfaces).
>
> or
>
> Can I keep all under Apache license? But I don't know how this will be
> affect the project in the future.
It will depend on what your project depends on. You can use the Apache
License independent of Apache - there are instructions at the end of
http://www.apache.org/licenses/LICENSE-2.0#apply
For the future, I recommend keeping a detailed record of any code you
accept from others in case you need to get back to them later. You are
a long way ahead of many open source endeavours who do somewhat ignore
legal issues. Yes, they are a bit of a cost/nuisance sometimes but that
is the way the world is.
<insert disclaimer="IANAL"/>
Andy
Re: Licenses: using Jena with other project
Posted by Fabio Aiub Sperotto <fa...@gmail.com>.
Thanks Andy,
In your link from Apache Software Foundation we can read:
"Apache 2 software can therefore be included in GPLv3 projects, because the
GPLv3 license accepts our software into GPLv3 works. However, GPLv3
software cannot be included in Apache projects. The licenses are
incompatible in one direction only, and it is a result of ASF's licensing
philosophy and the GPLv3 authors' interpretation of copyright law."
I'm not lawyer too :-(
But, is compatible in one direction, and this is my direction. Jena under
Apache, my .jar library in GPLv3. So I can use GPLv3 in my project, someone
disagree?
or
Can I keep all under Apache license? But I don't know how this will be
affect the project in the future.
2013/1/17 Andy Seaborne <an...@apache.org>
> On 17/01/13 15:51, Fabio Aiub Sperotto wrote:
>
>> Hello guys,
>>
>> I don't know where send this question. I´m using Jena like a base
>> framework
>> to my programming library (project is a master dissertation). My library
>> will be free software. But, can I spread my project under GNU-GPL license
>> and keeping de jena packages under Apache license?
>>
>> Will I have conflict licenses? If yes, how cai i spread my work using
>> Jena?
>> (I'm not modifying Jena, just using your several methods).
>>
>> (Soon all project will be uploaded in Github)
>>
>>
> Fabio,
>
> You are doing the right thing by thinking of this before you do a release.
> Legal matters are best done before releases, not after.
>
> The details are here:
>
> http://www.apache.org/**licenses/GPL-compatibility.**html<http://www.apache.org/licenses/GPL-compatibility.html>
>
> You can *use* Apache Jena with GPL in your system.
>
> You need to work out the implications of publishing/redistributing your
> code or binaries.
>
> I'll highlight from that link that
> """
> the Free Software Foundation (FSF) does not consider the Apache License to
> be compatible with GPL version 2, only GPLv3. The Apache Software
> Foundation believes that you should always try to obey the constraints
> expressed by the copyright holder when redistributing their work.
> """
>
> If you are using other projects that are GPLv2, not GPLv3, this is a
> roadblock.
>
> If you are choosing a GPL license and do not use any other GPLv2-only
> projects, you can choose GPLv3 (or AGPLv3).
>
> This is not legal advice and I am most definitely not a lawyer.
>
> Note also the LICENSE and NOTICE for licence and copyright of libraries
> that Jena uses.
>
> Andy
>
>
>
>
--
Fabio Aiub Sperotto
Mestrando em Modelagem Computacional
about.me/fabiosperotto
www.twitter.com/fabio_gk
Re: Licenses: using Jena with other project
Posted by Andy Seaborne <an...@apache.org>.
On 17/01/13 15:51, Fabio Aiub Sperotto wrote:
> Hello guys,
>
> I don't know where send this question. I´m using Jena like a base framework
> to my programming library (project is a master dissertation). My library
> will be free software. But, can I spread my project under GNU-GPL license
> and keeping de jena packages under Apache license?
>
> Will I have conflict licenses? If yes, how cai i spread my work using Jena?
> (I'm not modifying Jena, just using your several methods).
>
> (Soon all project will be uploaded in Github)
>
Fabio,
You are doing the right thing by thinking of this before you do a
release. Legal matters are best done before releases, not after.
The details are here:
http://www.apache.org/licenses/GPL-compatibility.html
You can *use* Apache Jena with GPL in your system.
You need to work out the implications of publishing/redistributing your
code or binaries.
I'll highlight from that link that
"""
the Free Software Foundation (FSF) does not consider the Apache License
to be compatible with GPL version 2, only GPLv3. The Apache Software
Foundation believes that you should always try to obey the constraints
expressed by the copyright holder when redistributing their work.
"""
If you are using other projects that are GPLv2, not GPLv3, this is a
roadblock.
If you are choosing a GPL license and do not use any other GPLv2-only
projects, you can choose GPLv3 (or AGPLv3).
This is not legal advice and I am most definitely not a lawyer.
Note also the LICENSE and NOTICE for licence and copyright of libraries
that Jena uses.
Andy