It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.
It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.
Absolutely not! Avoid CC0! Stop spreading bad information. If you want a public domain dedication with fallback permissive license the best choice is (sadly) The Unlicense. It is the only public domain dedication with fallback permissive license approved by both FSF and OSI. It’s unfortunate because The Unlicense is still a crayon license.
If you don’t want to burden some stream projects with including copyright notices, just don’t enforce it if you find people who forgot.
https://www.gnu.org/licenses/license-list.html#CC0
“just don’t enforce it” probably isn’t enough for most companies and projects
If your company won’t let you use MIT licensed software I don’t know what to tell ya. If your company won’t let you use MIT code, which FSF and OSI endorse, but will let you use CC0 code, which FSF and OSI do not endorse, then I really don’t know what to tell ya.