4 ms·
Rather than reviewing any licenses, you should incorporate a license check in your build. I did this in a Gradle project recently, and it was pretty easy: http
by twic 4y ago
Rather than reviewing any licenses, you should incorporate a license check in your build. I did this in a Gradle project recently, and it was pretty easy:
https://hg.sr.ht/~twic/lambda-property-matcher/rev/53ef7eb3051c90722a4624791d59c1719b149907 https://hg.sr.ht/~twic/lambda-property-matcher/rev/53ef7eb30...
- netr0ute 4y agoWhy make it so difficult? Just make your project AGPL and stop worrying about other OSS license compatibility.
- twic 4y agoBecause i'd like my software to be useful to normal people.
- klardotsh 4y agoBecause AGPL implies many things not all developers want associated with their project? Yes, due to their virality, GPL-flavored licenses tend to be the "top type" that you can just cast the top-level project to and call it a day, but try convincing your corporate boss to AGPL your money-making product. That's gonna go about as well as is predictable.
- netr0ute 4y agoThen that's not the company you want to work for.
- Thiez 4y agoAGPL isn't even compatible with GPLv2, so you still have to worry about OSS license compatibility. So given that you have to worry anyway, you might as well pick a less obnoxious license.