4 ms·
I've always contemplated doing this, but as I understand it, public domain isn't recognized internationally, and therefore anything you release to the public do
by geoffhill 15y ago
I've always contemplated doing this, but as I understand it, public domain isn't recognized internationally, and therefore anything you release to the public domain can later be copyrighted by someone else in those non-recognizing regions. Can anyone who is more well-informed weigh in on this?
- arto 15y agoThat is why the Unlicense is designed to be treated as a license as a fall-back strategy (inspired by the Creative Commons Zero public-domain dedication). More particulars at: http://ar.to/2010/01/dissecting-the-unlicense http://ar.to/2010/01/dissecting-the-unlicense
- clarkevans 15y agoOn the OSI's license-discuss list in December it was noted that the unlicense dedication statement is not well formed and could use the assistance/review of a legal professional.
- naner 15y agoPublic domain is ambiguous in some countries: http://stackoverflow.com/questions/219742/open-source-why-not-release-into-public-domain http://stackoverflow.com/questions/219742/open-source-why-no... There are ways to work around this such as what SQLite does (public domain + explicit license to anyone who asks): http://www.sqlite.org/copyright.html http://www.sqlite.org/copyright.html and CC0: http://creativecommons.org/choose/zero/ http://creativecommons.org/choose/zero/
- clarkevans 15y agoThe CC0 is currently under an license-review discussion at the OSI. The CC0 explicitly excludes patent rights from the permission and therefore may not be a great choice for a free software license.