From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 28C9DAE7 for ; Sun, 28 Jun 2015 20:21:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp2.hushmail.com (smtp2.hushmail.com [65.39.178.134]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DE2FCFD for ; Sun, 28 Jun 2015 20:21:27 +0000 (UTC) Received: from smtp2.hushmail.com (localhost [127.0.0.1]) by smtp2.hushmail.com (Postfix) with SMTP id 9501CA0698 for ; Sun, 28 Jun 2015 20:21:27 +0000 (UTC) Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32]) by smtp2.hushmail.com (Postfix) with ESMTP; Sun, 28 Jun 2015 20:21:27 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 27DCB41A3E; Sun, 28 Jun 2015 20:21:27 +0000 (UTC) MIME-Version: 1.0 Date: Sun, 28 Jun 2015 23:21:26 +0300 To: "Patrick Murck" , bitcoin-dev@lists.linuxfoundation.org, "Milly Bitcoin" From: "NxtChg" In-Reply-To: References: <558B7352.90708@bitcoins.info> <558D46EC.6050300@bitcoins.info> <558E9C06.9080901@bitcoins.info> <558FF307.9010606@bitcoins.info> <55901F7D.4000001@bitcoins.info> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20150628202127.27DCB41A3E@smtp.hushmail.com> X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] BIP Process and Votes X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2015 20:21:28 -0000 On 6/28/2015 at 10:05 PM, "Patrick Murck" wrote: >Maintainer is empowered to make changes to "teh Bitcoin" but the reality is that the Core Maintainer role is really about cat >herding and project management of Bitcoin Core the open-source software project and not the bitcoin network. It's not about pushing a change, it's about refusing a change on the grounds of controversy. This is _not_ an attack on Wladimir. His position in view of circumstances is perfectly reasonable: to take the safest option. Even at the risk of stagnation, as he pointed out, at least your funds won't be expropriated. It's a noble position to defend the minority. Unfortunately (or fortunately), the majority of power usually gets what it wants. Of course, "they will have it their way anyway" is not an appropriate reason to flip-flop on an ethical position, so nobody expects Wladimir to change his mind. Thus, we are playing a variation of prisoner's dilemma here: the best solution would be an agreement on both sides, if only they could agree. In reality, there's a good chance that Gavin's fork will win, creating precisely the problems and risks, which Wladimir tries to avoid, only more. And we will end up with lose-lose situation. But we lack any other mechanism for a scenario where interests of some of those 7 committers become misaligned with interests of the majority (which seems to be the case). And every time Bitcoin will face similar disagreement in the future we will go through it again...