4 ms·
AGPL is fine for open source projects. It isn’t really useful for a commercial closed-source or even an open-core codebase in some cases. On the other hand, us
by twodave 3y ago
AGPL is fine for open source projects. It isn’t really useful for a commercial closed-source or even an open-core codebase in some cases.
On the other hand, usually that’s the intention when a project selects AGPL. There’s usually a commercial license you can buy instead (see iText for example).
- anileated 3y agoAGPL is absolutely fine for commercial closed-source projects. Don’t fall for anti-AGPL propaganda. https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html
- twodave 3y agoIt isn't fine because it will come up in due diligence as a risk, every single time. It's easy to say "it's fine", and in theory I agree with you. But it's a cost that doesn't make sense if you know what the auditors are going to say and expect. Auditors flag even more benign things than the AGPL, but to pretend it's not a thing is just whimsy.
- freedomben 3y agoI very much want drew's post to be correct, but I can't let confirmation bias cause me to consider this due diligence. Are there any lawyers or legal cases that you know of that have proven this? or at least lawyers who have reviewed it and given a legal opinion?