I was involved with a group of open licensing lawyers that ended up publishing a "model" permissive license: https://blueoakcouncil.org/license/1.0.0
It's not everything anyone ever wanted, but we think it's a lot closer.
It's not everything anyone ever wanted, but we think it's a lot closer.
If you are serious about adoption, I suggest providing an official header to embed in files. Something simple like this:
// Licensed under https://blueoakcouncil.org/license/1.0.0
We've shied away from declaring one "right" way to use the license, because norms, conventions, and expectations vary so much across development communities. What's right and normal for, say, Maven artifacts would seem a bit strange in, say, an npm package or a C library.
Personally, I don't care what OSI says. If someone else wants to go and ask them about it, more power to them.