2 ms·

Thanks. We didn't originally set out to write a new license, but when we did, we put real time and thought into it. It's nice to see that appreciated. We've sh

Thanks. We didn't originally set out to write a new license, but when we did, we put real time and thought into it. It's nice to see that appreciated. 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.

luord 6y ago
I too like the license, and wouldn't mind using it. Have you considered submitting it for approval to the OSI and FSF?
- kemitchell 6y ago
  Everyone involved in the drafting has been through the OSI license process---or some ever-changing version of it---before. Last we discussed, nobody wanted to do that process again, even for an uncontroversial permissive license. Personally, I don't care what OSI says. If someone else wants to go and ask them about it, more power to them.