[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-26 1:43:08
Message-ID: CAGLHt72DLMh16r5q+BQ2vfTJf3te=jmknJn4W5z1rMamLArWJA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Just to be sure, this is the content I should include in the new COPYING
file
of Tupi: http://www.gnu.org/licenses/gpl-2.0.html
Right?
2013/6/25 Boudewijn Rempt <boud@valdyas.org>
> Looks pretty good -- nothing should prevent GPLv2+ then! And that would be
> very awesome :-)
>
>
> On Tuesday 25 June 2013 Jun 12:35:48 Gustav González wrote:
>
> > >
> > > With a quick glance at the KTooN codebase, I made the following
> > > observation:
> > >
> > >
> > >
> > > The KTooN commits from 2010-05-15 11:48 and 11:49 with message
> "Updating
> > > license version from source code -> GPL 3" changed the license from
> "GPL v2
> > > or any later version" to "GPL v3 or any later version".
> > >
> > >
> > >
> > > (Please correct me if I am wrong, the commits change about 1000 lines
> and
> > > I did not check every change!)
> > >
> > >
> > >
> > > From my POV you have two options. Both include first asking _every_
> > > commiter following up the license change commits in a documented way if
> > > they allow changing the license to "GPL v2 or any later version".
> After you
> > > received their approvals you can:
> > >
> > >
> > >
> > > Either
> > >
> > > * revert the two license change commits
> > >
> > > * do a rebase of all following commits
> > >
> > > * change newly introduced licenses
> > >
> > >
> > >
> > > Or
> > >
> > > * revert the license change commits and perform relicensing at once.
> > >
> > >
> > >
> > > I see no need to contact Monica about that issue, since all approvals
> that
> > > are necessary for doing the relicensing are from individual commiters
> (who
> > > commited after the relicense in 2010, as far as I understood).
> > >
> > >
> > >
> > > Greetings,
> > >
> > > Andreas
> > >
> >
> > Hello there,
> >
> > It seems you are right, yesterday I was talking to a friend who has a
> wide
> > knowledge of the GPL licenses and he told me
> > the same. I just need the approval from all the developers who made
> > contributions between the moment I changed the license
> > of Tupi from GPL v2 to v3 and the present.
> >
> > If you take a look at the old KTooN repository, you will find out that
> the
> > only user who made commits to the project from 2010,
> > even before the change of license, was me (xtingray):
> >
> > http://svn.berlios.de/viewvc/ktoon/
> >
> > About the repository of Tupi, you will be able to confirm that only
> > Cristian Cepeda (he helped me to fix some .pro files
> > to make possible the compilation of Tupi in OSX) and me were working on
> the
> > code:
> >
> > https://github.com/xtingray/tupi/commits/master?page=20
> >
> > About Cristian, I already contacted him and this was his answer:
> >
> > ---------- Forwarded message ----------
> > From: Cristian David Cepeda Piscal <cristiandavid.cepeda@gmail.com>
> > Date: 2013/6/25
> > Subject: Re: Question about Tupi license
> > To: Gustav González <xtingray@gmail.com>
> >
> > Hello Gustavo,
> >
> > About the Tupi relicensing.
> >
> > I absolutely agree with the change of license, even more when it will
> help
> > to spread the word about your project and to make it part of something so
> > great as the KDE project. I have no objections. Do it!
> >
> >
> --
> Boudewijn Rempt
> http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl
>
> _______________________________________________
> 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.
>
--
============================
Gustav Gonzalez
xtingray@gmail.com
============================
[Attachment #5 (text/html)]
Just to be sure, this is the content I should include in the new COPYING file<br>of \
Tupi: <a href="http://www.gnu.org/licenses/gpl-2.0.html">http://www.gnu.org/licenses/gpl-2.0.html</a><br><br>Right?<br><br><br><br><div \
class="gmail_quote"> 2013/6/25 Boudewijn Rempt <span dir="ltr"><<a \
href="mailto:boud@valdyas.org" \
target="_blank">boud@valdyas.org</a>></span><br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Looks pretty \
good -- nothing should prevent GPLv2+ then! And that would be very awesome :-)<br> \
<div class="HOEnZb"><div class="h5"><br> <br>
On Tuesday 25 June 2013 Jun 12:35:48 Gustav González wrote:<br>
<br>
> ><br>
> > With a quick glance at the KTooN codebase, I made the following<br>
> > observation:<br>
> ><br>
> ><br>
> ><br>
> > The KTooN commits from 2010-05-15 11:48 and 11:49 with message \
"Updating<br> > > license version from source code -> GPL 3" \
changed the license from "GPL v2<br> > > or any later version" to \
"GPL v3 or any later version".<br> > ><br>
> ><br>
> ><br>
> > (Please correct me if I am wrong, the commits change about 1000 lines \
and<br> > > I did not check every change!)<br>
> ><br>
> ><br>
> ><br>
> > From my POV you have two options. Both include first asking _every_<br>
> > commiter following up the license change commits in a documented way if<br>
> > they allow changing the license to "GPL v2 or any later version". \
After you<br> > > received their approvals you can:<br>
> ><br>
> ><br>
> ><br>
> > Either<br>
> ><br>
> > * revert the two license change commits<br>
> ><br>
> > * do a rebase of all following commits<br>
> ><br>
> > * change newly introduced licenses<br>
> ><br>
> ><br>
> ><br>
> > Or<br>
> ><br>
> > * revert the license change commits and perform relicensing at once.<br>
> ><br>
> ><br>
> ><br>
> > I see no need to contact Monica about that issue, since all approvals \
that<br> > > are necessary for doing the relicensing are from individual \
commiters (who<br> > > commited after the relicense in 2010, as far as I \
understood).<br> > ><br>
> ><br>
> ><br>
> > Greetings,<br>
> ><br>
> > Andreas<br>
> ><br>
><br>
> Hello there,<br>
><br>
> It seems you are right, yesterday I was talking to a friend who has a wide<br>
> knowledge of the GPL licenses and he told me<br>
> the same. I just need the approval from all the developers who made<br>
> contributions between the moment I changed the license<br>
> of Tupi from GPL v2 to v3 and the present.<br>
><br>
> If you take a look at the old KTooN repository, you will find out that the<br>
> only user who made commits to the project from 2010,<br>
> even before the change of license, was me (xtingray):<br>
><br>
> <a href="http://svn.berlios.de/viewvc/ktoon/" \
target="_blank">http://svn.berlios.de/viewvc/ktoon/</a><br> ><br>
> About the repository of Tupi, you will be able to confirm that only<br>
> Cristian Cepeda (he helped me to fix some .pro files<br>
> to make possible the compilation of Tupi in OSX) and me were working on the<br>
> code:<br>
><br>
> <a href="https://github.com/xtingray/tupi/commits/master?page=20" \
target="_blank">https://github.com/xtingray/tupi/commits/master?page=20</a><br> \
><br> > About Cristian, I already contacted him and this was his answer:<br>
><br>
> ---------- Forwarded message ----------<br>
> From: Cristian David Cepeda Piscal <<a \
href="mailto:cristiandavid.cepeda@gmail.com">cristiandavid.cepeda@gmail.com</a>><br>
> Date: 2013/6/25<br>
> Subject: Re: Question about Tupi license<br>
> To: Gustav González <<a \
href="mailto:xtingray@gmail.com">xtingray@gmail.com</a>><br> ><br>
> Hello Gustavo,<br>
><br>
> About the Tupi relicensing.<br>
><br>
> I absolutely agree with the change of license, even more when it will help<br>
> to spread the word about your project and to make it part of something so<br>
> great as the KDE project. I have no objections. Do it!<br>
><br>
><br>
--<br>
</div></div><div class="im HOEnZb">Boudewijn Rempt<br>
<a href="http://www.valdyas.org" target="_blank">http://www.valdyas.org</a>, <a \
href="http://www.krita.org" target="_blank">http://www.krita.org</a>, <a \
href="http://www.boudewijnrempt.nl" \
target="_blank">http://www.boudewijnrempt.nl</a><br>
<br>
</div><div class="HOEnZb"><div \
class="h5">_______________________________________________<br> kde-community mailing \
list<br> <a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-community" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br> <br>
Please remember our Code of Conduct and assume good intentions from your fellow \
community members.</div></div></blockquote></div><br><br clear="all"><br>-- \
<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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic