Skip to content

Latest commit

 

History

History
64 lines (37 loc) · 5.45 KB

DandelicenceV1.4.md

File metadata and controls

64 lines (37 loc) · 5.45 KB
Raw

Dandelicence

A licence that works on good faith, because why can't we all just be friends instead of bickering?

Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence

Version 1.4, 2nd of December 2021

———————————————————————————————————————

Glossary

  • Except where local laws and/or B's licences from §4 state otherwise, redistributions or borrowed content counts as

    • Unmodified if it has received 0 changes,
    • Transformative work if more than 20% of the lines or 20% of the sentences (whichever is more) have been altered from their original borrowing,
    • Near-unmodified if it is somewhere between those two categories.

  • The British English version of this licence is the official version. All other translations are unofficial.

  • A country is defined as a United Nations member state, the Republic of China, the Sahrawi Arab Democratic Republic's Free Zone, Vatican State, Kosovo, or Northern Cyprus.

———————————————————————————————————————

Licence text

Redistribution and use in all forms, with or without modification, with or without commercial purpose, are permitted as long as the following conditions are met:

  1. Redistributions of (near-)unmodified source code must retain this licence text in unmodified form somewhere inside it, or a URL link to it.

  2. The creator(s) of the original project/code may under no circumstances be held responsible for damages, incompatibilities, breakage or unmerchantability, except if the unmodified source code contained live ransomware/malware.

    • 2a. Anyone who modify the source code to add live ransomware/malware that was not originally in the source code, can be held responsible for it.

  1. The name(s) of the copyright/trademark holder or contributors may not be used to endorse products forked from this software without explicit prior written permission.

  2. If a project with this licence (A), incorporates (near-)unmodified content from another project (B), then A's official maintainer(s) are required to follow requests made by B that are about creditations of them or their project, and/or removal of that content. In return, B is expected to assume for ≥14 days after the request is placed that A's official maintainer(s) will act in good faith and will perform the request within that timespan, and that DMCA claims and admin reports are to be kept at an absolute minimum for as long as A acts in good faith.

    • 4a. If B's project was licenced with a creditation requirement⁽¹⁾, it is expected that A will add crediting without needing to be told to do so, though the principle of asking about it and expecting good faith applies in this case as well.
    • 4b. If B's project was licenced with a share-alike clause⁽²⁾, then (near-)unmodified content that is taken from B shall be treated as still being licenced with B's licence.
    • 4c. A's owners can, through written text, donate and relicence any portion of their code to any other project, even if it has not become transformative work, unless it's affected by 4b.

  1. If a different licence is specified as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes full precedence.

  2. Transformative versions of the source code can be relicenced into any licence, but will remain subject to §2, §3 and §5.

    • 6a) For those parts of the relicenced source code that were previously added to the source code from B, §4. applies to such content as well.

  1. Any (near-)unmodified redistributions of the source code, shall be accessible in some way in ≥100 countries worldwide⁽³⁾. VPN access does not count. If the work is not available in enough countries, any living person can request that A's maintainer must make it available in 10 more countries within 14 days. Once a 14-day period has finished, a new request can be placed, until 100 countries have been reached.

  2. It is forbidden to sell (near-)unmodified source code as standalone paid products in quantities limited to less than 500,000 copies. This includes non-fungible tokens (NFTs), limited-run books (incl. schoolbooks), password-protected ZIP files, among other things.

———————————————————————————————————————

Non-mandatory guidelines

  • If it's feasible, the incorporated content from B is to be placed in its own section, and the following template or something similar should be used: "Below are <content> that [I/we] borrowed from <the name of B>, which is maintained by <link to B's maintainer> at <link to B's project>, and which is licenced under <B's licence>."
  • It is preferable to write the copyright sign as © instead of (C).
  • Adding name/year copyright-info is optional, but a name or nickname to refer to the owner as, should be stated clearly in the licence and/or in the source code.

———————————————————————————————————————

⁽¹⁾ = Including GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA and CC BY-NC-SA (among others).
⁽²⁾ = Including GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse and EUPL (among others).
⁽³⁾ = This is to prevent it from only being available in very geographically limited places, e.g. many US streaming services, or Asian MMO games without non-Asian servers.