diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-06-22 09:30:31 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-06-22 09:30:54 +0200 |
| commit | 9ea8012e687a8465a72c610fa4dfcdea40aa454f (patch) | |
| tree | 607c159532cfd9683e68f2531ba8dae372a75f51 | |
| parent | 8defdc87d18a8f36d426ed40145441d271f18ae4 (diff) | |
| download | bips-9ea8012e687a8465a72c610fa4dfcdea40aa454f.tar.xz | |
bip-0001: Mailing list move
| -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 5c8a544..dda1d37 100644 --- a/bip-0001.mediawiki +++ b/bip-0001.mediawiki @@ -27,7 +27,7 @@ The BIP editors assign BIP numbers and change their status. Please send all BIP- 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 [http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development bitcoin-development@lists.sourceforge.net] 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. +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. Vetting an idea publicly before going as far as writing a BIP is meant to save the potential author 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. |