[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Relicensing Krita as LGPLv2+
From:       Wolthera <griffinvalley () gmail ! com>
Date:       2017-01-05 17:51:38
Message-ID: CAN80MtF5DbMdtudifK49G3cKaRG9R2DTk5CqtC=46JZdK8gsoA () mail ! gmail ! com
[Download RAW message or body]

LGPL's big thing is the linking stuff, right?


Yeah, this is fine by me.

On Thu, Jan 5, 2017 at 1:28 PM, Alvin Wong <alvinhochun+krita@gmail.com>
wrote:

> Hi Boud,
>
> I'm fine with relicensing my few lines of contributions to LGPL.
>
> Regards,
> Alvin
>
> P.S. Please note that my commit email address doesn't have `+krita` in
> it in case if you're checking the commit log.
>
> 2017-01-05 17:13 GMT+08:00 Boudewijn Rempt <boud@valdyas.org>:
> > Hi,
> >
> > Umpteenth draft of this mail, but I think we should consider relicensing
> > the GPL code in Krita to LGPL.
> >
> > One reason is that now that Krita is on its own, the mix of LGPL library
> > code inherited from koffice/calligra and GPL library code inherited from
> > Krita makes it hard to move code around; like we just did in the svg
> > branch, creating the kritacommand library from code from krita/image
> > and libs/kundo2. That code needs to be relicensed to LGPL before we
> > merge the branch, of course.
> >
> > Another reason is that there are too many macOS users who get confused
> > when they install an application that's not in the app store, and we
> > cannot publish GPL software in the app store. I wish I could just shrug
> > that off, and I've done that until 3.1, but it's getting quite a
> > support burden.
> >
> > I haven't found a script yet that will figure out who owns copyright
> > on the original GPL'ed krita code only -- running things like git fame
> > only works on the whole repo, most of which is LGPL already...
> >
> > --
> > Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>



-- 
Wolthera

[Attachment #3 (text/html)]

<div dir="ltr"><div>LGPL&#39;s big thing is the linking stuff, \
right?<br><br><br></div>Yeah, this is fine by me.<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 5, 2017 at 1:28 PM, \
Alvin Wong <span dir="ltr">&lt;<a href="mailto:alvinhochun+krita@gmail.com" \
target="_blank">alvinhochun+krita@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi Boud,<br> <br>
I&#39;m fine with relicensing my few lines of contributions to LGPL.<br>
<br>
Regards,<br>
Alvin<br>
<br>
P.S. Please note that my commit email address doesn&#39;t have `+krita` in<br>
it in case if you&#39;re checking the commit log.<br>
<div class="HOEnZb"><div class="h5"><br>
2017-01-05 17:13 GMT+08:00 Boudewijn Rempt &lt;<a \
href="mailto:boud@valdyas.org">boud@valdyas.org</a>&gt;:<br> &gt; Hi,<br>
&gt;<br>
&gt; Umpteenth draft of this mail, but I think we should consider relicensing<br>
&gt; the GPL code in Krita to LGPL.<br>
&gt;<br>
&gt; One reason is that now that Krita is on its own, the mix of LGPL library<br>
&gt; code inherited from koffice/calligra and GPL library code inherited from<br>
&gt; Krita makes it hard to move code around; like we just did in the svg<br>
&gt; branch, creating the kritacommand library from code from krita/image<br>
&gt; and libs/kundo2. That code needs to be relicensed to LGPL before we<br>
&gt; merge the branch, of course.<br>
&gt;<br>
&gt; Another reason is that there are too many macOS users who get confused<br>
&gt; when they install an application that&#39;s not in the app store, and we<br>
&gt; cannot publish GPL software in the app store. I wish I could just shrug<br>
&gt; that off, and I&#39;ve done that until 3.1, but it&#39;s getting quite a<br>
&gt; support burden.<br>
&gt;<br>
&gt; I haven&#39;t found a script yet that will figure out who owns copyright<br>
&gt; on the original GPL&#39;ed krita code only -- running things like git fame<br>
&gt; only works on the whole repo, most of which is LGPL already...<br>
&gt;<br>
&gt; --<br>
&gt; Boudewijn Rempt | <a href="http://www.krita.org" rel="noreferrer" \
target="_blank">http://www.krita.org</a>, <a href="http://www.valdyas.org" \
rel="noreferrer" target="_blank">http://www.valdyas.org</a><br> \
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div \
class="gmail_signature" data-smartmail="gmail_signature">Wolthera</div> </div>



[prev in list] [next in list] [prev in thread] [next in thread]