bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-07-21 12:58:14 +00:00
Code Issues Releases Wiki Activity

bip3: Don't require omitting unacceptable licenses

Browse Source 
I think that requirement is not helpful. I don't think hat including
additional licenses will be overwhelming to the reader. If anything, it
will obfuscates the actual licensing conditions. (Anyway, this should be
super rare.)
This commit is contained in:
Tim Ruffing 2025-07-09 09:12:49 +02:00
parent d01e941188
commit 3de6ed6dc0
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bip-0003.md
View File

@ -147,7 +147,7 @@ appear in the following order. Headers marked with "\*" are optional. All other
Authors header. See the [BIP Ownership](#bip-ownership) section above.
* Status — The stage of the workflow of the proposal. See the [Workflow](#workflow) section below.
* Type — See the [BIP Types](#bip-types) section below for a description of the three BIP types.
* License and License-Code — These headers specify SPDX License Expressions describing the acceptable licenses under which the
* License and License-Code — These headers specify SPDX License Expressions describing the licenses under which the
BIP and corresponding code are available. See the [BIP Licensing](#bip-licensing) section below.
* Discussion — The Discussion header points the audience to relevant discussions of the BIP, e.g., the mailing list
thread in which the idea for the BIP was discussed, a thread where a new version of the BIP was presented, or relevant
@ -430,8 +430,7 @@ In all cases, details of the licensing terms must be provided in the Copyright s
Each new BIP must be made available under at least one acceptable license as listed below. BIPs are not required to be
*exclusively* licensed under approved terms, and may also be licensed under unacceptable licenses *in addition to* at
least one acceptable license. In this case, only the acceptable license(s) should be specified in the License and
License-Code headers.
least one acceptable license.
In other words, a new BIP must specify an SPDX License Expression that is either "L" or equivalent to "L OR E" for some
acceptable license L from the following list and another SPDX License Expression E.
@ -448,8 +447,7 @@ acceptable license L from the following list and another SPDX License Expression
#### Not Acceptable Licenses
All licenses not explicitly included in the above lists are not acceptable terms for a Bitcoin Improvement Proposal.
However, BIPs predating this proposal were allowed under other terms, and should use these identifiers
when no other license is granted:
However, BIPs predating this proposal were allowed under other terms, and should use these identifiers:
* LicenseRef-PD: Placed into the public domain
* OPUBL-1.0: [Open Publication License, version 1.0](http://opencontent.org/openpub/)