Cohabitation with the GPL license of NodeBB ?
-
Thanks for your reply Julien.
Effectively the GPL is not obvious as regards development of some customers orders. This is why I privileged BSD, MIT, Apache, ... licence without hard copyleft
So it's ok for customizing a customer website.
To be sure limits, license NodeBB does not allow to create or adapt a paid plugin for NodeBB ?
I do not sell software but I want to know if one day a customer that sells an application ask me to integrate with other app, if I can add NodeBB in its software (or lib) or add its software (or lib) in NodeBB.
-
In my opinion (and again, I could be wrong), creating a paid plugin is no different from a free one. I view it not as a "derivative" of NodeBB, but rather just an additional functionality add-on, which would be entirely separate.
Now, on the other hand, if you were to sell your version of NodeBB with that plugin pre-installed, then that would run afoul of the GPLv3.
-
@julian said:
Keep in mind I am not a lawyer. You would be wise to look for a second opinion on the matter
Would there be any restriction if I use NodeBB in a paid-for Web Application? The forum functionality is one of the modules in this application. As a SaaS vendor, we would host a modified version of NodeBB in our own environment. We would have no problem sharing the parts of NodeBB that are modified.
-
@jhui, according to the GPL, the entire project's source code must be released under the GPL license, if you are intending to redistribute the software, which you are.
There is no restriction on you combining the software for personal use, but redistribution is where the GPL comes into full effect.
-
-
DISCLAIMER: I'm not a lawyer...
There is a difference within GPL when it comes to compiled software vs non-compiled software. Do some reading up in that regard. I believe what you are mentioning has to do with compiled software not something like nodebb or other javascript apps. I would guess several of the modules that nodebb depends on aren't GPL and probably several of the modules those modules use.
-
Yes things get tougher when we get into the specifics of the licensing all of our dependent packages use. To make things easier, we use the GPLv3, which co-habitates well with other free/open-source licenses, but does preclude the use of it in a commecial/resold context.
