3 ms·
> My non-expert reading of the AGPL seems to indicate that using AGPL code in a commercial project is find as long as you don't change it Any restriction impos
by jraph 5y ago
> My non-expert reading of the AGPL seems to indicate that using AGPL code in a commercial project is find as long as you don't change it
Any restriction imposed by the GPL is also true for the AGPL. In particular, if you reuse some code from a (A)GPL project, even if you don't change the code, you must release your whole project under this license too, and give attribution to the author.
For the LGPL, the same thing applies, except you can reuse LGPL code in your code without releasing it under a *GPL license if someone can replace this code at execution time by another code (static linking does not allow this).
- ineedasername 5y agoBut AGPL & LGPL still don't prohibit commercial use do they? They impose obligations on those using the code to--potentially-- release their own code, but commercial use in & of itself isn't prohbited. Again, I think GitHub is going against the spirit of these licenses and should behave differently. What I'm trying to do in this discussion is simply explore the limitations within the letter of the license. Basically the boundary between being legal, and being legal but still wrong in some other sense. Consider it my exploration of the ethical constraints vs. legal constraints.
- jraph 5y agoYou can use GPL code commercially, as long as you release what needs to be released as GPL for the AGPL, that's probably your entire codebase. You cannot use AGPL code in non-AGPL codebase or as a library in a non-AGPL. Same for LGPL, except you can use LGPL code as a dynamic library in a non-GPL codebase, as long as you redistribute modifications to the LGPL code. You can sell *GPL software or services around it.