3 ms·
Because AGPL is so highly restrictive that most OSS foundations won't have projects use it - they prefer the far more permissive Apache/MIT/BSD licenses
by jjirsa 10y ago
Because AGPL is so highly restrictive that most OSS foundations won't have projects use it - they prefer the far more permissive Apache/MIT/BSD licenses
- drdaeman 10y agoYes, I've heard similar things. But they're really generic - that's why I've asked. I was wondering if there are somewhat more concrete examples. Like... some specific use cases and clauses that conflict with them.
- jjirsa 10y agoLet's pretend your sponsoring entity makes a security or search appliance (anything from a google mini to a NAT/firewall) - AGPL code shipped on that appliance requires publishing source. Depending on how it's intertwined in the product, that may mean shipping source for the whole product Apache / MIT / BSD have no such restrictions - Apache httpd is on a ton of appliances for that reason