Messages in this thread | | | Subject | RE: GPL and NON GPL version modules | From | Xavier Bestel <> | Date | Tue, 16 May 2006 10:52:05 +0200 |
| |
On Tue, 2006-05-16 at 05:42, David Schwartz wrote: > > 1. I developed a code which interfaces well with a proprietary OS. Now, > > somebody else feels to use the same module in his Linux Kernel. So, he > > comes up with a patch, which interfaces and talks to my module with my > > interfaces and then makes a release with the patch. And, I would have no > > idea of my module being really compatible/used in Linux Kernel. One fine > > day, I would get a mail saying that I need to make my code open source. > > What would be my reply? > > When you say "makes a release with the patch", what are you talking about? > A release of what? It sounds like all you need to do is include a note in > your license that you prohibit combining your code with GPL'd code and > distributing the result. Talk to a lawyer about the right wording, but you > want to impose complying with any GPL obligations on the person who chooses > to combine your code with GPL'd code. Then it's not your problem. > > However, I don't see how it's your problem anyway. This sounds way outside > the scope of the GPL or any copyright license. Since your module is not a > derivative work of any GPL'd work, it should be well outside the scope of > the GPL.
Unless the "someone else will release a GPL wrapper to my proprietary module" accident is planned from the start.
Xav
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |