summaryrefslogtreecommitdiff
path: root/bip-0001.mediawiki
diff options
context:
space:
mode:
authorAmos Bairn <Eylrid@Gmail.com>2015-06-29 15:24:12 -0700
committerAmos Bairn <Eylrid@Gmail.com>2015-06-29 15:24:12 -0700
commit0bac1dcc70821262fbc62171880e3c38e5a0506f (patch)
treefad0bf1d062845e7103e69fc514387890906ec84 /bip-0001.mediawiki
parent11d8610907df70cc1cfef760af81fdaf9913fff8 (diff)
Update Missed Mailing List Link
A second link to the mailing list was missed and left pointing to the old list.
Diffstat (limited to 'bip-0001.mediawiki')
-rw-r--r--bip-0001.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0001.mediawiki b/bip-0001.mediawiki
index dda1d37..c18ebd3 100644
--- a/bip-0001.mediawiki
+++ b/bip-0001.mediawiki
@@ -31,7 +31,7 @@ Each BIP must have a champion -- someone who writes the BIP using the style and
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.
-Once the champion has asked the Bitcoin community as to whether an idea has any chance of acceptance, a draft BIP should be presented to [http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development bitcoin-development@lists.sourceforge.net]. This gives the author a chance to flesh out the draft BIP to make properly formatted, of high quality, and to address initial concerns about the proposal.
+Once the champion has asked the Bitcoin community as to whether an idea has any chance of acceptance, a draft BIP should be presented to [https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev bitcoin-dev@lists.linuxfoundation.org]. This gives the author a chance to flesh out the draft BIP to make properly formatted, of high quality, and to address initial concerns about the proposal.
Following a discussion, the proposal should be sent to the Bitcoin-dev list and the BIP editor with the draft BIP. This draft must be written in BIP style as described below, else it will be sent back without further regard until proper formatting rules are followed.