Quote:
Originally Posted by JBotAlan
Since Kevin Watson has expressly stated that he does not want his files re-posted, I am not going to re-post them. It is perfectly fine to GPL my portions of the project. I am also not re-posting IFI-written code as they still hold the copyright whether or not they choose to enforce it. If this project takes off, I am going to make it very clear that people can only license what they own, and nothing more.
JBot
|
Quote:
|
Originally Posted by http://www.gnu.org/licenses/gpl-faq.html
What does it mean to say that two licenses are "compatible"?
In order to combine two programs (or substantial parts of them) into a larger work, you need to have permission to use both programs in this way. If the two programs' licenses permit this, they are compatible. If there is no way to satisfy both licenses at once, they are incompatible.
Can I apply the GPL when writing a plug-in for a non-free program?
If the program dynamically links plug-ins, and they make function calls to each other and share data structures, we believe they form a single program, which must be treated as an extension of both the main program and the plug-ins. This means that combination of the GPL-covered plug-in with the non-free main program would violate the GPL. However, you can resolve that legal problem by adding an exception to your plug-in's license, giving permission to link it with the non-free main program.
|
IANAL, but unless I'm reading this wrong, that would imply that the entire program must be licensed under the GPL, which it is not.