From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] BIP process
Date: Tue, 18 Oct 2011 15:17:43 -0400 [thread overview]
Message-ID: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com> (raw)
Amir started the "get more formal about changes to bitcoin" ball
rolling by creating BIP 0001, starting from the Python "PEP" /
BitTorrent "BEP" processes:
https://en.bitcoin.it/w/index.php?title=BIP_0001
The idea is to use BIPs for changes that may or will affect every
bitcoin implementation (not to use them for proposed changes to one
particular implementation).
I'd like to propose some minor changes to the process:
• I propose that BIPs be wiki pages, with a social convention that the
Author gets final word if any editing wars break out.
• If he's willing, I propose that Amir take the role of BIP editor.
• I think bitcoin is still too small to have a specialized
"bitcoin-ideas" mailing list; I propose that new potential BIPs be
discussed either here or on the bitcoin-dev mailing list.
What do y'all think?
--
--
Gavin Andresen
next reply other threads:[~2011-10-18 19:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 19:17 Gavin Andresen [this message]
2011-10-18 21:26 ` [Bitcoin-development] BIP process Nils Schneider
2011-10-20 5:02 ` Alex Waters
2011-10-20 11:27 ` Christian Decker
2014-10-15 8:29 Wladimir
2014-10-15 9:22 ` Gregory Maxwell
2014-10-15 9:36 ` Wladimir
2014-10-15 18:58 ` Cory Fields
2014-10-16 7:50 ` Thomas Zander
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46 ` Mike Hearn
2014-10-15 15:54 ` Adam Back
2014-10-15 16:47 ` Peter Todd
2014-10-15 18:13 ` Mike Hearn
2014-10-16 7:38 ` Thomas Zander
2014-10-16 14:19 ` Oliver Egginger
2014-10-15 19:00 ` Btc Drak
2014-10-15 19:40 ` Peter Todd
2014-10-16 4:41 ` Luke Dashjr
2014-10-19 7:17 ` xor
2014-10-19 9:42 ` Btc Drak
2014-10-19 9:49 ` Wladimir
2014-10-19 18:58 ` Thomas Zander
2014-10-20 0:33 ` odinn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox