--===============4535622980839397771== Content-Type: multipart/alternative; boundary=047d7b10c83793401104e004c4dc --047d7b10c83793401104e004c4dc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 > Looks pretty good -- nothing should prevent GPLv2+ then! And that would b= e > very awesome :-) > > > On Tuesday 25 June 2013 Jun 12:35:48 Gustav Gonz=E1lez 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=3D20 > > > > About Cristian, I already contacted him and this was his answer: > > > > ---------- Forwarded message ---------- > > From: Cristian David Cepeda Piscal > > Date: 2013/6/25 > > Subject: Re: Question about Tupi license > > To: Gustav Gonz=E1lez > > > > 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.n= l > > _______________________________________________ > 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. > --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Gustav Gonzalez xtingray@gmail.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --047d7b10c83793401104e004c4dc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Just to be sure, this is the content I should include in the new COPYING fi= le
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=E1lez 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 &q= uot;Updating
> > license version from source code -> GPL 3" changed the li= cense from "GPL v2
> > or any later version" to "GPL v3 or any later version&q= uot;.
> >
> >
> >
> > (Please correct me if I am wrong, the commits change about 1000 l= ines and
> > I did not check every change!)
> >
> >
> >
> > From my POV you have two options. Both include first asking _ever= y_
> > commiter following up the license change commits in a documented = way if
> > they allow changing the license to "GPL v2 or any later vers= ion". 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 on= ce.
> >
> >
> >
> > I see no need to contact Monica about that issue, since all appro= vals that
> > are necessary for doing the relicensing are from individual commi= ters (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 o= n the
> code:
>
> https://github.com/xtingray/tupi/commits/master?page=3D20=
>
> 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=E1lez <xtingr= ay@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.o= rg, http://w= ww.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 fe= llow community members.



--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
=A0 Gustav Gonzalez
=A0 xtingray@gmail.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D --047d7b10c83793401104e004c4dc-- --===============4535622980839397771== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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. --===============4535622980839397771==--