diff options
| author | Luke Dashjr <luke-jr+git@utopios.org> | 2016-09-24 03:24:28 +0000 |
|---|---|---|
| committer | Luke Dashjr <luke-jr+git@utopios.org> | 2016-09-24 06:27:07 +0000 |
| commit | deb036798acc61023636bae1886718e3386d4efb (patch) | |
| tree | 9fbed9cd4ca789140e16d19be5ace1100bb2d269 /bip-0002.mediawiki | |
| parent | f1ed5afd1fa4e4ea12c81883947c45bb18aaeab2 (diff) | |
| download | bips-deb036798acc61023636bae1886718e3386d4efb.tar.xz | |
bip-0002: Drop BitcoinTalk recommendation
Diffstat (limited to 'bip-0002.mediawiki')
| -rw-r--r-- | bip-0002.mediawiki | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/bip-0002.mediawiki b/bip-0002.mediawiki index 3252d77..59b6af0 100644 --- a/bip-0002.mediawiki +++ b/bip-0002.mediawiki @@ -24,7 +24,8 @@ This BIP is dual-licensed under the Open Publication License and BSD 2-clause li ==BIP workflow== -The BIP process begins with a new idea for Bitcoin. Each potential 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@lists.linuxfoundation.org] 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. +The BIP process begins with a new idea for Bitcoin. Each potential 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@lists.linuxfoundation.org] mailing list is the best way to go about this. Vetting an idea publicly before going as far as writing a BIP is meant to save both the potential author and the wider community time. Many ideas have been brought forward for changing Bitcoin that have been rejected for various reasons. Asking the Bitcoin community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Bitcoin is used. Small enhancements or patches often don't need standardisation between multiple projects; these don't need a BIP and should be injected into the relevant Bitcoin development work flow with a patch submission to the applicable Bitcoin issue tracker. |