diff options
| author | BtcDrak <btcdrak@gmail.com> | 2015-09-08 00:20:16 +0100 |
|---|---|---|
| committer | BtcDrak <btcdrak@gmail.com> | 2015-10-21 05:57:12 +0100 |
| commit | aecb84f38daf6c9c3ab5b1e87bddb3a556460812 (patch) | |
| tree | a2ee538384c6a9a90fba69cd16796c76075900dd /bip-0001.mediawiki | |
| parent | a409100854f52454b0ba30f98f8f5e585695ec0e (diff) | |
Simplify clarifications
Diffstat (limited to 'bip-0001.mediawiki')
| -rw-r--r-- | bip-0001.mediawiki | 10 |
1 files changed, 7 insertions, 3 deletions
diff --git a/bip-0001.mediawiki b/bip-0001.mediawiki index c18ebd3..9af43bc 100644 --- a/bip-0001.mediawiki +++ b/bip-0001.mediawiki @@ -25,6 +25,8 @@ There are three kinds of BIP: The BIP editors assign BIP numbers and change their status. Please send all BIP-related email to the BIP editor, which is listed under [[#BIP_Editors|BIP Editors]] below. Also see [[#BIP_Editor_Responsibilities__Workflow|BIP Editor Responsibilities & Workflow]]. +Authors MUST NOT self assign numbers, but should use an alias such as "bip-johndoe-infinitebitcoins" which includes the author's name/nick and the BIP subject. + The BIP process begins with a new idea for Bitcoin. It is highly recommended that a single BIP contain a single key proposal or new idea. Small enhancements or patches often don't need a BIP and can be injected into the Bitcoin development work flow with a patch submission to the Bitcoin issue tracker. The more focused the BIP, the more successful it tends to be. The BIP editor reserves the right to reject BIP proposals if they appear too unfocused or too broad. If in doubt, split your BIP into several well-focused ones. Each BIP must have a champion -- someone who writes the BIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The BIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is BIP-able. Posting to the [https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev bitcoin-dev] mailing list (and maybe the [https://bitcointalk.org/index.php?board=6.0 Development&Technical Discussion] forum) is the best way to go about this. @@ -155,11 +157,13 @@ For each new BIP that comes in an editor does the following: If the BIP isn't ready, the editor will send it back to the author for revision, with specific instructions. -Once the BIP is ready for the repository, the BIP editor will: +Once the BIP is ready for the repository it should be submitted as a "pull request" to the [https://github.com/bitcoin/bips bitcoin/bips] repository on GitHub where it may get further feedback. + +The BIP editor will: -* Assign a BIP number (almost always just the next available number, but sometimes it's a special/joke number, like 666 or 3141). +* Assign a BIP number (almost always just the next available number, but sometimes it's a special/joke number, like 666 or 3141) in the pull request comments. -* Add the BIP to the [https://github.com/bitcoin/bips bitcoin/bips] repository on GitHub. +* Merge the pull request when the author is ready (allowing some time for further peer review). * List the BIP in [[README.mediawiki]] |