• Join Us |
  • |
  • Sign in with:

Carmack on GPL

by Clay Mitchell, Feb 23, 2000 5:09pm PST
Related Topics – Quake

Update - Clay: Here's the whole dealie, since i know you can't get to the QuakeLives site right now. This is what's happening: The QuakeLives guy has stated this:

To download binaries or proceed into this site, you have to give up your rights under the GPL. Specifically the rights regarding access to the source code. And while we are obligated to offer you the source code, for up to 3 years until we stop releasing this. To gain access to this site, you are obligated not to ask.
So the guy wants to protect his source code? Big deal right? Wrong! Carmack released the source under the GPL. What's that? The GNU Public License. And here's a snippet of it:
"6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. YOU MAY NOT IMPOSE ANY FURTHER RESTRICTIONS ON THE RECIPIENTS' EXERCISE OF THE RIGHTS GRANTED HEREIN."
Anyhow, whats this mean? All these free software jokers who do stuff with Linux are up a creek if this kind of mess can happen. Any Tom, Dick or Harry, can take their software, close it and sell it! Anyway here's Carmack's whole "don't mess with me foo" .plan update.
This is a public statement that is also being sent directly to Slade at QuakeLives regarding http://www.quakelives.com/main/ql.cgi?section=dlagreement&file=qwcl-win32/ I see both sides of this. Your goals are positive, and I understand the issues and the difficulties that your project has to work under because of the GPL. I have also seen some GPL zealots acting petty and immature towards you very early on (while it is within everyone's rights to DEMAND code under the GPL, it isn't necessarily the best attitude to take), which probably colors some of your views on the subject. We discussed several possible legal solutions to the issues. This isn't one of them. While I doubt your "give up your rights" click through would hold up in court, I am positive that you are required to give the source to anyone that asks for it that got a binary from someone else. This doesn't provide the obscurity needed for a gaming level of security. I cut you a lot of slack because I honestly thought you intended to properly follow through with the requirements of the GPL, and you were just trying to get something fun out ASAP. It looks like I was wrong. If you can't stand to work under the GPL, you should release the code to your last binary and give up your project. I would prefer that you continue your work, but abide by the GPL. If necessary, I will pay whatever lawyer the Free Software Foundation reccomends to pursue this.





Comments

180 Threads | 181 Comments


  • #159, I don\'t think that would work.

    If I modify a unix GPL program to work under windows and reference one of the window DLLs in the resulting code, Microsoft is under NO requirement to release the source to THEIR DLL.

    The same would be true, if I created a DLL that contained an engine for AI programming that I copyrighted and granted redistribution license to anyone who purchases the development IDE tools. If someone decides to use my AI DLL as part of a Quake project, the GPL does not force me to release my source to the AI engine.




  • #159 If your library is a seperate entity entirely its not a derivitive :) If I write an API of my OWN, then later on I write support into Quake for it, how can it be a derivitive?

    It could be for any game, and Quake simply SUPPORTS it.

    There is nothing to stop you writing a secure networking API of you own violition. If you then modify the Quake source to support it, you don\'t have to release your own SEPERATE work, which is distributed under a seperate liscense, in a seperate download. After all GPL only applies to a work and its derivitives.



  • 166, you STILL have no idea what Open Source is. And open source project DOES have an owner, and the GPL is jsut one type of open source liscence. id is the owner, end of story. They LISCENCE the code out under the GPL- essentially that\'s the terms of \"sale\"- ANYONE who agrees to the stipulations can modify the source and do anything with it as long as they post the source. It keeps them clean and legal.

    But id STILL owns the code. If Slade wanted to, he could negotiate a different liscence with id that WOULDN\'T require him to post the code. That\'s perfectly legit- and plenty of software companies like Raven hav similar agreements on the Quake source that don\'t require them to post source. But you HAVE to get that relisence from id, you can\'t just make it up yourself like Slade has done.
























  • The simple solution is to write a generic library for protected network games. Say a DLL. Release it under its own liscense. Then release your quake code WITH dll support. I know this works under the LGPL (I think it should work with the GPL), and as a seperate entity, Carmack can do nothing. All Slade would have to do is release code with modified support which loads the library.

    Limits being - Dll stuff can be OS specific - Needs porting/portability support and the ability to modify the Quake Code in such a way the secret needed stuff is outside of the code.