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

List:       kde-community
Subject:    Re: [kde-community] Tupi: Open 2D Magic
From:       Gustav_González <xtingray () gmail ! com>
Date:       2013-06-24 15:02:07
Message-ID: CAGLHt71K7WQjFm977-Et+-9WOQvR7U6M4MUGLcJZ5kxr25-svw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2013/6/24 Boudewijn Rempt <boud@valdyas.org>

> No, the license is everybodies concern. If you want to share code from
> tupi with, for instance, Krita, the license has to be (L)GPLv2+, or
> compatible. Your license is your interface to the rest of the floss
> community.
>
> But in fact, if you didn't have a clear (written, email is ok) OK from all
> previous developers as well as Monica (if they are copyright holders of
> code currently in Tupi) to relicense to GPLv3, then you're already in deep
> problems with your codebase.
>

  As far as I understood, the agreement between Toonka (in that time, the
Monica's company) and the developers was
  that the whole rights of the project would belong to Toonka, even when
the chosen license was GPL.
  KTooN wasn't a "normal" free software project. It wasn't about a
community sharing and creating code, it was about a
  company working on a free source code application.

  Note: when I did the change of license from v2 to v3, I did it with the
support/knowledge of Monica.

  I understand if I have to talk to Monica to deal with this issue, but
legally, should I talk to the old developers?

-- 
============================
  Gustav Gonzalez
  xtingray@gmail.com
============================

[Attachment #5 (text/html)]

<div class="gmail_quote">2013/6/24 Boudewijn Rempt <span dir="ltr">&lt;<a \
href="mailto:boud@valdyas.org" \
target="_blank">boud@valdyas.org</a>&gt;</span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

No, the license is everybodies concern. If you want to share code from tupi with, for \
instance, Krita, the license has to be (L)GPLv2+, or compatible. Your license is your \
interface to the rest of the floss community.<br>


<br>
But in fact, if you didn&#39;t have a clear (written, email is ok) OK from all \
previous developers as well as Monica (if they are copyright holders of<br> code \
currently in Tupi) to relicense to GPLv3, then you&#39;re already in deep<br> \
problems with your codebase.<br></blockquote><div><br>  As far as I understood, the \
agreement between Toonka (in that time, the Monica&#39;s company) and the developers \
was<br>  that the whole rights of the project would belong to Toonka, even when the \
chosen license was GPL.<br>

  KTooN wasn&#39;t a &quot;normal&quot; free software project. It wasn&#39;t about a \
community sharing and creating code, it was about a <br>  company working on a free \
source code application.<br><br>  Note: when I did the change of license from v2 to \
v3, I did it with the support/knowledge of Monica.<br>

<br>  I understand if I have to talk to Monica to deal with this issue, but legally, \
should I talk to the old developers?<br><br></div></div>-- \
<br>============================<br>  Gustav Gonzalez<br>  <a \
href="mailto:xtingray@gmail.com" target="_blank">xtingray@gmail.com</a><br>

============================



_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community

Please remember our Code of Conduct and assume good intentions from your fellow community members.

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