On Tue, Jan 4, 2011 at 10:19 PM, Ryan C. Gordon <iccu...@icculus.org> wrote: > >> If Turtle Arena contains both GPLv2+ modules (from ioquake3) and GPLv3 >> modules >> (from WolfET) > > I'm late to this discussion, but I wanted to throw in an important note: > > Enemy Territory, as far as I can tell, isn't compatible with the GPL3. > > http://icculus.org/~icculus/dotplan/ET-COPYING.txt > > You can't say "this is GPL3 licensed, oh, but delete this section and use > this text instead." I mean, you _can_, but then you can't intermingle it > with other GPL code. Basically, it's not the GPL3 license anymore once you > make modifications to it...and all versions of the GPL explicit require that > you not add new restrictions to the license. > > This is almost certainly fallout from id Software's sale to Zenimax. > Apparently the new set of lawyers don't "get it" like the old ones did. > > You can still use, modify, and distribute ET source code, and by-and-large, > use it like GPL3 source code. But it's not the GPL3. ioquake3 should not > commit any patches based on ET source code. I'm sorry, that sucks, but > that's how they (probably unintentionally) set it up in the ET source > release. > > tl;dr: you can't intermingle the open source releases of ET and Quake3 at > all. > > I am not a lawyer, this is not legal advice,
It may not be true but I wouldn't be surprised. GPL seems especially designed to be selected for id software's profitability. If it was BSD, they wouldn't be able to sell their closed id tech 3 (they just sold one to Urban Terror). Making more problems with GPL3 might be in the same venue. However, I do realize a developer only donating work may find it offensive seeing his work being reused indiscriminately and almost secretly (BSD) so there's also the Stallman way to look at it. _______________________________________________ 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.
