[License-review] Request for legacy approval: The Unlicense

[Brendan Hickey]

Unlicense should not be approved under any circumstance, regardless of
popularity.  The public domain dedication simply doesn't work. Some
countries outside of the US (Germany?) don't recognize these grants. CC0
anticipates jurisdictional issues and contains a fallback grant of rights.
Without this, no one can actually rely on Unlicense.

I wish this wasn't the case, but Unlicense is a great example of why we
should listen to specialist attorneys on licensing matters.

Brendan

On Sun, Mar 29, 2020, 12:42 PM <osi-license-review at jaeckel.eu> wrote:

> The license
> ===========
>
> 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/>
>
> The rationale
> =============
>
> The Unlicense exists since 10 years [1] to give projects the possibility
> to dedicate their code into the public domain in jurisdictions that
> don't have an understanding of the public domain. The homepage at
> https://unlicense.org/ lists a wide variety of software that already
> uses said license. A search on GitHub for projects using The Unlicense
> [2] returns by the time of writing 133,188 repositories using it (not
> including forks of repositories).
>
> Proliferation category
> ======================
>
> Licenses that are popular and widely used or with strong communities
>
> Reasoning for this category
> ---------------------------
>
> e.g. the EPL1.0 and EPL2.0 licenses together don't have half of the
> number of repositories (38,117 [3] resp. 12,509 [4]) and they fall as
> well under this category.
>
>
>
>
> Thank you for your work and considering the approval of The Unlicense to
> the wide and well-chosen variety of Open Source Licenses.
>
>
> Kind regards,
> Steffen Jaeckel
>
>
> [1] https://ar.to/2010/01/set-your-code-free
> [2]
>
> https://github.com/search?q=license%3Aunlicense&type=Repositories&ref=advsearch&l=&l=
> [3]
>
> https://github.com/search?q=license%3Aepl-1.0&type=Repositories&ref=advsearch&l=&l=
> [4]
>
> https://github.com/search?q=license%3Aepl-2.0&type=Repositories&ref=advsearch&l=&l=
>
> _______________________________________________
> The opinions expressed in this email are those of the sender and not
> necessarily those of the Open Source Initiative. Communication from the
> Open Source Initiative will be sent from an opensource.org email address.
>
> License-review mailing list
> License-review at lists.opensource.org
>
> http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20200329/d719dc0b/attachment.html>