-
Notifications
You must be signed in to change notification settings - Fork 2
Update the BIP Process #2
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.
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
Changes from 101 commits
bbf7c51
d1d49e9
0bd8036
4643b16
74e691d
e600c49
3f990ed
97744be
9426c2e
613f1ff
59c9f12
0214659
4ba4e47
f076ade
ba40daa
affea61
f23cf9d
556e2d4
598848b
96df5fe
ca32adb
5017847
ddfe787
88e68c0
2ffcb8d
851858c
10e23f5
7ce39f9
896b4ec
3916387
5d50bb1
2d2d4f1
0296846
13b64e3
4a4b640
33ed167
02c9717
afb5b9c
56ebea0
0446c5f
7727100
3ae7a3b
5b0f797
8168178
c30ec6a
b67dda6
e90f180
a677b0d
b09ca95
7d2b81a
a6b5e65
7f90aa5
99646f1
f2b1a6c
6ad4172
a676839
d6780d7
4b63d36
374ab86
8194030
d198deb
e4b4c7c
e4a59ab
d3d0e7e
d5a3e91
564c38d
df1e84a
57d8c08
f5e5414
41cd06a
dea58f3
452c05c
b35e02f
ac95ca2
0caa8aa
6b184dc
eea8df8
f667bf0
8458dfd
9e804df
e07f38e
94cebfd
fd423a8
3504b74
4ba4899
1da9d40
3c47a01
85c4fe5
e987582
1a648aa
36e716f
27e174c
a4c8b23
b10f117
c41b2ee
311b3d0
e158b95
201ffd2
c1e27bb
b795d91
2cb5a90
2f1cd93
e2378f3
d226be7
f2c1afb
52304cd
78b6b44
cf2e14f
81a2310
b54223d
7650ff3
4f99f38
3bdc703
5113902
7a359f7
985f976
2cc9ff6
37e8488
c949ec6
1bb2af3
649c80d
0b6ec15
acc7492
27c46c0
fc60b69
d48c894
bb252f6
2e115e5
d857e80
c6ad72e
1804ea9
d7fd3f7
9bf78fe
f16907c
0638dcb
d4b8825
5fdffc0
c97044e
7554714
7c4a9e7
74627b2
32b1fc4
ebe9f54
791260f
da24630
e0c3515
f4e5881
f839c53
f08d079
2de85d2
313c967
299bfd1
daa559f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,10 +1,6 @@ | ||||||
| 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 meeting the editorial criteria, a BIP Editor will assign a number, and it will be published here. Authors do <em>not</em> assign a number to their own proposal. Please see <a href="bip-update-process.md">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 of 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 approving BIPs, and try not to be too involved in decision making on behalf of the community. Beyond the formal criteria, evaluation of the proposals is left to the audience of the repository. The exception are rare cases when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will be preferred. Authors proposing changes should consider that ultimately consent rests with the Bitcoin users (see also: [https://en.bitcoin.it/wiki/Economic_majority economic majority]). | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Maybe you can expand on the meaning of "the conservative option." I think that means the BIP should be assigned a number, but perhaps make that more explicit.
Owner
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The phrase "conservative option" was there before. I had assumed that it meant to decline merging, but actually in the context of being liberal with approval, your read does sound more plausible. I’m leaving this the same for the moment, because I want to mull over whether this should be rephrased and how.
Owner
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I’ve deferred changes to the README to a separate PR #3 as I came to the conclusion that the README should only be updated when this proposal is adopted rather than when it is merged to the repository. I adopted your proposed changes, though. I have made an attempt to clarify the "conservative option": -community consensus, or that it is about to be adopted. The BIP Editors are expected to be liberal with approving BIPs
-and try not to be too involved in decision-making on behalf of the community. Beyond the formal criteria, evaluation of
-the proposals is left to the audience of the repository. The exceptions are rare cases when a decision is contentious
-and cannot be agreed upon. In those cases, the conservative option will be preferred. Authors proposing changes should
-consider that ultimately, consent rests with the Bitcoin users (see also: [https://en.bitcoin.it/wiki/Economic_majority
-economic majority]).
+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 | ||||||
|
|
||||||
Uh oh!
There was an error while loading. Please reload this page.