> 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 beca

> 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 http://landley.net/toybox/license.html It's on spdx: https://spdx.org/licenses/0BSD.html https://spdx.org/licenses/0BSD.html It's approved by OSI: https://opensource.org/licenses/0BSD https://opensource.org/licenses/0BSD Available on choosealicense.com: https://choosealicense.com/licenses/0bsd/ https://choosealicense.com/licenses/0bsd/ Unlike the unlicense, google allows it: https://opensource.google/docs/patching/ https://opensource.google/docs/patching/