zakalawe wrote:If the FPS guy makes improvements, he's obliged to contribute them.
Are there any obligations about giving credit where credit is due in the license? Cos he's definitely not doing that...
zakalawe wrote:If the FPS guy makes improvements, he's obliged to contribute them.
Algernon wrote:zakalawe wrote:If the FPS guy makes improvements, he's obliged to contribute them.
Are there any obligations about giving credit where credit is due in the license? Cos he's definitely not doing that...
zakalawe wrote:we're GPL, everyone contributing to the code knows that, understands the license, and is comfortable with it.If the FPS guy makes improvements, he's obliged to contribute them.
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#TOCGPLCommercially
You are allowed to sell copies of the modified program commercially, but only under the terms of the GNU GPL. Thus, for instance, you must make the source code available to the users of the program as described in the GPL, and they must be allowed to redistribute and modify it as described in the GPL.
These requirements are the condition for including the GPL-covered code you received in a program of your own.
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLRequireSourcePostedPublic
The 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 program's 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.
Return to The FlightGear project
Users browsing this forum: No registered users and 3 guests