2 ms·
Sidestep this debate with one trick - use the GPLv3. No company large enough to have a legal team will be able to use it, you're still squarely within the vario
by nemomarx 1y ago
Sidestep this debate with one trick - use the GPLv3. No company large enough to have a legal team will be able to use it, you're still squarely within the various definitions, and the FSF basically has to approve.
As a bonus maybe you can get some proprietary software open sourced too.
- fleebee 1y agoIs there a real reason not to use AGPL? The fact that it makes Google very uncomfortable[1] is a great selling point to me. [1]: https://opensource.google/documentation/reference/using/agpl-policy https://opensource.google/documentation/reference/using/agpl...
- nemomarx 1y agoFor the purposes of me being facetious, it's less infectious than v3. but yeah it would have the same impact on large corps I think
- em-bee 1y agoit's less infectious than v3 putting aside the argument about how infectious the GPL is in general, the the current AGPL is based on the GPL v3. it adds additional requirements. so how can it be less infectious than the GPL v3?
- SAI_Peregrinus 1y agoAGPL is arguably an EULA, not just a copyright license.
- JTbane 1y agoCompanies are happy to use GPLv3 as long as they can put it behind a proprietary SaaS.