From: Eric Lombrozo <elombrozo@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Splitting BIPs
Date: Mon, 24 Aug 2015 21:01:26 +0000 [thread overview]
Message-ID: <CABr1YTcoWesaBJaT--bbUUN-c2phc-=3ieWT7vVDNPGg0iHH2g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Seems like a lot of effort and goodwill is being wasted on contention over
things we don't really need to agree upon. In order to help us better
prioritize, I propose adding an extra attribute to BIPs indicating their
"level" which is split into five as follows:
1. Consensus (hard/soft fork)
2. Peer Services
3. RPC
4. Implementations
5. Applications
I posted an example of what such a table might look like here: http://
blockhawk.net/bitcoin-dev/bipwiki.html
If other folks also think this is a good idea I'll start working on a BIP
draft for this.
[-- Attachment #2: Type: text/html, Size: 727 bytes --]
next reply other threads:[~2015-08-24 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 21:01 Eric Lombrozo [this message]
2015-08-24 23:25 ` Eric Lombrozo
2015-08-27 20:51 ` Eric Lombrozo
2015-08-29 23:37 ` Jorge Timón
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='CABr1YTcoWesaBJaT--bbUUN-c2phc-=3ieWT7vVDNPGg0iHH2g@mail.gmail.com' \
--to=elombrozo@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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