[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: [kde-community] Licensing question with header-only libraries
From: Jaroslaw Staniek <staniek () kde ! org>
Date: 2016-01-24 8:57:43
Message-ID: CAOj7QQ2o9L37P-rhf0KvkJqWicRztFoSobWNxJ9AqNEwVaDr1Q () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 24 January 2016 at 09:37, Ivan Čukić <ivan.cukic@kde.org> wrote:
> Hi all,
>
> I'm preparing a library that will probably end up being a header-only
> library.
> I would like to use a license like LGPL - the code in question needs
> to stay free, but that it can be used from non-free code like it is
> the case with other frameworks.
>
> The issue is that (if I'm correct) LGPL does not have anything
> different to GPL in this case since this is not a library that is
> dynamically linked - if someone uses it, its code becomes a part of
> the end product.
>
> If the above is correct, I think we should add a GPL+exception to the
> list of approved licences.
>
Hi Ivan
I'd go with LGPL+exception. It's effectively the same as GPL+exception
in this context but shows the intent of providing a library. If someone
ever transforms the code to a regular library + headers, no change will be
needed: LGPL will work for linkable code, and LGPL+exception for the
embeddable headers.
Cheers.
>
>
> --
> KDE, ivan.cukic@kde.org, http://cukic.co/
> gpg key id: 850B6F76
> _______________________________________________
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
--
regards, Jaroslaw Staniek
KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_default" \
style="font-family:monospace,monospace;font-size:small"><br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On 24 January 2016 at 09:37, Ivan \
Čukić <span dir="ltr"><<a href="mailto:ivan.cukic@kde.org" \
target="_blank">ivan.cukic@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi all,<br> <br>
I'm preparing a library that will probably end up being a header-only \
library.<br> I would like to use a license like LGPL - the code in question needs<br>
to stay free, but that it can be used from non-free code like it is<br>
the case with other frameworks.<br>
<br>
The issue is that (if I'm correct) LGPL does not have anything<br>
different to GPL in this case since this is not a library that is<br>
dynamically linked - if someone uses it, its code becomes a part of<br>
the end product.<br>
<br>
If the above is correct, I think we should add a GPL+exception to the<br>
list of approved licences.<br></blockquote><div><br><div class="gmail_default" \
style="font-family:monospace,monospace;font-size:small">Hi Ivan<br>I'd go with \
LGPL+exception. It's effectively the same as GPL+exception in this context \
but shows the intent of providing a library. If someone ever transforms the code to a \
regular library + headers, no change will be needed: LGPL will work for linkable \
code, and LGPL+exception for the embeddable headers.<br></div><br><div \
class="gmail_default" \
style="font-family:monospace,monospace;font-size:small">Cheers.<br></div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
<br>
<br>
--<br>
KDE, <a href="mailto:ivan.cukic@kde.org">ivan.cukic@kde.org</a>, <a \
href="http://cukic.co/" rel="noreferrer" target="_blank">http://cukic.co/</a><br> gpg \
key id: 850B6F76<br> _______________________________________________<br>
kde-community mailing list<br>
<a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-community" rel="noreferrer" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a></blockquote></div><br><br \
clear="all"><br>-- <br><div class="gmail_signature">regards, Jaroslaw \
Staniek<br><br>KDE:<br>: A world-wide network of software engineers, artists, \
writers, translators<br>: and facilitators committed to Free Software development - \
<a href="http://kde.org" target="_blank">http://kde.org</a><br>Calligra Suite:<br>: A \
graphic art and office suite - <a href="http://calligra.org" \
target="_blank">http://calligra.org</a><br>Kexi:<br>: A visual database apps builder \
- <a href="http://calligra.org/kexi" \
target="_blank">http://calligra.org/kexi</a><br>Qt Certified Specialist:<br>: <a \
href="http://www.linkedin.com/in/jstaniek" \
target="_blank">http://www.linkedin.com/in/jstaniek</a></div> </div></div>
[Attachment #6 (text/plain)]
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic