3 ms·

You can also use CC0 for software to dedicate something into the public domain.

• smartmic 7y ago
  Or use https://unlicense.org/ https://unlicense.org/
• est31 7y ago
  In many countries, you can't release your works into the public domain. You can only license them. Thus you should generally avoid CC0.
  • zokier 7y ago
    CC0 is explicitly designed with such legal issues in mind and includes a license for legislations that do not have direct way of putting works to PD > If the waiver isn’t effective for any reason, then CC0 acts as a license from the affirmer granting the public an unconditional, irrevocable, non exclusive, royalty free license to use the work for any purpose. https://wiki.creativecommons.org/wiki/CC0_FAQ#How_does_it_work.3F https://wiki.creativecommons.org/wiki/CC0_FAQ#How_does_it_wo... https://creativecommons.org/share-your-work/public-domain/cc0/ https://creativecommons.org/share-your-work/public-domain/cc...
    • est31 7y ago
      Alright thanks for pointing that out, I misremembered it then.
  • vertex-four 7y ago
    The point of CC0 is that it puts things in the public domain if possible, and provides the most liberal license if not. See the "public license fallback" - https://creativecommons.org/publicdomain/zero/1.0/legalcode https://creativecommons.org/publicdomain/zero/1.0/legalcode
• fanf2 7y ago
  CC0 has a mildly problematic patents clause, so if you want to avoid questions about that you might prefer 0BSD. There is a longer explanation on the OSI FAQ https://opensource.org/faq#cc-zero https://opensource.org/faq#cc-zero
  • legulere 7y ago
    BSD is unclear about patents. How is that better than explicitly stating that the license is just about copyright?