[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-23 11:45:47
Message-ID: CAGLHt731SAw3btvNW0u_BkD2KN7PTV7qba52WQ2T=3CfScLzvQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2013/6/23 Andreas Cord-Landwehr <cordlandwehr@kde.org>

> **
> One maybe problematic point I noted is the license: In KDE we require all
> source code to be GPL v2 compatible [1], meaning GPL v3 does not comply
> with the license policy. Hence, would relicensing the code to be GPL v2
> compatibly (e.g. to license "GPL v2 or GPL v3 or any later") be an option?
>

    Ironies of life: when I changed the license of Tupi from GPLv2 to
GPLv3, I did it looking for "more freedom" or something
    like that. I have no idea about laws but as far as I understood, the
version 3 ensures that the code will be always available
    for the people "more than" the version 2, at least for some specific
cases. Anyway, it doesn't matter any more.

    Question: How should I make this license change without getting in a
legal issue? I mean: it can be done without any kind
    of trouble? I'll appreciate your guide on this. I have no problem
changing the license again.

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

[Attachment #5 (text/html)]

<div class="gmail_quote">2013/6/23 Andreas Cord-Landwehr <span dir="ltr">&lt;<a \
href="mailto:cordlandwehr@kde.org" \
target="_blank">cordlandwehr@kde.org</a>&gt;</span><br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <u></u>
<div style="font-family:&#39;DejaVu Sans \
Mono&#39;;font-size:9pt;font-weight:400;font-style:normal">One maybe problematic \
point I noted is the license: In KDE we require all source code to be GPL v2 \
compatible [1], meaning GPL v3 does not comply with the license policy. Hence, would \
relicensing the code to be GPL v2 compatibly (e.g. to license &quot;GPL v2 or GPL v3 \
or any later&quot;) be an option?<br> </div></blockquote><div><br>    Ironies of \
life: when I changed the license of Tupi from GPLv2 to GPLv3, I did it looking for \
&quot;more freedom&quot; or something<br>    like that. I have no idea about laws but \
as far as I understood, the version 3 ensures that the code will be always \
available<br>  for the people &quot;more than&quot; the version 2, at least for some \
specific cases. Anyway, it doesn&#39;t matter any more.<br><br>    Question: How \
should I make this license change without getting in a legal issue? I mean: it can be \
done without any kind<br>  of trouble? I&#39;ll appreciate your guide on this. I have \
no problem changing the license again.   <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]