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

List:       kde-kimageshop
Subject:    Re: Relicensing Krita as LGPLv2+
From:       Alvin Wong <alvinhochun+krita () gmail ! com>
Date:       2017-01-05 12:28:39
Message-ID: CAE_6Y7Eggp2TkHMHQLOZE=dmFoWW=7cE07K=Oo0ovEQLKGLoEw () mail ! gmail ! com
[Download RAW message or body]

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
[prev in list] [next in list] [prev in thread] [next in thread]