public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@jtimon•cc>
To: Eric Lombrozo <elombrozo@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Splitting BIPs
Date: Sun, 30 Aug 2015 01:37:05 +0200	[thread overview]
Message-ID: <CABm2gDqXByotyZDWL_i7amrhTN_ZwX5X6rpQdpgq-81gTi7B8w@mail.gmail.com> (raw)
In-Reply-To: <CABr1YTffo1m6U0DsT1vvoKzcLsnufUnwA8Lo6ipVuhjyoqjMEA@mail.gmail.com>

Concept ACK. As suggested in the other thread, maybe it is worth to
start a new BIP draft for this?


On Thu, Aug 27, 2015 at 10:51 PM, Eric Lombrozo via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> I posted a new draft of the proposal:
> http://blockhawk.net/bitcoin-dev/bipwiki.html
>
> The subsections still need to be fleshed out a bit more. I'd love any
> comments or suggestions.
>
>
> On Mon, Aug 24, 2015, 4:30 PM Eric Lombrozo <elombrozo@gmail•com> wrote:
>>
>> 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.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


      reply	other threads:[~2015-08-29 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 21:01 Eric Lombrozo
2015-08-24 23:25 ` Eric Lombrozo
2015-08-27 20:51   ` Eric Lombrozo
2015-08-29 23:37     ` Jorge Timón [this message]

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=CABm2gDqXByotyZDWL_i7amrhTN_ZwX5X6rpQdpgq-81gTi7B8w@mail.gmail.com \
    --to=jtimon@jtimon$(echo .)cc \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=elombrozo@gmail$(echo .)com \
    /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