<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>Hi Alvin,<div><br></div><div>Thank you for considering my request and willingness to work with us on this. It is much appreciated.</div><div><br></div><div>I've reached out to the OpenToonz source owner to make sure this will work for us and will get back to you as soon as I hear from him.</div><div><br></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Alvin Wong <alvinhochun+krita@gmail.com> </div><div>Date: 7/13/18 12:05 PM (GMT-05:00) </div><div>To: Krita's developers and users mailing list <kimageshop@kde.org> </div><div>Cc: John Dancel <dancel@ptd.net>, Jeremy Bullock <jcbullock@gmail.com>, Calle Laakkonen <laakkonenc@gmail.com> </div><div>Subject: Considering to re-license the Windows Ink support code as BSD 2-Clause </div><div><br></div></div>Dear all,<br><br>I have been told by multiple people that OpenToonz developers would<br>like to make use of the Windows Pointer Input Message (Windows Ink on<br>Windows 8 or above) support code files<br>(libs/ui/input/wintab/kis_tablet_support_win8.h and<br>libs/ui/input/wintab/kis_tablet_support_win8.cpp) that I wrote for<br>Krita, but couldn't due to Krita being GPLv2+ and OpenToonz being<br>licensed in BSD 3-Clause, Currently Drawpile has already adopted these<br>code with no issues since Drawpile is GPLv3.<br><br>I would be fine with allowing OpenToonz to use the current version of<br>the code in BSD 3-Clause licence, but this would seem short-sighted<br>since future changes of the code in Krita wouldn't make it into<br>OpenToonz without further permissions, and it would get more<br>complicated if other developers make changes.<br><br>Therefore, I am considering to re-license these two files within the<br>Krita repo as BSD 2-Clause (BSD 3-Clause is not allowed according to<br>KDE policies), and request that in the future other developers who<br>make changes to these two files within Krita should agree to license<br>their changes as BSD 2-Clause. A problem with this approach is that if<br>Drawpile, OpenToonz or other derivatives make other functional changes<br>under a more restrictive licence (e.g. GPL or even BSD 3-Clause), they<br>can't be backported to Krita without explicit permission. It would<br>also mean that even closed-source software can use code from these two<br>files, though I don't have problems with this. Drawpile and others can<br>still continue to use the current or older versions of the files (and<br>derivatives of it) as GPLv2+, though it would get a bit complicated if<br>they wish to include any future changes.<br><br>The process should be as simple as me making a commit to change the<br>license comment blocks in these two files.<br><br>Are there any technical issues with this approach, or did I show any<br>misunderstanding in the previous paragraphs?<br><br>I would like to have this done in no more than a week, so if there are<br>any concerns please raise them as soon as possible.<br><br>Best Regards,<br>Alvin Wong<br><br>CC: OpenToonz develoeprs John Dancel and Jeremy Bullock and Drawpile<br>developer Calle Laakkonen<br></body></html>