"Slap a GPL3 in there" is pretty much the opposite of what the parent commenter wants, though. At 5500 words, GPL3 is a long read - I have a rough idea what it says, but can't say I've ever read and understood every word. Making my users do so might constitute cruel and unusual punishment :)
0BSD looks short and sweet, though. I don't need people using my libraries to include my LICENSE.txt, or give attribution, or tag any changes with their own copyright notice. Just take the code and do whatever you want, no strings attached.
> Making my users do so might constitute cruel and unusual punishment
The very opposite. GPLv3 is written by lawyers and for very good reasons. The more detailed a license is the more clear it is. That's why it clearly defines what constitutes distribution and so on.
This is also why things like rent contracts have long lists of what is allowed and expected and what is not, and when and why and so on: it creates clarity.
Clarity means less debating in court.
If you want legal trouble, sign a very short contract.
> If you want legal trouble, sign a very short contract.
If the length of contract is what is protecting you, you're already in court. If it's a jury trial, all bets are off no matter what the law or contract says.
> If the length of contract is what is protecting you, you're already in court.
Not at all! A strong, detailed, clearly written contract reduces the amount of "wiggle room" for litigation.
The other party is much more likely *not* to sue you in the first place if they know they would be fighting an uphill battle against a strong contract.
That's why GPLv3 has anti-patent-troll clauses for example.
0BSD looks short and sweet, though. I don't need people using my libraries to include my LICENSE.txt, or give attribution, or tag any changes with their own copyright notice. Just take the code and do whatever you want, no strings attached.