Spring RTS Engine

After this latest debacle, it appears there is much confusion about how the GPL works, what people have to do to be compliant with it, and why people like me are releasing their work under the GPL in the first place.

I am not a lawyer. The following answers are not, in fact, guaranteed to be 100% perfect, in terms of legality. However, this is my understanding of the text of the GPL. I'm going to do this as a Q&A, taking common questions and answering them.

Q: I want my game to be 100% closed-source. Can I release it with GPL content?

A: No. The GPL content must be made available, and you must include a prominent notice that states you are making use of it.

In a Spring game, this means that if 99% of your code was written entirely by you, without re-using GPL'd code, then that 99% is still yours, it's private, and in theory you can tell people they can't use it. That 1% that is GPL, however, comes with obligations.

What are these obligations?

1. Provide a manifest (a text file) detailing what GPL code was used. If, for example, you're using my Nuke scripts or other FX code, then just put a textfile saying, "This game contains the following code, which was originally released under the GPL: ScriptThatMakesThingsGoBoom.tdf, etc., which can be downloaded in its entirety at http://whatever.com"

2. Include the original source files. That way, people wanting to verify that you are playing fair don't have to spend a lot've time checking your work.

3. Make sure to include the text of the GPL license (probably at the bottom of the manifest file would be easiest). If you have never read the license, then you can find it here: http://www.gnu.org/licenses/gpl.txt



Q: If I release a game with GPL content in it, is everything in my game subject to the GPL?

A: No. The GPL only applies to the GPL code or other content you are using. It does not mean you have signed away your rights.



Q: Do I give up my copyrights to my content, if I make it available under the GPL?

A: No. If somebody takes your work and claims it as their own, you can pursue them, both for violation of the GPL and for violation of copyright law. Releasing under the GPL does not, for example, give people the right to take your work, put it into some other game, and make money off of your work.



Q: Let's say that I'm releasing a game that contains... artwork or other elements that are copyrighted to somebody else. Just theoretically, heh. If I get shut down by the owners of the copyright, will that get whoever made the GPL code in trouble, too?

A: No. In fact, adhering to the GPL means that you are less likely to get whoever wrote the GPL'd code in trouble, because it will be crystal clear that you were using someone else's work.



Q: I want to charge money for my game at some point. If it contains GPL code, and it is adheres to the license, can I do that?

A: YES! The GPL does not prevent you from doing so- in fact, that is one of the reasons it was made in the first place- to avoid people continually suing each other over really important algorithms that get used for all sorts of commercial stuff.


In short... the GPL is about three things:

1. Proper credit- i.e., not labeling stuff as yours, when it was actually made by someone else.
2. Making it clear to the public that your work is building on the work of other people.
3. Leveraging the work of other people to build other really cool stuff. Following the rules means that you can use all of this cool stuff openly, without obfuscation, guilt, or any legal problems!

The GPL is good for everybody working on Spring. It allows people like me to contribute some of their best work to the community without having to worry about it getting ripped off without proper credit. It allows modders who aren't quite as technically proficient to use GPL'd code without any problems down the line about copyright. And it allows everybody to build on everybody else's GPL'd work. It's a very good thing, and the rules are super-easy to follow.

*************************************************************


After the E&E disaster, I have read posts indicating that even after explaining all this stuff once, it still wasn't clear what I was getting mad about in the first place.

I was not mad that Fang was using my stuff. That's what the GPL is for.

I was not mad that Fang did not want to make his entire mod GPL. That is his choice. And it's 100% legal.

I was mad that Fang would not follow the GPL rules, even after I explained what I needed him to do. I thought I had made myself 100% clear, but from his statements after the fact, this does not seem to be the case.

Apparently, this is because Fang thought that releasing his mod with GPL'd content would make his mod 100% GPL.

As I have stated above, this is not true. The GPL is not some legal disease which will "infect" your game and make it so that anybody can come in, change a few variables here and there, and start claiming your work as their own. In fact, it is the OPPOSITE. It protects you from people just ripping you off. And using a little GPL'd code, properly documented, does not put your entire game under the GPL!

Basically, people, I have been releasing stuff under the GPL, because I want people around here to get used to the idea that, at some point in the future, Spring will go 100% legal. We need to get used to the idea that, instead of being "modders" who are actually in violation of the law most of the time, we are "game designers", making legal work, that we can actually protect... sell... or give away. How one gives things away is as important as the act of doing it- does it come with any strings, or can anybody anywhere use the work?

If you want anybody anywhere to be able to use your stuff, without having to give you credit or anything... release under the Creative Commons license found with NanoBlobs. Under the law in almost any country, that should be sufficient to nullify your copyrights.

If you wish to retain copyrights, and you want people to have to acknowledge your contributions to their work, release under the GPL.

That is, in short, why I licensed the artwork and sounds for NanoBlobs with the Creative Commons license, but the code is released under the GPL. I think the code is far more valuable, basically, and I wanted to make sure that nobody could rip me off.

If anybody has any further questions, please let me know. Please do not restart the flame-war about E&E. They took down their release, deleted all GPL code from the mod, and I am explicitly credited, so I am satisfied that they are no longer in violation of the rules.

That isn't a useful comment FA, its clear you and argh don't agree on this issue. -Moderator

I just want to say, that your following explaination is very enlightening and had I heard this before hand I probably would have reacted differently.

As it was I am sorry I took this the wrong way I did not understand the full implications of what was going on and in the heat of the moment did some things I shouldnt have. I am sorry, I wish I had, had a better understanding of the GPL setup as Im almost positive if I had understood it as you have layed it out here then my overall problem would have been nothing. Thank you for posting this explaination I just found it enlightening and Im sure other people will too..

Argh puts a lot of very hard work into the stuff he does for Spring and I completely respect his decision to GPL it. I think he may have overreacted a bit, but I think we can all understand the frustration when someone else uses your work.

This whole thing sounds like a miscommunication on Argh's/Fang's part and I don't see the need for the huge fight.

<snips>

Sheekel is right, I need to not act like a tard. And Fang, for what it's worth, I wish none of this crap had happened either.

<snip>

nm

I might actually recommend that this is put up as a sticky and revised regularly. I planned to add a section on GPL to the Wiki, so I may simply step that up.

Q: If I release a game with GPL content in it, is everything in my game subject to the GPL?

A: No. The GPL only applies to the GPL code or other content you are using. It does not mean you have signed away your rights.

This is incorrect

... could you elaborate?

At least everything that is linked somehow to the GPL content needs to be GPL, perhaps even the entire mod. I think LGPL would be safer for these purposes, if you want a "give and take" system.

The official FAQ is also helpful:
http://www.gnu.org/licenses/gpl-faq.html

madman2003 wrote:At least everything that is linked somehow to the GPL content needs to be GPL, perhaps even the entire mod. I think LGPL would be safer for these purposes, if you want a "give and take" system.

Linked is an inaccurate term. The most precise way to put it is that anything "derived from" the GPL'd content has to be GPL'd. So if you use a GPL'd function or block of code in a script, that script is probably GPL'd. However, none of your other scripts are, unless they are also "derived from" the GPL'd content. One could argue that a model is derived from its textures (or the textures from the model), but this probably wouldn't hold up in court.

Here, read this.

http://www.gnu.org/licenses/gpl-faq.htm ... NUSoftware

madman2003 wrote:At least everything that is linked somehow to the GPL content needs to be GPL, perhaps even the entire mod. I think LGPL would be safer for these purposes, if you want a "give and take" system.

This is actually sort of ambiguous.

Here's the relevant section of the GPL:
I think that this does require the entire mod to be released into GPL if parts of the mod are modifications of GPL'd source. I've *'d the section I think is relevant.

I'd reccomend that Argh simply create his own license. A license need not be long and be written in complex legalese. For example, I think this encapsulates his intentions:

Section 2b is a bit vague in this context.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

But obviously you could add some exception/addendum thingie specifying that "work" refers to each and every script file in the mod. (And I actually think it would be a good idea to do that).

EDIT: I'm slow.

@ felix: the disadvantage of writing random new licenses is that they are untested, unless you are a lawyer you can easily leave big gaps open, plus that it basically means no one can combine your stuff with something else (as in inclusion with spring, for example) because you need a GNU lawyer to figure out whether the custom license is compatible with the GPL...

@ Argh: GNU software != GPL'ed software. The GNU thing doesn't really have anything to do with the GPL thing except that they wrote it

Also read this:
http://www.gnu.org/licenses/gpl-faq.htm ... ggregation

Argh wrote:Here, read this.

URL removed

Do you mean the specific question? (which seems very strange in this case)

Then that's what I will do, in the next version of NanoBlobs, so that people will free to use them.

My posted license, in the root of NanoBlobs, stated:

All BOS code included in this game is hereby released under the GPL.
All other information in this game is hereby released under the Creative Commons license.

If you need to know the details of the licenses, and your rights and responsibilities under them, please read the files GNU_PUBLIC_LICENSE.txt and CC_PUBLIC_LICENSE.txt, respectively.

I will change it so that it specifically states that each BOS script is released and licensed separately under the GPL, and similar language to that effect for the FX code and other special code. That should take care of that issue.

Tobi wrote: @ felix: the disadvantage of writing random new licenses is that they are untested, unless you are a lawyer you can easily leave big gaps open, plus that it basically means no one can combine your stuff with something else (as in inclusion with spring, for example) because you need a GNU lawyer to figure out whether the custom license is compatible with the GPL...

thanks Tobi... i'm starting to dislike GNU and the GPL more and more, the more I find out about it. (for example, GNU are a bunch of commies, etc.)

They aren't Communists.

They're people who got sick and tired of the big corporations patenting software methods in various languages to the point where everybody was getting sued by everybody else, and little guys with smart ideas were getting screwed- big companies would show up with a bunch of lawyers and patent-infringement claims, and force the little guys to either close up shop, pay them huge royalties, or let the big corporations buy them out at a fraction of their real worth, based on legal attacks. The law, especially here in the U.S.A., does not favor the little guy. It's far more expensive to defend yourself than it is to attack, and either way it's wasted revenue.

In short, you should like these people, if you like freedom. Without them, the Internet would not exist as it does today. Most of the major technologies we use, including this message board, were built on the GPL, to keep the rich and powerful from limiting our freedom. The GPL was designed to make it a lot less possible for people to take away our freedom to innovate.

Argh wrote:Include the original source files. That way, people wanting to verify that you are playing fair don't have to spend a lot've time checking your work.

Why do you think this is necessary?