This is a multi-part message in MIME format. --===============6562175490640228159== Content-Type: multipart/alternative; boundary="nextPart8802714.oFuxXZDT6S" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart8802714.oFuxXZDT6S Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" On Monday 24 June 2013 11:08:34 Gustav Gonz=E1lez wrote: > 2013/6/24 Paul Gideon Dann >=20 > > This is a question of who owns the copyright, which depends on the > > employment contract that Toonka had with its employees. If you wan= t=20 to > > switch back to GPLv2 in order to join KDE, though, I don't think yo= u=20 need > > to do anything, since the code was GPLv2 before anyway, right? With a quick glance at the KTooN codebase, I made the following=20 observation: The KTooN commits from 2010-05-15 11:48 and 11:49 with message=20 "Updating license version from source code -> GPL 3" changed the licens= e=20 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=20= and I did not check every change!) From my POV you have two options. Both include first asking _every_=20 commiter following up the license change commits in a documented way if= =20 they allow changing the license to "GPL v2 or any later version". After= you=20 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 t= hat=20 are necessary for doing the relicensing are from individual commiters (= who=20 commited after the relicense in 2010, as far as I understood). Greetings, Andreas --nextPart8802714.oFuxXZDT6S Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

On = Monday 24 June 2013 11:08:34 Gustav Gonz=E1lez wrote:

>= ; 2013/6/24 Paul Gideon Dann <pdgiddie@gmail.com>

>= ;

>= ; > This is a question of who owns the copyright, which depends on t= he

>= ; > employment contract that Toonka had with its employees. If you = want to

>= ; > switch back to GPLv2 in order to join KDE, though, I don't think= you need

>= ; > to do anything, since the code was GPLv2 before anyway, right?

Wit= h a quick glance at the KTooN codebase, I made the following observatio= n:

The= KTooN commits from 2010-05-15 11:48 and 11:49 with message "Up= dating license version from source code -> GPL 3" changed the l= icense 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 a= nd I did not check every change!)

= From my POV you have two options. Both include first asking _every_ com= miter following up the license change commits in a documented way if th= ey 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 t= hat are necessary for doing the relicensing are from individual commite= rs (who commited after the relicense in 2010, as far as I understood).<= /span>

= Greetings,

= Andreas

--nextPart8802714.oFuxXZDT6S-- --===============6562175490640228159== 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. --===============6562175490640228159==--