3 ms·
Regardless, some companies have a blanket thou-shalt-not-use-AGPL-anything policy.
by bradfitz 3y ago
Regardless, some companies have a blanket thou-shalt-not-use-AGPL-anything policy.
- anonzzzies 3y agoYep, our lawyers say to not use and we have to check components and libs we use too. People are really shooting themselves in the foot with that license.
- aragilar 3y agoYou assume that people want you to use their project. For MinIO, the AGPL seems to be a way to get people into their ecosystem so they can sell exceptions. Others might want you to contribute code back.
- anonzzzies 3y agoI have no problem with contributing back: we do that all the time on MIT / BSD projects even if we don't have to. AGPL just restricts the use-cases and (apparently) there is limited legal precedence in my region to see if we don't have to give away everything that's not even related but uses it, so the lawyers (I am not a lawyer, so I cannot provide more details) say to avoid it completely. Just to be safe. And I am sure it hurts a lot of projects... There are many modern projects that are the same thing, but they don't share code because the code is agpl.
- corobo 3y agoSounds more like the license is doing its job as intended, and businesses that can afford lawyers but not bespoke licenses are shooting themselves in the foot with that policy
- JoshTriplett 3y agoExactly. If someone doesn't want to use your software because the copyleft license is stricter than they would prefer, that's an opportunity to sell them a license.
- anonzzzies 3y agoWe just won’t use their product. Works as well.
- corobo 3y agoEveryone wins :)
- NoraCodes 3y ago[flagged]
- trollian 3y agoLawyercats are the worst cats.
- hiharryhere 3y agoSome companies Including Google. I’ve sold Enterprise Saas to Google and we had to attest we have no AGPL code servicing them. This is for a CRM-like app.