Moderator: MacroQuest Developers


Thats the whole point of the GPL. Yes you could add it to the CVS in part or full. They say you can sell copies but you can't put restrictions with what people do with the source once they get it. That keeps a big company from sucking up some code and adding a little functionality then selling it for major profit. They could sell copies but they would also have to make the source (which still falls under GPL) avalible.Wishbringer wrote:So, in other words, only one person has to buy this "gold thingy", has to request source, can sue eqplat when not giving him the source, and can put it in CVS if he wants...?!
Am not sure about putting source in CVS...
AndThe GPL does not require you to release your modified version. You are free to make modifications and use them privately, without ever releasing them. This applies to organizations (including companies), too; an organization can make a modified version and use it internally without ever releasing it outside the organization.
But if you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the users, under the GPL.
Thus, the GPL gives permission to release the modified program in certain ways, and not in other ways; but the decision of whether to release it is up to you.
On your second question I don't think you could sue. The person who holds the copywrite could and should be notified. If the originator of this project was smart he has left the copywrite with the EFF to handle since they take up these types of things for people. They would sue for the source of the application.Does the GPL allow me to distribute a modified or beta version under a nondisclosure agreement?
No. The GPL says that anyone who receives a copy of your version from you has the right to redistribute copies (modified or not) of that version. It does not give you permission to distribute the work on any more restrictive basis.
What should I do if I discover a possible violation of the GPL?
You should report it. First, check the facts as best you can. Then tell the publisher or copyright holder of the specific GPL-covered program. If that is the Free Software Foundation, write to <license-violation@gnu.org>. Otherwise, the program's maintainer may be the copyright holder, or else could tell you how to contact the copyright holder, so report it to the maintainer.
Who has the power to enforce the GPL?
Since the GPL is a copyright license, the copyright holders of the software are the ones who have the power to enforce the GPL. If you see a violation of the GPL, you should inform the developers of the GPL-covered software involved. They either are the copyright holders, or are connected with the copyright holders.
Why does the FSF require that contributors to FSF-copyrighted programs assign copyright to the FSF? If I hold copyright on a GPL'ed program, should I do this, too? If so, how?
Our lawyers have told us that to be in the best position to enforce the GPL in court against violators, we should keep the copyright status of the program as simple as possible. We do this by asking each contributor to either assign the copyright on his contribution to the FSF, or disclaim copyright on it and thus put it in the public domain.
We also ask individual contributors to get copyright disclaimers from their employers (if any) so that we can be sure those employers won't claim to own the contributions.
Of course, if all the contributors put their code in the public domain, there is no copyright with which to enforce the GPL. So we encourage people to assign copyright on large code contributions, and only put small changes in the public domain.
If you want to make an effort to enforce the GPL on your program, it is probably a good idea for you to follow a similar policy. Please contact <licensing@gnu.org> if you want more information.

This is not legally binding on several levels, here are two: First, to have a valid contract, you must have bargain, consideration and agreement. Second, it violates pre existing duty (on your part, if you are indeed using GPL'd code).GENERAL PUBLIC LICENSE (GPL)
By visiting this site you agree that you will not take the Company to court over any issues related to the GPL (General Public License).
yes I think so and that really gives me a reason to fix it.Do you really think the devs want /click to be public?
donations for this month's patches.

Not fully true...sprite wrote:Take me to court then =)
Plazmic is the copyright owner, so he is needed. Plazmic is not around anymore. If it was taken to court the verdict would most likely be that the source had to be released.

No I dont think anyone wants to spend the time filing, as i stated early in the thread. btw I think anyone could file, since the GPL basically puts the code in the public domain. (The whole point of it is that ther is no copyright holder, it's like an anti-copyright, or copyleft as they like to call it).sprite wrote:Take me to court then =)
Plazmic is the copyright owner, so he is needed. Plazmic is not around anymore. If it was taken to court the verdict would most likely be that the source had to be released.
Do you really think the devs want /click to be public? If you do think again.