public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Splitting BIPs
Date: Mon, 24 Aug 2015 23:25:54 +0000	[thread overview]
Message-ID: <CABr1YTc=aXS4V8gO3cmKrrinFv5BO-3Dpo+TRmSWcd-ed=JdLA@mail.gmail.com> (raw)
In-Reply-To: <CABr1YTcoWesaBJaT--bbUUN-c2phc-=3ieWT7vVDNPGg0iHH2g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

Also, the current "type" attribute needs modification. There are different
degrees of "standard". Just because a lot of people do X doesn't need to
mean that doing X is "officially" endorsed by any other devs. At most
levels below 1, disagreements might be entirely tolerable for many things.

On Mon, Aug 24, 2015, 2:06 PM Eric Lombrozo <elombrozo@gmail.com> wrote:

>
> 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: 1391 bytes --]

  reply	other threads:[~2015-08-24 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 21:01 [bitcoin-dev] Splitting BIPs Eric Lombrozo
2015-08-24 23:25 ` Eric Lombrozo [this message]
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='CABr1YTc=aXS4V8gO3cmKrrinFv5BO-3Dpo+TRmSWcd-ed=JdLA@mail.gmail.com' \
    --to=elombrozo@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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