4 ms·
A potential pitfall is that only AGPLv3 and GPLv3 are directly compatible (in the sense of producing programs created from both AGPLv3 and GPLv3 code without vi
by wongarsu 7y ago
A potential pitfall is that only AGPLv3 and GPLv3 are directly compatible (in the sense of producing programs created from both AGPLv3 and GPLv3 code without violating either license). That's not possible with GPLv2 or AGPLv1 in any combination, and there's still some code-bases that will be GPLv2 forever.
But if that's not a concern then I would agree that AGPL is exactly how the GPL should look like in the age of SaaS, PaaS and all the other ?aaS.
- juuul 7y agoThat's not entirely true. GPLv3 and AGPLv3 have explicit clauses that allow the linking of GPLv3 and AGPLv3 code into a single work without violating either license: https://en.wikipedia.org/wiki/Affero_General_Public_License#Compatibility_with_the_GPL https://en.wikipedia.org/wiki/Affero_General_Public_License#... You're right about GPLv2 though.
- afiori 7y agoBut GPLv2 is the one that allows for tivoization, and whether that violates the spirit of free code does not have a consensus.
- lonelappde 7y agoNothing has consensus, that's why there are so many licenses.