Thanks for your response!
So I would start writing the stuff... but I'm afraid it would be then limited to the functions that I'm using for my site, and of course some explanations depend on the theme that I'm using 😄
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.
I also think.
Thank you (I reread me I realize that it should not easy to decipher my English).
Your english is not as bad as you make it out to be.
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.
Strictly speaking though, I was talking about hosting this in the Cloud for people to use, no software is distributed to the user. They don't get any files for the software.
DISCLAIMER: I'm not a lawyer...
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.