Let's say I have a game that has 2 programs. One is a client for players to use, and the other one is a server. Both use GPLed code. I understand that I have to give the client's code if requested to any third parties, however, if the server binaries and code are only used in my team's computers, if they don't distribute it, do I have to give my server's code because it is used as a part of the game, even if it's separated from the binaries given to the public?

IANAL, but if my interpretation of the GPL is correct, no you don't have to just give away the code to the server, since it's not meant for distribution, however, if you one day decide that you want to sublend, rent, or license the server to anyone in order to leverage the serving costs or whatever reason, you would be required to make the code available to them.

This is more an addition to your question vs. an answer but here it goes. I thought that you only had to provide the original source if you didn't modify the GPL'd thirdparty source. As your integration with the thirdparty source is not their intellectual property. But, if you modify the thirdparty source to fit your needs you had to provide source for the modifications. Is this true? I've always been kinda leary when it comes to the GPL licensing scheme.

Thanks!

If you use the gpl'd code in a dll you can give that code away without worrying about giving away game code.

Personally I keep my stuff gpl free. Look for alternative licenses like the BSD licence which is give credit.

Quote: Original post by ArmitageIII87
This is more an addition to your question vs. an answer but here it goes. I thought that you only had to provide the original source if you didn't modify the GPL'd thirdparty source. As your integration with the thirdparty source is not their intellectual property. But, if you modify the thirdparty source to fit your needs you had to provide source for the modifications. Is this true? I've always been kinda leary when it comes to the GPL licensing scheme.

If you use GPL code in an application all code in the application must then become covered by the GPL.

Here's a good FAQ about the GPL.

But if you use a program that is GPL to do something like make artwork for a game you don't have to make the game GPL (as long as no GPL code is in the game). The blender page has a good guide about the GPL for artists.

Quote: Original post by anonuser
If you use the gpl'd code in a dll you can give that code away without worrying about giving away game code.

I'm not an expert on the GPL, but i'm not sure if that's correct. However, if you use code that is LGPL (GNU Lesser General Public License) you can definately use a dll without worry.

Quote: Personally I keep my stuff gpl free. Look for alternative licenses like the BSD licence which is give credit.

The MIT license is also good for that type of thing.

Quote: Original post by anonuser
If you use the gpl'd code in a dll you can give that code away without worrying about giving away game code.

False, you're thinking of the LGPL, if you link against a GPL .dll, .so, or whatever, it doesn't matter whether or not it is dynamically linked or if you made no modifications, your code becomes GPL as well, hence you must provide a way for the end user to obtain the code to your application.

Quote: Original post by Kwizatz

Quote: Original post by anonuser
If you use the gpl'd code in a dll you can give that code away without worrying about giving away game code.

False, you're thinking of the LGPL, if you link against a GPL .dll, .so, or whatever, it doesn't matter whether or not it is dynamically linked or if you made no modifications, your code becomes GPL as well, hence you must provide a way for the end user to obtain the code to your application.

Are you sure about that ? You are saying if you dynamically link to gpl'd dll you must open your source code up ? So only gpl licensed programs can use gpl dll's ?

can you please confirm this .. Thanks.

Quote: Original post by Codemonger
Are you sure about that ? You are saying if you dynamically link to gpl'd dll you must open your source code up ? So only gpl licensed programs can use gpl dll's ?

can you please confirm this .. Thanks.

Sure:

Quote:
The GNU Project has two principal licenses to use for libraries. One is the GNU Library GPL; the other is the ordinary GNU GPL. The choice of license makes a big difference: using the Library GPL permits use of the library in proprietary programs; using the ordinary GPL for a library makes it available only for free programs.

Which license is best for a given library is a matter of strategy, and it depends on the details of the situation. At present, most GNU libraries are covered by the Library GPL, and that means we are using only one of these two strategies, neglecting the other. So we are now seeking more libraries to release under the ordinary GPL.

Proprietary software developers have the advantage of money; free software developers need to make advantages for each other. Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it.

Source: Why Not LGPL

Edit: This is why you absolutelly cannot keep the source code for anything you code using the Cygwin runtime closed.

hmm I had a quick thought. If a 12 year old kid created a piece of software using GPL code, surely the GPL agreement is not valid (at least in most countries) because a child cannot enter into a contract without parental consent. And their are no laws that I am familiar with that would require someone to be a certain age to use software. So how would GPL be handled in this situation ?

Just trying to get my head around the whole GPL thing, to understand it better.

Quote: Edit: This is why you absolutelly cannot keep the source code for anything you code using the Cygwin runtime closed.

I'm not a linux user yet, but is everything in Linux open source ? (all software programs, libraries, etc)

Thanks.