public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: Mark Friedenbach <mark@friedenbach.org>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
	Gavin Andresen <gavin@bitcoinfoundation.org>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers
Date: Thu, 18 Jun 2015 14:58:06 -0700	[thread overview]
Message-ID: <CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com> (raw)
In-Reply-To: <CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>

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

Is that a forward-looking position?  It does not seem so.

The whole point is getting out in front of the need, to prevent significant
negative impact to users when blocks are consistently full.

To do that, you need to (a) plan forward, in order to (b) set a hard fork
date in the future.

"We don't see a need today" is therefore useless, because when you do reach
X day when need is apparent, the best solution then becomes an immediate
fork for which the network and markets are not prepared.

Failing to resolve the block size issue soon will simply result in most
businesses assuming relevant Bitcoin Core standards process is failing, and
proceed with the Bitcoin-XT fork.

As I've said on IRC, the "do nothing, for now" position is untenable.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/

[-- Attachment #2: Type: text/html, Size: 1170 bytes --]

  reply	other threads:[~2015-06-18 21:58 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18  8:54 [Bitcoin-development] Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers odinn
2015-06-18 10:00 ` Mike Hearn
2015-06-18 11:14   ` Wladimir J. van der Laan
2015-06-18 11:47     ` Wladimir J. van der Laan
2015-06-18 13:36       ` Mike Hearn
2015-06-18 15:58         ` Gregory Maxwell
2015-06-18 12:29     ` Pieter Wuille
2015-06-18 12:50       ` Wladimir J. van der Laan
2015-06-18 12:56         ` Benjamin
2015-06-18 13:49       ` Mike Hearn
2015-06-18 14:05         ` Wladimir J. van der Laan
2015-06-18 14:16           ` Mike Hearn
2015-06-18 14:53           ` Milly Bitcoin
2015-06-18 14:56             ` Jeff Garzik
2015-06-18 15:13               ` Milly Bitcoin
2015-06-18 14:53       ` Jeff Garzik
2015-06-18 16:07         ` justusranvier
2015-06-18 16:28           ` Jeff Garzik
2015-06-18 17:04             ` justusranvier
2015-06-18 17:42               ` Alex Morcos
2015-06-18 18:01                 ` Milly Bitcoin
2015-06-18 18:23                 ` Gavin Andresen
2015-06-18 18:44                   ` Alex Morcos
2015-06-18 18:49                   ` Jorge Timón
2015-06-18 19:31                     ` Ross Nicoll
2015-06-18 21:42                       ` Matt Whitlock
2015-06-18 21:49                         ` Mark Friedenbach
2015-06-18 21:58                           ` Jeff Garzik [this message]
2015-06-18 22:33                             ` Mark Friedenbach
2015-06-18 22:52                               ` Jeff Garzik
2015-06-18 23:25                                 ` odinn
2015-06-18 23:16                               ` Ross Nicoll
2015-06-19  0:57                               ` Chris Pacia
2015-06-19  5:59                                 ` Eric Lombrozo
2015-06-19  9:37                               ` Mike Hearn
2015-06-19  9:53                                 ` Benjamin
2015-06-19 10:08                                   ` GC
2015-06-19 10:19                                   ` Mike Hearn
2015-06-19 10:52                                 ` Eric Lombrozo
2015-06-19 11:31                                 ` Jorge Timón
2015-06-19 12:26                                   ` GC
2015-06-19 11:48                                 ` Brooks Boyd
2015-06-21 14:45                                   ` Owen Gunden
2015-06-18 21:55                         ` Ross Nicoll
2015-06-18 19:24                   ` Matt Corallo
2015-06-18 19:32                     ` Gregory Maxwell
2015-06-18 12:38     ` Milly Bitcoin
2015-06-18 13:31     ` Mike Hearn
2015-06-18 13:50       ` Pieter Wuille
2015-06-18 15:03       ` Mark Friedenbach
2015-06-18 15:30         ` Milly Bitcoin
2015-06-18 15:46           ` Wladimir J. van der Laan
2015-06-18 16:05             ` Mike Hearn
2015-06-18 16:20               ` Wladimir J. van der Laan
2015-06-18 22:49               ` odinn
2015-06-18 16:11             ` Milly Bitcoin
2015-06-18 11:41   ` Lawrence Nahum
2015-06-18 14:33   ` Bryan Bishop
2015-06-18 18:09   ` Melvin Carvalho
2015-06-18 22:10   ` 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=CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavin@bitcoinfoundation.org \
    --cc=mark@friedenbach.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