Skip to content

Update README to match new BIP process #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
murchandamus wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update README to match new BIP process #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
976c1dd
Update README to match new BIP process
murchandamus Sep 20, 2024
4bf9c1d
Err on merging high-quality proposals
murchandamus Sep 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 13 additions & 6 deletions README.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,17 @@
People wishing to submit BIPs, first should propose their idea or document to the [https://groups.google.com/g/bitcoindev bitcoindev@googlegroups.com] mailing list (do <em>not</em> assign a number - read <a href="bip-0002.mediawiki">BIP 2</a> for the full process). After discussion, please open a PR. After copy-editing and acceptance, it will be published here.
People wishing to submit BIPs should first describe their idea to the [https://groups.google.com/g/bitcoindev
bitcoindev@googlegroups.com] mailing list. Please open a pull request to this repository only when substantial progress
on the draft has been made, preferably when the draft is nearing completion. After a proposal meets the editorial
criteria, a BIP Editor will assign a number to it, and publish the proposal by merging the pull request to the
repository. Authors do <em>not</em> assign a number to their own proposal. Please see <a
href="bip-update-process.md">tk: BIP Update Process</a> for the full process.

We are fairly liberal with approving BIPs, and try not to be too involved in decision making on behalf of the community. The exception is in very rare cases of dispute resolution when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will always be preferred.

Having a BIP here does not make it a formally accepted standard until its status becomes Final or Active.

Those proposing changes should consider that ultimately consent may rest with the consensus of the Bitcoin users (see also: [https://en.bitcoin.it/wiki/Economic_majority economic majority]).
The BIPs repository serves as a publication medium and archive. Having a BIP published here indicates that the proposal
is in scope and has met other formal criteria for this repository, but does not indicate that it is a good idea, has
community consensus, or that it is about to be adopted. The BIP Editors are expected to be liberal with accepting BIPs
and not to be too involved in decision-making on behalf of the community. Beyond the formal criteria, evaluation of
proposals is left to the audience of the repository. When a proposal is controversial, but deemed high-quality and in
scope, the BIP Editors shall err on the side of merging it. Ultimately, consent and adoption rests with the Bitcoin
users (see also: [https://en.bitcoin.it/wiki/Economic_majority economic majority]).

{| class="wikitable sortable" style="width: auto; text-align: center; font-size: smaller; table-layout: fixed;"
!Number
Expand Down