From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqMyQ-0001qw-20 for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 14:40:26 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.148.106 as permitted sender) client-ip=62.13.148.106; envelope-from=pete@petertodd.org; helo=outmail148106.authsmtp.co.uk; Received: from outmail148106.authsmtp.co.uk ([62.13.148.106]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YqMyO-0003vF-3L for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 14:40:26 +0000 Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237]) by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t47EeHiW079290; Thu, 7 May 2015 15:40:17 +0100 (BST) Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com [75.119.251.161]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t47EeCZS059318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 7 May 2015 15:40:15 +0100 (BST) Date: Thu, 7 May 2015 10:40:12 -0400 From: Peter Todd To: Mike Hearn Message-ID: <20150507144012.GC32602@savin.petertodd.org> References: <554A91BE.6060105@bluematt.me> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mvpLiMfbWzRoNl4x" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: f9db4b2a-f4c6-11e4-9f74-002590a135d3 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgUUFVQNAgsB AmMbWlFeVF17WGU7 bA9PbARUfEhLXhtr VklWR1pVCwQmRRgG c0ttOHpycgxFeXY+ ZEdrWXYVCk0uJ0Iv QB9JQ2lVY3phaTUb TUkOcAdJcANIexZF O1F8UScOLwdSbGoL NQ4vNDcwO3BTJTpY RgYVKF8UXXNDNDo7 TBNKJjQ9EAUkQS4p IhU9JzYB X-Authentic-SMTP: 61633532353630.1024:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 75.119.251.161/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YqMyO-0003vF-3L Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Block Size Increase X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 14:40:26 -0000 --mvpLiMfbWzRoNl4x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 07, 2015 at 04:05:41PM +0200, Mike Hearn wrote: > > One thing is the Bitcoin core project where you could argue that the 5 > > committers decide (I don't know why Wladimir would have any more > > authority than the others). > > >=20 > Because he is formally the maintainer. I quite liked Wladimir's description of what someone with the ability to merge pull requests into Bitcoin Core is: @orionwl github.com/bitcoin/bitcoin repository admin, or maybe just "ja= nitor" -https://twitter.com/orionwl/status/563688293737697281 In any case, we can't force people to run Bitcoin Core - an unpopular patch that fails to reach consensus is a strong sign that it may not get user acceptance either - so we might as well accept that centralized authority over the development process isn't going to fly and deal with the sometimes messy consequences. Like I said, you're welcome to fork the project and try to get user acceptance for the fork. --=20 'peter'[:-1]@petertodd.org 000000000000000013e67b343b1f6d75cc87dfb54430bdb3bcf66d8d4b3ef6b8 --mvpLiMfbWzRoNl4x Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJVS3lIXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAxMTVkZjY4OTcwNmM4OTZkYTJjMjdiODdjYjc2MjQyMjFm NTJkMDRjNzA1NjZlODQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfsSDQgAl/lcL81n2GEgukVYfMvZ1nTX ipwO/YYDBze8Erjhp27HZep0WRL75ubXp21q8ckBcp4TfZMltUCRp62CozThEhJR JDL8Xk1Bq89CNCfRguNb+FVqZY57U0v5J+tiZTlMqv97ZEMnF9VIAmYYrP3PsORT BHtjeQRqkJy3MtgvN4Q3WW2tHIYrUc+8xsSYZH4rI4BfeHmVwn7uRDRmtHMrKLLk TnZ+VFpE2AjCcP6irbnPiAhpvZ5b/KQnN1D6zJg5fcOpC8gV9l7rp844XIok59GX Oa0NGmCNoxfqArQphneWfBUyKP0w3ig3kZdnVM06mq3n3U6vViuE6bYDq0ih8Q== =MxJe -----END PGP SIGNATURE----- --mvpLiMfbWzRoNl4x--