119

I have often heard that I should not use the Unlicense because of issues regarding putting things into the public domain. However, I do not understand why this would be an issue for the Unlicense. The Unlicense attempts to put whatever is being unlicensed into the public domain, and if that works, awesome! However, the author of the Unlicense understands that putting something into the public domain is not so simple, it may even be impossible, and therefore the Unlicense contains a backup clause (the 2nd paragraph) which clearly states that everyone is free to do whatever they want with the Unlicensed software. The Unlicense even includes a disclaimer containing the usual "this software is provided as-is blah blah" legalese.

Is the Unlicense bad because it is short and doesn't define who the "unlicensor", the "unlicensee" and Santa Claus is? If yes, then what about the MIT/BSD-style licenses? They are generally considered to be valid, so why isn't the Unlicense? Is the opposition to public domain waivers with permissive license backup clauses, such as the Unlicense, and even the Creative Commons CC0, just FUD or are there really major legal issues with them?

Here is the full text of the Unlicense:

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to http://unlicense.org/

Improve this question
6
  • 10
    Can you link to someone that is discussing the issues that you're concerned about?
    – Justin Cave
    May 3, 2012 at 15:47
  • 31
    There is nothing wrong with this question. It's common knowledge that the concept of public domain doesn't exist in all areas, and this is a valid question about if this particular license is suitable and valid for software projects.
    – Thomas Owens ♦
    May 3, 2012 at 15:55
  • 3
    This question appears to be off-topic because it is about a license issue.
    – Jim G.
    Jul 8, 2014 at 1:08
  • 16
    @JimG. Software licensing is a valid topic for this site.
    – cgt
    Jul 9, 2014 at 1:30
  • Use 0BSD which was created earlier but doesn't have any issues as the Unlicense and used by a Google itself in Android (Toybox)
    – Sergey Ponomarev
    Apr 28 at 14:36

2 Answers 2

Reset to default
87

(Disclaimer: IANAL - for reliable advice on legal issues, ask a lawyer.)

See [the discussion on the OSI mailing list][1] for some of the immediate issues with the license. My interpretation:

  • It's not global. It doesn't make sense outside of a commonwealth ecosystem, is explicitly illegal in some places (Germany), and of unclear legality in others (Australia)
  • It's inconsistent. Some of the warranty terms cannot, logically, co-exist, given the current legal ecosystem, as written, with the licensing terms.
  • Its applicability is unpredictable. The license is short, clearly expressing intent, at the cost of not carefully addressing common license, copy-right and warranty issues. It leaves a lot of leeway interpretation - meaning that, in the US, it will take a few trials before you can reliably know when the license is applicable, and how.

Personally, I think of the license as having been written in human-readable pseudo-code, without having been properly compiled yet to a given set of legal systems.

[1]: https://lists.opensource.org/pipermail/license-review_lists.opensource.org/2012-January/001386.html (archived)

Improve this answer
25
  • 18
    It looks like CC0 has done a much better job at the "compilation", including making sure the license degrades gracefully in systems where it's not possible to legally apply parts of it. I'm not a lawyer - but it looks like there's a body of work discussing the finer points of where the CC0 applies and where it doesn't, meaning it's written well enough for the legal system to take seriously. So I'd say, reliable, but no guarantee it works as written everywhere.
    – blueberryfields
    May 3, 2012 at 17:15
  • 21
    @blueberryfields I'm curious, why the Unlicense is illegal in Germany? I couldn't find it on Google...
    – Metalcoder
    Oct 2, 2013 at 13:57
  • 10
    @Metalcoder looks like the stackexchange question i was referencing has been deleted. Again, I'm not a lawyer, so don't take this as 100% true, but, as I understand it, in Germany it is explicitly illegal for anyone to relinquish all rights, in perpetuity, to the public domain; there is no easy graceful way to degrade built into the law - you're expected to list, in excruciating detail, how all of the related legal cases are to be handled; judges are much more hesitant there, in general, to attempt to decipher intent and judge based on that.
    – blueberryfields
    Oct 2, 2013 at 15:13
  • 18
    This means that, for example, if you unlicence a piece of software, in Germany, technically, your inheritors still might own some of the relevant rights, and might be able to start going after people for money, or with cease and desist letters, after you've passed away. Or you can change your mind, and do this. Meaning that unlicensing your software makes it potentially dangerous for german companies to use
    – blueberryfields
    Oct 2, 2013 at 15:15
  • 6
    And then when you've created "unlicense 2", make a website which hosts all of the unlicensed code, and releases it under "unlicense 2". (You're allowed to do this because... hey! it's unlicensed!) . ...and then what will that mean? It means german copyright law just exploded in a puff of logic
    – Harry Wood
    Jun 10, 2016 at 15:06
3

Doesn't work for Google

Forbidden patches

Our general philosophy is that we do not allow patches to projects that Google cannot use, either because of the terms of the license or Google policy. For example, we can’t use software that restricts commercial use, and so we don’t contribute to those projects. In some cases, you may be able to contribute to these projects via IARC.

You can’t patch projects with any of the following licenses:

  • No License

  • WTFPL

  • AGPL (except those with special exceptions)

  • Public domain dedications (including CC0 and Unlicense)

    • Exceptions: United States government projects; BSD0.

  • CC BY-NC-* (this restricts Google’s access to that code)

  • Hippocratic License or similar “Ethical Source” licenses (not OSI approved)

  • Private repositories (unless under a written agreement between Google and a third party)

Improve this answer
3
  • 13
    This is Google's internal policy and doesn't explain what's wrong with the license.
    – user253751
    Oct 15, 2020 at 11:37
  • 10
    Google’s policy prohibits “Public domain dedications”. It has nothing to do with explaining why Unlicense is a bad way to dedicate your work to Public domain.
    – kirelagin
    Oct 15, 2020 at 23:22
  • 3
    Frankly, I consider the fact Google wouldn't touch public domain code to be a nice bonus rather than a negative - it's not a bug, it's a feature!
    – Pharap
    Oct 21, 2022 at 14:20

Not the answer you're looking for? Browse other questions tagged or ask your own question.