public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Andy Chase <theandychase@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [BIP/Draft] BIP Acceptance Process
Date: Fri, 4 Sep 2015 21:45:32 +0000	[thread overview]
Message-ID: <201509042145.34410.luke@dashjr.org> (raw)
In-Reply-To: <CAAxp-m8pgvHqUcmjCt6W5uscgb9ErtiTHdR0-nKU6OVdCE7rXA@mail.gmail.com>

On Friday, September 04, 2015 9:36:42 PM Andy Chase wrote:
> I understand your concerns. What kinds of changes do you think should go
> through a process like this? Just hard forks?

The process loses meaning if it doesn't reflect reality. So only hardforks 
should go through the hardfork process; only softforks through the softfork 
process; etc. Trying to make one-size-fits-all just means de facto accepted 
BIPs wouldn't be recognised as such because nobody cares to meet the higher 
requirements.

Luke


  reply	other threads:[~2015-09-04 21:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  0:30 [bitcoin-dev] [BIP/Draft] BIP Acceptance Process Andy Chase
2015-09-04  0:41 ` Luke Dashjr
2015-09-04  0:52   ` Andy Chase
2015-09-04  0:43 ` Bryan Bishop
2015-09-04  4:40   ` Andy Chase
2015-09-04 19:20     ` Btc Drak
2015-09-04 20:13       ` Andy Chase
2015-09-04 20:31         ` Peter Todd
2015-09-04 20:42           ` Martin Becze
2015-09-04 21:05           ` Milly Bitcoin
2015-09-04 21:01         ` Luke Dashjr
2015-09-04 21:36           ` Andy Chase
2015-09-04 21:45             ` Luke Dashjr [this message]
2015-09-05 21:19               ` Andy Chase
     [not found]                 ` <CAHv+tb5ksyZKp5jLvmzFbD2vBOUrWn6ps80ODECVRqYj8m=PZA@mail.gmail.com>
2015-09-06 20:44                   ` Andy Chase
2016-01-19  2:12                 ` Luke Dashjr
2016-01-19  4:23                   ` Andy Chase
2016-01-19  6:07                   ` Dave Scotese
2015-09-07 19:37         ` Btc Drak
2015-09-10  1:21           ` Andy Chase
2015-09-12 23:50             ` Andy Chase

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=201509042145.34410.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=theandychase@gmail.com \
    /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