Skip to content

Commit 7aa54dd

Browse files
bip3: Change License example to CC0-1.0 OR MIT
The actual reason why I suggest this is that I think that's a great default choice for a new BIP, so it's a perfect example. CC0-1.0 is a great liberal choice for the BIP document (and test vectors etc.), and MIT is the common choice for code in our ecosystem. Putting both BIP and code under the "OR" avoids any confusion about which part is licensed under which terms and also avoids any hassle when reorganizing, e.g., when moving code out of the BIP Markdown file to a separate file etc. But I don't want this PR to recommend a license, so let me sell this change as an editorial change to an example, which is warranted because the MIT is much more known than FSFAP, in particular in this ecosystem.
1 parent 0cc4d26 commit 7aa54dd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

bip-0003.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -395,10 +395,10 @@ Copyright section, possibly providing further details on licensing.
395395

396396
For example, a preamble might include the following License header:
397397

398-
License: CC0-1.0 OR FSFAP
398+
License: CC0-1.0 OR MIT
399399

400400
In this case, the BIP (including all auxiliary files) is made available under the terms of both Creative Commons CC0 1.0 Universal as well as the
401-
FSF All Permissive License, and anyone may modify and redistribute it provided they comply with the terms of
401+
MIT License, and anyone may modify and redistribute it provided they comply with the terms of
402402
*either* license, at their option. In other words, the license list is an "OR choice", not an "AND also" requirement. See the [SPDX
403403
documentation](https://spdx.dev/ids/) and the [SPDX License List](https://spdx.org/licenses/) for further details.
404404

0 commit comments

Comments
 (0)