On Thu, Dec 30, 2010 at 05:40:08PM -0600, eviljoel wrote: > Hello Zack, > > I think your only option is to convert the ioquake3 code to GPLv3. Of > course, if you own the copyright to the GPLv3 code in question you can > always dual license it as GPLv2, but it sounds like Id owns the > copyright in this case. > > Yeah, rewriting the code from scratch or using someone else's GPLv2 > code is also a valid option. > > I personally like the GPLv3. I really wish we would all just move to that.
You have all the pieces here, but you haven't put them together: 1) ID owns the copyright on their code. 2) The copyright owner [ID] has specifically chosen a license under which the code is to be distributed: GPLv2+ 3) You don't get to change the license to "GPLv3" when the copyright owner has specifically chosen the license "GPLv2+". By saying GPLv2+, ID have allowed you the perogative of distributing the code under terms in GPLv3, but you aren't allowed to actually change the license under which the copyright owner has put the code. Specifically, there is no "convert the ioquake3 code to GPLv3" option afforded to zakk in this scenario. The FAQ about the GPL includes this guy: "Is GPLv3 compatible with GPLv2?" http://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility along with "What does it mean to say that two licenses are 'comaptible'?" http://www.gnu.org/licenses/gpl-faq.html#WhatIsCompatible Gary (-; _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
