< Guidelines and HOWTOs | RelicensingRevision as of 12:59, 17 November 2007 by Chani (talk | contribs) (→Current Reply List: gpl3 ftw)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 KDE GPL v2.0 Relicensing effort 1.1 Why does it matter ? 2 How can I help ? 2.1 Whats next? 3 Current Reply List 4 Current TODO List 5 Current list of problematic Files 6 Current top 30 of possible contributors to GPLv2-only files KDE GPL v2.0 Relicensing effort Why does it matter ? A couple of KDE dependent projects or even libraries have moved or are going to move to GPLv3 (State of GPLv3 movement). Unfortunately, GPL v3 is incompatible with GPL v2. This means that it is not possible to create a project linking GPL v2 and v3 code together. There is no problem for projects which are licensed GPLv2+ (version 2 or above). A few parts of KDE are currently licensed as GPLv2 only. So far we have no reason to believe that this was something other than an oversight. However, we still need to validate with the individual copyright holders that a relicense to GPLv2+ or GPLv2+v3 is okay with them. Therefore, in an effort we're trying to identify the contributors that have contributed under the terms of GPLv2 and where the "+" part was not explicetly mentioned. If we know that all contributors agreed to a relicense, we can go ahead and flip the license of the individual source file. How can I help ? By identifying a contributor who as contributed under the terms of GPLv2 (use kdesdk/scripts/relicensecheck.pl on the file in question or the Relicense Status Page), and contacting him if he wasn't already contacted. Ask him the following questions: Are you okay with relicensing your contributions done under GPLv2 to GPLv2+? Are you okay with relicensing your contributions done under GPLv2 to GPLv2 or GPLv3 ? Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2+? Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2 or LGPLv3? Are you okay with the KDE e.V. deciding on a future licensing change to your code, should that be necessary? Whats next? you checkout relicensecheck.pl from trunk/KDE/kdesdk/scripts you run it on the file or directory in question you interpret the result. check each commit that is being complained about carefully. Try to get the copyright's holder's permission. if you get it, update the whitelist in the script. review the list of declared copyright holders in the file. if you're all clear, change the license to the most liberal license possible. Document your change verbosely in the SVN commit log. Current Reply List Please keep the list sorted by family name! Please only use "YES" or "NO" Name GPLv2->GPLv2+ LGPLv2 -> LGPLv2+ GPLv2 -> GPLv2+v3 LGPLv2 -> LGPLv2+LGPLv3 KDE e.V. decides Adam, Till YES YES YES YES NO Armitage, Chani YES YES YES YES YES Bastian, Waldo NO NO YES YES YES Boemann, Casper YES YES YES YES YES Broadstone, Matt NO NO YES YES YES Cullmann, Christoph NO NO YES YES NO Drummond, Craig YES YES YES YES YES Dymo, Alexander YES YES YES YES NO Faure, David YES YES YES YES YES Granroth, Kurt YES YES YES YES YES Herden, Jens YES YES YES YES YES Hoeglund, Fredrik NO NO YES YES Kainhofer, Reinhold YES YES YES YES YES Kellet, Alexander YES YES YES YES YES Knight, Robert YES YES YES YES YES Kretz, Matthias NO NO YES YES NO Kulow, Stephan YES YES YES YES NO Lunak, Lubos YES YES YES YES NO Mac-Vicar, Duncan YES YES YES YES NO Macieira, Thiago YES YES YES YES YES Mantia, Andras NO NO YES YES YES Martyn, Greg YES YES YES YES YES Molkentin, Daniel YES YES YES YES NO Montel, Laurent YES YES YES YES YES Moore, Richard NO NO YES YES YES Mueller, Dirk YES YES YES YES NO Mutz, Marc YES YES NO NO NO Raabe, Frerich NO NO YES YES NO Riddell, Jonathan YES YES YES YES YES Sand, Espen YES YES YES Schlaeger, Chris NO NO YES YES NO Schumacher, Cornelius YES YES YES YES YES Seigo, Aaron YES YES YES YES YES Stephenson, Will YES YES YES YES YES Tapsell, John YES YES YES YES YES Trueg, Sebastian (Exception: K3b) YES YES YES YES YES Wolfer, Urs YES YES YES YES YES Current TODO List KDAB Tobias Koenig Matthew Woehlke Daniel Teske Dawit Alemayehu Alex Zepeda Thomas Leitner Lars Knoll Kevin Ottens Simon Hausmann Maksim Orlovich Sirtaj Singh Kang Karol Szwed Thorsten Roeder Joseph Wenninger Current list of problematic Files Tom Albers has written a webfrontend to relicensecheck.pl, which makes it really easy to find files that can already be relicensed, or for those that can not it is possible to easily see (via tooltip) which commits are preventing it. Visit the Relicensing Status Page Current top 30 of possible contributors to GPLv2-only files 59212 ingwa 38032 bulygin 32243 dfaure 23647 sequitur 19747 amantia 18148 mutz 17365 rdale 17149 trueg 15012 tokoe 14218 lunakl 11806 winterz 10603 coolo 10449 mbuesch 10094 thorsen 9339 arnorehn 7424 rogowski 7382 cies 6177 gyurco 6130 mlaurent 5612 cramblitt 5531 mrudolf 5028 tilladam 4605 kloecker 4390 mkretz 4327 waba 4216 cschlaeg 4159 burghard 4152 johnflux 3327 fredrik 3154 gungl Retrieved from "https://community.kde.org/index.php?title=Guidelines_and_HOWTOs/Relicensing/KDE_Relicensing&oldid=84747" Content is available under Creative Commons License SA 4.0 unless otherwise noted.