I'm quite confused about what are the obligations of GPL libraries in the context of plugin based software.
Let's say I want to distribute & sell a plugin based app as closed source providing to the users a set of closed source core plugins as well.
Here's the thing, if both the plugin framework and core plugins are not using any GPL deps and assuming they're not violating license terms of possible deps should not be mandatory to open source any of the code.
Now, here's my question... what happens if some of the plugins (be it plugins either created by the company or by users) use GPL dependencies... Would the GPL dependencies only affect to the plugin(s) or would also infect the host and other closed-source plugins?
Common sense suggests that only the source code of plugins using GPL deps should be opened but considering GPL is virical & nasty I'm not sure anymore.
In fact, if that was the case (which would be crazy), as a user, you could argue companies to open source a whole host app in case you've added a plugin that uses GPL code on a plugin for that host... couldn't you?
- You've created a driver for windows that uses GPL code, would Microsoft be forced to open source the OS?
- You've created a plugin for SublimeText/VisualStudio/3dsMax/(whatever closed source plugin based software goes here) that uses GPL code, would these companies be forced to open source the hosts?
Summing up, could anyone clarify here which type of code GPL libraries would infect directly/indirectly?
Ps. Reason I've opened this thread is because I've found this answer and I found it pretty confusing, specially the part where he says:
(b) If you do distribute YOUR APPLICATION, and you used something GPL as part of your application (even if only linking at run-time to a library) - and even if you do not charge money - and even if you do not change that GPL s/w in any way - then you MUST make the source of YOUR APPLICATION available.
how would you interpret that statement?