├── .github └── FUNDING.yml ├── README.md ├── NerdStats.md ├── DandelicenceV1.3.md ├── DandelicenceNewestVersion.md ├── DandelicenceV1.4.md ├── LICENSE.md ├── DandelicenceV1.md ├── DandelicenceV1.2.md └── DandelicenceV1.1.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | github: DandelionSprout 2 | custom: ["https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=imreeil42@gmail.com&lc=US&item_name=Donations+to+me+(Donasjoner+til+meg)&no_note=0&cn=¤cy_code=NOK&bn=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted", "https://flattr.com/@DandelionSprout"] 3 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | My attempt at creating an open-source licence that works on good faith, specifically crafted for adblock filterlist maintainers. 4 | 5 | As someone who previously used BSD-3 for my projects, I began to worry if tech geeks would take offence to it or not if I semi-automatically added content from other people's GPLv3 projects to them. So I created this licence instead. 6 | 7 | Important legal note: The licence's legal value in a court of law is considered to be highly questionable when it comes to files with GPL or AGPL content (More info at https://github.com/DandelionSprout/Dandelicence/issues/2). Instead, it operates on the concept of ["Why can't we be friends?"](https://deezer.page.link/S6SM79bg7FqFmcfT7), by demonstrating crediting and good intent, especially when it comes to text files, and especially when compared to vanilla BSD-3. 8 | -------------------------------------------------------------------------------- /NerdStats.md: -------------------------------------------------------------------------------- 1 | ## Stats for theorethical inclusion on licence comparison sites 2 | 3 | (Do **NOT** use this as an excuse to not read through [the actual licence text](https://github.com/DandelionSprout/Dandelicence/blob/master/DandelicenceNewestVersion.md)): 4 | 5 | | Ability | Permission | 6 | | - | - | 7 | | Modification | Allowed | 8 | | Redistribution of modifications | Allowed | 9 | | Commercial use of source code | Allowed | 10 | | Commercial use of modifications | Allowed | 11 | | Creditation | Required for source code or light modifications (Not required at all if your modifications have become transformative, or if the original work had no self-creditation to begin with) | 12 | | Share-alike | Required for source code or light modifications (Not required at all if your modifications have become transformative) | 13 | | GPL compatibility | Intended to work by encapsulating GPL source material into GPL-subjected sections/paragraphs. | 14 | | Multi-licencing | Other licences can be stated for individual files and sections; otherwise forbidden | 15 | | Geographical availability | ≥100 countries | 16 | | Ransomware/skimmingware | Forbidden to include | 17 | 18 | ## Alternate licence wording for projects based in politically sensitive areas 19 | 20 | Section 10 in Dandelicence v1.1 (Section 9 in v1.2) normally mentions non-United-Nations countries by the countries' own preferred names. If your project is based in a country where you believe you'll be at risk of persecution if you use those original names, here's Dandelion Sprout's recommended alternate names: 21 | 22 | | Original text | Permitted alternate text | 23 | | - | - | 24 | | Republic of China | Taiwan Area | 25 | | The Sahrawi Arab Democratic Republic's Free Zone | Morocco Southeast Autonomous Provinces | 26 | 27 | It is permitted to use the alternate text even for non-transformative redistributions, as long as `-G` (short for "Geography") is added to the end of the version name, e.g. `v1.1-G` or `v1.2-WIP-G`. 28 | -------------------------------------------------------------------------------- /DandelicenceV1.3.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1.3, 28th of August 2020 8 | 9 | ——————————————————————————————————————— 10 | 11 | ## Glossary 12 | 13 | * Except where local laws and/or B's licences from §4 state otherwise, redistributions or borrowed content counts as 14 | * * **Unmodified** if it has received 0 changes, 15 | * * **Transformative work** if more than 20% of the lines or 20% of the sentences (whichever is more) have been altered from their original borrowing, 16 | * * **Near-unmodified** if it is somewhere between those two categories. 17 | 18 | * The British English version of this licence is the official version. All other translations are unofficial. 19 | 20 | * 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. 21 | 22 | ——————————————————————————————————————— 23 | 24 | ## Licence text 25 | 26 | 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: 27 | 28 | 1) Redistributions of (near-)unmodified source code must retain this licence text in unmodified form somewhere inside it. 29 | 30 | 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/skimmingware. Likewise, anyone who modify the source code to add live ransomware/skimmingware that was not originally in the source code, can be held responsible for it. 31 | 32 | 3) The name(s) of the copyright/trademark holder or contributors may not be used to endorse or promote products derived from this software without explicit prior written permission. 33 | 34 | 4) If a project with this licence (A), incorporates (near-)unmodified content from another project (B), then it's mandatory for A's official maintainer(s) 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 placement 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. 35 | 36 | * * 4a. If B's project was licenced with a creditation requirement⁽¹⁾, it is expected that A will add creditation without needing to be told to do so, although the principle of asking about it and expecting good faith applies in this case as well. 37 | * * 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. 38 | * * 4c. A's owners can, through means of 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. 39 | 40 | 5) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 41 | 42 | 6) Transformative versions of the source code can be relicenced into any licence, but will remain subject to §2, §3 and §5. 43 | 44 | * * 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. 45 | 46 | 7) 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. 47 | 48 | ——————————————————————————————————————— 49 | 50 | ## Non-mandatory guidelines 51 | 52 | * 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 \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 53 | * It is preferable to write the copyright sign as © instead of (C). 54 | * 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. 55 | 56 | ——————————————————————————————————————— 57 | 58 | ⁽¹⁾ = Including GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA and CC BY-NC-SA (among others).
59 | ⁽²⁾ = Including GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse and EUPL (among others).
60 | ⁽³⁾ = 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. 61 | -------------------------------------------------------------------------------- /DandelicenceNewestVersion.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1.3, 28th of August 2020 8 | 9 | ——————————————————————————————————————— 10 | 11 | ## Glossary 12 | 13 | * Except where local laws and/or B's licences from §4 state otherwise, redistributions or borrowed content counts as 14 | * * **Unmodified** if it has received 0 changes, 15 | * * **Transformative work** if more than 20% of the lines or 20% of the sentences (whichever is more) have been altered from their original borrowing, 16 | * * **Near-unmodified** if it is somewhere between those two categories. 17 | 18 | For the purposes of section 4, if A believes that their content use has become transformative, A can optionally add a note about it in the 4c template for as long as B does not contest the claim. 19 | 20 | * The British English version of this licence is the official version. All other translations are unofficial. 21 | 22 | * 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. 23 | 24 | ——————————————————————————————————————— 25 | 26 | ## Licence text 27 | 28 | 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: 29 | 30 | 1) Redistributions of (near-)unmodified source code must retain this licence text in unmodified form somewhere inside it. 31 | 32 | 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/skimmingware. Likewise, anyone who modify the source code to add live ransomware/skimmingware that was not originally in the source code, can be held responsible for it. 33 | 34 | 3) The name(s) of the copyright/trademark holder or contributors may not be used to endorse or promote products derived from this software without explicit prior written permission. 35 | 36 | 4) If a project with this licence (A), incorporates (near-)unmodified content from another project (B), then it's mandatory for A's official maintainer(s) 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 placement 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. 37 | 38 | * * 4a. If B's project was licenced with a creditation requirement⁽¹⁾, it is expected that A will add creditation without needing to be told to do so, although the principle of asking about it and expecting good faith applies in this case as well. 39 | * * 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. 40 | * * 4c. A's owners can, through means of 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. 41 | 42 | 5) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 43 | 44 | 6) Transformative versions of the source code can be relicenced into any licence, but will remain subject to §2, §3 and §5. 45 | 46 | * * 6a) If the relicenced source code was previously added to the source code from B, then §4 applies to such content as well. 47 | 48 | 7) 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. 49 | 50 | ——————————————————————————————————————— 51 | 52 | ## Non-mandatory guidelines 53 | 54 | * 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 \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 55 | * It is preferable to write the copyright sign as © instead of (C). 56 | * 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. 57 | 58 | ——————————————————————————————————————— 59 | 60 | ⁽¹⁾ = Including GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA and CC BY-NC-SA (among others).
61 | ⁽²⁾ = Including GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse and EUPL (among others).
62 | ⁽³⁾ = 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. 63 | -------------------------------------------------------------------------------- /DandelicenceV1.4.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1.4, 2nd of December 2021 8 | 9 | ——————————————————————————————————————— 10 | 11 | ## Glossary 12 | 13 | * Except where local laws and/or B's licences from §4 state otherwise, redistributions or borrowed content counts as 14 | * * **Unmodified** if it has received 0 changes, 15 | * * **Transformative work** if more than 20% of the lines or 20% of the sentences (whichever is more) have been altered from their original borrowing, 16 | * * **Near-unmodified** if it is somewhere between those two categories. 17 | 18 | * The British English version of this licence is the official version. All other translations are unofficial. 19 | 20 | * 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. 21 | 22 | ——————————————————————————————————————— 23 | 24 | ## Licence text 25 | 26 | 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: 27 | 28 | 1) Redistributions of (near-)unmodified source code must retain this licence text in unmodified form somewhere inside it, or a URL link to it. 29 | 30 | 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. 31 | 32 | * * 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. 33 | 34 | 3) 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. 35 | 36 | 4) 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. 37 | 38 | * * 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. 39 | * * 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. 40 | * * 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. 41 | 42 | 5) 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. 43 | 44 | 6) Transformative versions of the source code can be relicenced into any licence, but will remain subject to §2, §3 and §5. 45 | 46 | * * 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. 47 | 48 | 7) 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. 49 | 50 | 8) 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. 51 | 52 | ——————————————————————————————————————— 53 | 54 | ## Non-mandatory guidelines 55 | 56 | * 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 \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 57 | * It is preferable to write the copyright sign as © instead of (C). 58 | * 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. 59 | 60 | ——————————————————————————————————————— 61 | 62 | ⁽¹⁾ = Including GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA and CC BY-NC-SA (among others).
63 | ⁽²⁾ = Including GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse and EUPL (among others).
64 | ⁽³⁾ = 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. 65 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1, 10th of July 2019 UTC 8 | 9 | Redistribution and use in source and binary forms, with or without modification, with or without commercial intentions, are permitted provided that the following conditions are met: 10 | 11 | 1) Redistributions of unmodified or near-unmodified source code must retain this very licence in unmodified form somewhere inside it. 12 | 13 | 2) The creator(s) of the original project and source code may not under any possible circumstances be held responsible for damages, incompatibilities, breakage, or unmerchantability. The sole exception is if it can be decidedly proven beyond reasonable doubt that the original unmodified source code contained live ransomware or live skimmingware. Likewise, anyone who modifies the source code to contain live ransomware or live skimmingware that was not originally in the source code, can be held responsible for it. 14 | 15 | 3) Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. 16 | 17 | 4) If a project that is licenced under the Dandelicence (A), incorporates verbatim or near-verbatim content from another project that is licenced under any reasonably open-sourced licence (B), then it is mandatory for the maintainer(s) of A to adhere to creator/licence creditation requests and/or requests to remove the incorporated content, from the owner(s) or substantial contributor(s) of B, as long as it can be reasonably assumed that the requestor really does own or contribute to B. In return, the requestor is expected to assume for at least 14 days after the request has been placed that the maintainer(s) of A will act in good faith, will include the creditation or perform the removal within that timespan, and that reports and DMCA takedowns are to be kept at an absolute minimum for as long as A acts in good faith. 18 | 19 | * * 4a. To make it easier for the creator of A to demonstrate their good faith, creditation for incorporated content should be added as fast as humanly possible without the need for a request from B, if B's content was licenced under either GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA, CC BY-NC-SA, another licence that is strict on creditation, or was from a project that appears to not mention any licences or copyright policies of any sort. Content that is taken from such projects and credited, unless they have been changed enough to count as transformative work, is to be treated as still being licenced under B's licence. 20 | 21 | * * 4b. If it's feasibly possible, the incorporated content from B is to be placed in its own paragraph, and the following template or something similar should be used: *"Below are \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 22 | 23 | * * 4c. Content that was originally incorporated, but which has since been significantly transformed, are exempted from 4a and 4b, but not from 4. 24 | 25 | 5) Should there be incompatible disprecancies between different translations of this licence, then the British English version takes precedence. 26 | 27 | 6) Substantially modified versions of the source code does not require adding this licence to it, and can be relicenced into any licence. However, condition 2, 3, 5, and 6 in the Dandelicence will still apply to how the modified version relates to the source code. 28 | 29 | 7) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 30 | 31 | 8) It is merely optional for the Dandelicence-using project to list copyright details (e.g. name, year) in the licence file. However, it should be made clear in some or another way who the creator of the source code was, for example (but not limited to) through the project's homepage or FAQ page, even if it's just a fictional username. Should you wish to include the copyright details, they are written on the line beneath the version number/date line. It is preferable to use the Unicode character © instead of (C). 32 | 33 | 9) This licence was partially written as a contrast to those licences that shout at the top of lungs in all-caps about non-liability. It is therefore considered bad sport (although non-enforceably so) to change any section of this licence into all-caps. 34 | 35 | 10) The source code that is covered by the licence, and any redistributions of unmodified or near-unmodified source code, shall be accessible in some or another capacity at whichever access price in at least 100 countries worldwide. This is to try to prevent it from e.g. being solely accessible from United States-only streaming services or similarly restricted services. VPN access does not count towards the tally. A "country" is defined as a member state of the United Nations, or alternately the Republic of China, the Sahrawi Arab Democratic Republic's Free Zone, Vatican State, Kosovo, or Northern Cyprus. Should the work not be available in a sufficient amount of countries, any living person may request to the project's maintainer that it be made available in at least 10 more countries within 14 days. 14-day periods may be stacked through successive requests placed 14 or more days after the previous request, until 100 countries have been reached. 36 | -------------------------------------------------------------------------------- /DandelicenceV1.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1, 10th of July 2019 UTC 8 | 9 | Redistribution and use in source and binary forms, with or without modification, with or without commercial intentions, are permitted provided that the following conditions are met: 10 | 11 | 1) Redistributions of unmodified or near-unmodified source code must retain this very licence in unmodified form somewhere inside it. 12 | 13 | 2) The creator(s) of the original project and source code may not under any possible circumstances be held responsible for damages, incompatibilities, breakage, or unmerchantability. The sole exception is if it can be decidedly proven beyond reasonable doubt that the original unmodified source code contained live ransomware or live skimmingware. Likewise, anyone who modifies the source code to contain live ransomware or live skimmingware that was not originally in the source code, can be held responsible for it. 14 | 15 | 3) Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. 16 | 17 | 4) If a project that is licenced under the Dandelicence (A), incorporates verbatim or near-verbatim content from another project that is licenced under any reasonably open-sourced licence (B), then it is mandatory for the maintainer(s) of A to adhere to creator/licence creditation requests and/or requests to remove the incorporated content, from the owner(s) or substantial contributor(s) of B, as long as it can be reasonably assumed that the requestor really does own or contribute to B. In return, the requestor is expected to assume for at least 14 days after the request has been placed that the maintainer(s) of A will act in good faith, will include the creditation or perform the removal within that timespan, and that reports and DMCA takedowns are to be kept at an absolute minimum for as long as A acts in good faith. 18 | 19 | * * 4a. To make it easier for the creator of A to demonstrate their good faith, creditation for incorporated content should be added as fast as humanly possible without the need for a request from B, if B's content was licenced under either GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA, CC BY-NC-SA, another licence that is strict on creditation, or was from a project that appears to not mention any licences or copyright policies of any sort. Content that is taken from such projects and credited, unless they have been changed enough to count as transformative work, is to be treated as still being licenced under B's licence. 20 | 21 | * * 4b. If it's feasibly possible, the incorporated content from B is to be placed in its own paragraph, and the following template or something similar should be used: *"Below are \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 22 | 23 | * * 4c. Content that was originally incorporated, but which has since been significantly transformed, are exempted from 4a and 4b, but not from 4. 24 | 25 | 5) Should there be incompatible disprecancies between different translations of this licence, then the British English version takes precedence. 26 | 27 | 6) Substantially modified versions of the source code does not require adding this licence to it, and can be relicenced into any licence. However, condition 2, 3, 5, and 6 in the Dandelicence will still apply to how the modified version relates to the source code. 28 | 29 | 7) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 30 | 31 | 8) It is merely optional for the Dandelicence-using project to list copyright details (e.g. name, year) in the licence file. However, it should be made clear in some or another way who the creator of the source code was, for example (but not limited to) through the project's homepage or FAQ page, even if it's just a fictional username. Should you wish to include the copyright details, they are written on the line beneath the version number/date line. It is preferable to use the Unicode character © instead of (C). 32 | 33 | 9) This licence was partially written as a contrast to those licences that shout at the top of lungs in all-caps about non-liability. It is therefore considered bad sport (although non-enforceably so) to change any section of this licence into all-caps. 34 | 35 | 10) The source code that is covered by the licence, and any redistributions of unmodified or near-unmodified source code, shall be accessible in some or another capacity at whichever access price in at least 100 countries worldwide. This is to try to prevent it from e.g. being solely accessible from United States-only streaming services or similarly restricted services. VPN access does not count towards the tally. A "country" is defined as a member state of the United Nations, or alternately the Republic of China, the Sahrawi Arab Democratic Republic's Free Zone, Vatican State, Kosovo, or Northern Cyprus. Should the work not be available in a sufficient amount of countries, any living person may request to the project's maintainer that it be made available in at least 10 more countries within 14 days. 14-day periods may be stacked through successive requests placed 14 or more days after the previous request, until 100 countries have been reached. 36 | -------------------------------------------------------------------------------- /DandelicenceV1.2.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1.2, 11th of January UTC 8 | 9 | Redistribution and use in source and binary forms, with or without modification, with or without commercial intentions, are permitted provided that the following conditions are met: 10 | 11 | 1) Redistributions of unmodified or near-unmodified source code must retain this licence text in unmodified form somewhere inside it. 12 | 13 | 2) The creator(s) of the original project/code may under no circumstances be held responsible for damages, incompatibilities, breakage or unmerchantability, except if it's proven beyond reasonable doubt that the unmodified source code contained live ransomware/skimmingware. Likewise, anyone who modify the source code to contain live ransomware/skimmingware that was not originally in the source code, can be held responsible for it. 14 | 15 | 3) The name(s) of the copyright/trademark holder or contributors may not be used to endorse or promote products derived from this software without explicit prior written permission. 16 | 17 | 4) If a project that is licenced under the Dandelicence (A), incorporates (near-)unmodified content from another project that is licenced under any reasonably open-sourced licence (B), then it's mandatory for the maintainer(s) of A to adhere to requests for creator/licence creditation and/or to remove the incorporated content, from the owner(s)/maintainer(s) of B, as long as it can be reasonably assumed that the requestor really does own/maintain B. In return, the requestor is expected to assume for ≥14 days after the request has been placed that the maintainer(s) of A will act in good faith, will include the creditation or perform the removal within that timespan, and that reports and DMCA claims are to be kept at an absolute minimum for as long as A acts in good faith. 18 | 19 | * * 4a. To make it easier for A's creator to display their good faith, creditation for incorporated content should be added as fast as possible without needing a request from B, if B's content was licenced with a creditation requirement⁽¹⁾, or was from a project that appears to not mention any licences or copyright policies of any sort. 20 | * * 4b. If the content was taken from a project whose licence had a share-alike clause⁽²⁾, and which has not been sufficiently transformed to count as transformative work, it will be treated as still being licenced under B's licence. Otherwise, it will be treated as being under the Dandelicence. 21 | * * 4c. 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 \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 22 | * * 4d. The owner(s) of A can choose to donate and relicence any portion of his/her own code to any other project of any kind even if it has not become transformative, unless it's subject to 4a or 4b. 23 | * * 4e. Content that was originally incorporated, but which has since become transformative, are exempted from 4a, 4b and 4c, but not from 4. 24 | 25 | 5) The British English version of this licence is the official version. All other translations are unofficial. 26 | 27 | 6) Transformative versions of the source code do not require retaining this licence file, and can be relicenced into any licence. However, condition 2, 3, 5, and 6 in the Dandelicence will still apply to how the transformative version relates to the source code. 28 | 29 | 7) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 30 | 31 | 8) It is merely optional for the Dandelicence-using project to list copyright details (e.g. name, year) in the licence file, but it should be made clear in some way who the creator of the source code was, for example (but not limited to) through the project's homepage or FAQ page, even if it's just a fictional username. It is preferable to use © instead of (C). 32 | 33 | 9) Any (near-)unmodified redistributions of the source code, shall be accessible in some form at whichever monetary price in ≥100 countries worldwide. This is to prevent it from e.g. only being accessible on USA-only streaming services or similarly restricted services. VPN access does not count towards the tally. 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. Should the work not be available in enough countries, any living person may request the project's maintainer to make it available in at least 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. 34 | 35 | 10) Except where local laws and/or B's licences from 4b 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, and «Near-unmodified» if it is somewhere between those two categories. For the purposes of section 4, if A believes that their content use has become transformative, A can optionally add a note about it in the 4c template for as long as B does not contest the claim. 36 | 37 | ——————————————————————————————————————— 38 | 39 | ⁽¹⁾ = Including GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA and CC BY-NC-SA (among others).
40 | ⁽²⁾ = Including GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse and EUPL (among others). 41 | -------------------------------------------------------------------------------- /DandelicenceV1.1.md: -------------------------------------------------------------------------------- 1 | # Dandelicence 2 | 3 | ## A licence that works on good faith, because why can't we all just be friends instead of bickering? 4 | 5 | ### Dandelicence's homepage: https://github.com/DandelionSprout/Dandelicence 6 | 7 | ### Version 1.1, 3rd of September 2019 UTC 8 | 9 | Redistribution and use in source and binary forms, with or without modification, with or without commercial intentions, are permitted provided that the following conditions are met: 10 | 11 | 1) Redistributions of unmodified or near-unmodified source code must retain this very licence in unmodified form somewhere inside it. 12 | 13 | 2) The creator(s) of the original project and source code may not under any possible circumstances be held responsible for damages, incompatibilities, breakage, or unmerchantability. The sole exception is if it can be decidedly proven beyond reasonable doubt that the original unmodified source code contained live ransomware or live skimmingware. Likewise, anyone who modifies the source code to contain live ransomware or live skimmingware that was not originally in the source code, can be held responsible for it. 14 | 15 | 3) Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. 16 | 17 | 4) If a project that is licenced under the Dandelicence (A), incorporates unmodified or near-unmodified content from another project that is licenced under any reasonably open-sourced licence (B), then it is mandatory for the maintainer(s) of A to adhere to creator/licence creditation requests and/or requests to remove the incorporated content, from the owner(s) or substantial contributor(s) of B, as long as it can be reasonably assumed that the requestor really does own or contribute to B. In return, the requestor is expected to assume for at least 14 days after the request has been placed that the maintainer(s) of A will act in good faith, will include the creditation or perform the removal within that timespan, and that reports and DMCA takedowns are to be kept at an absolute minimum for as long as A acts in good faith. 18 | 19 | * * 4a. To make it easier for the creator of A to demonstrate their good faith, creditation for incorporated content should be added as fast as humanly possible without the need for a request from B, if B's content was licenced under either GPLv3, GPLv2, MPLv2, CC BY, CC BY-NC, CC BY-SA, CC BY-NC-SA, another licence that is strict on creditation, or was from a project that appears to not mention any licences or copyright policies of any sort. 20 | 21 | * * 4b. If the content was taken from a project that used a licence with a share-alike clause, incl. (but not limited to) GPLv3, GPLv2, CC BY-SA, CC BY-NC-SA, Eclipse, and EUPL, and which has not been sufficiently transformed to count as transformative work, will be treated as still being licenced under B's licence. Otherwise, it will be treated as being under the Dandelicence. 22 | 23 | * * 4c. If it's feasibly possible, the incorporated content from B is to be placed in its own paragraph, and the following template or something similar should be used: *"Below are \ that [I/we] borrowed from \, which is maintained by \ at \, and which is licenced under \."* 24 | 25 | * * 4d. Content that was originally incorporated, but which has since been significantly transformed, are exempted from 4a, 4b, and 4c, but not from 4. 26 | 27 | 5) Should there be incompatible disprecancies between different translations of this licence, then the British English version takes precedence. 28 | 29 | 6) Substantially modified versions of the source code does not require adding this licence to it, and can be relicenced into any licence. However, condition 2, 3, 5, and 6 in the Dandelicence will still apply to how the modified version relates to the source code. 30 | 31 | 7) If a different licence is mentioned and used as the sole licence for an individual file in a multi-file project (e.g. a Git), then the file's licence takes sole precedence over the Dandelicence. 32 | 33 | 8) It is merely optional for the Dandelicence-using project to list copyright details (e.g. name, year) in the licence file. However, it should be made clear in some or another way who the creator of the source code was, for example (but not limited to) through the project's homepage or FAQ page, even if it's just a fictional username. Should you wish to include the copyright details, they are written on the line beneath the version number/date line. It is preferable to use the Unicode character © instead of (C). 34 | 35 | 9) This licence was partially written as a contrast to those licences that yell at the top of lungs in all-caps about non-liability. It is therefore considered bad sport (although non-enforceably so) to change any section of this licence into all-caps. 36 | 37 | 10) The source code that is covered by the licence, and any redistributions of unmodified or near-unmodified source code, shall be accessible in some or another capacity at whichever access price in at least 100 countries worldwide. This is to try to prevent it from e.g. being solely accessible from United States-only streaming services or similarly restricted services. VPN access does not count towards the tally. A "country" is defined as a member state of the United Nations, or alternately the Republic of China, the Sahrawi Arab Democratic Republic's Free Zone, Vatican State, Kosovo, or Northern Cyprus. Should the work not be available in a sufficient amount of countries, any living person may request to the project's maintainer that it be made available in at least 10 more countries within 14 days. 14-day periods may be stacked through successive requests placed 14 or more days after the previous request was placed, until 100 countries have been reached. 38 | 39 | 11) Except where local laws and/or B's licences from 4b explicitly state otherwise, redistributions or borrowed content counts as «unmodified» if it has received 0 changes, «transformative work»/«substantially modified» if more than 20% of the lines or 20% of the sentences (whichever is more) have been altered from their original borrowing, and «near-unmodified» if it is somewhere between those two categories. For the purposes of section 4, if the project believes that the content has become transformative, A can optionally add a note about it in the 4c template for as long as B does not contest the claim. 40 | --------------------------------------------------------------------------------