Hacker News new | ask | show | jobs
by jabl 2073 days ago
> Since we're now getting deeper into what I personally do, I'll note that in practice, I dual license under the UNLICENSE and the MIT. I use the UNLICENSE because it's goal is to explicitly disclaim monopoly copyright interest while attempting to be a public domain dedication. I also add the MIT because some folks stopped using my code when I only used the UNLICENSE because they were too risk averse and wanted a more established license.

As an aside, an alternative to this dual licensing might be the 0BSD license: http://landley.net/toybox/license.html

It's on spdx: https://spdx.org/licenses/0BSD.html

It's approved by OSI: https://opensource.org/licenses/0BSD

Available on choosealicense.com: https://choosealicense.com/licenses/0bsd/

Unlike the unlicense, google allows it: https://opensource.google/docs/patching/

1 comments

Firstly, I am sooooo over Google's open source policy. I'm thankful that they document it, but it's just plain annoying.

Secondly, I use the UNLICENSE because it is an ideological statement. The 0BSD is not. Dual licensing with the MIT gives me a very small activist voice while also providing a practical option for the risk averse Googles of the world.