diff options
| author | Bryan Bishop <kanzure@gmail.com> | 2016-01-01 11:06:47 -0600 |
|---|---|---|
| committer | Bryan Bishop <kanzure@gmail.com> | 2016-01-01 11:07:58 -0600 |
| commit | c1261ac6473040ca6079fe4f9301102d0e518446 (patch) | |
| tree | 83e36514ed78dcdd43d488e42c0adc12e3991775 /bip-0001.mediawiki | |
| parent | bada79afddc7cd70f7ad36d163aa7110964e03ee (diff) | |
BIP1: clarify "issue tracker" statement
This switches from specifying "Bitcoin issue tracker" to specifying
"Bitcoin Core issue tracker". Other issue trackers are useful for other
client development activities, although this does not seem necessary to
mention.
Diffstat (limited to 'bip-0001.mediawiki')
| -rw-r--r-- | bip-0001.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0001.mediawiki b/bip-0001.mediawiki index ad96dce..9703409 100644 --- a/bip-0001.mediawiki +++ b/bip-0001.mediawiki @@ -28,7 +28,7 @@ The BIP editors assign BIP numbers and change their status. Please send all BIP- 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. +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 Core development work flow with a patch submission to the Bitcoin Core 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. |