3 ms·

Why not just put stuff into the public domain?

• silentbicycle 13y ago
  The "public domain" designation has its own problems, nicely summarized on Google Code (https://code.google.com/p/support/wiki/FAQ#Can_I_host_code_that_I_have_placed_in_the_public_domain? https://code.google.com/p/support/wiki/FAQ#Can_I_host_code_t...). In particular, Dr. Richard Hipp (SQLite's main author) has talked about problems that came up from releasing it into the public domain. He eventually created a second license specifically for companies in places that didn't legally recognize the public domain, and wanted to make sure they were protected from liability. Licensing is complicated.
  • greenlakejake 13y ago
    Thanks for the link.
  • idupree 13y ago
    CC0 addresses these problems with "public domain"; its intent is the most permissive license that's legally possible (plus, in jurisdictions where it is possible, actually placing the work in the public domain). Unlike the other Creative Commons licenses, it it suitable for source code. ( http://wiki.creativecommons.org/CC0_FAQ http://wiki.creativecommons.org/CC0_FAQ , https://creativecommons.org/choose/zero/ https://creativecommons.org/choose/zero/ )