From: "NxtChg" <nxtchg@hush•com>
To: "Patrick Murck" <patrick.murck@gmail•com>,
bitcoin-dev@lists•linuxfoundation.org,
"Milly Bitcoin" <milly@bitcoins•info>
Subject: Re: [bitcoin-dev] BIP Process and Votes
Date: Sun, 28 Jun 2015 23:21:26 +0300 [thread overview]
Message-ID: <20150628202127.27DCB41A3E@smtp.hushmail.com> (raw)
In-Reply-To: <etPan.5590456f.61df0e2.23f7@Patricks-MacBook-Pro-2.local>
On 6/28/2015 at 10:05 PM, "Patrick Murck" <patrick.murck@gmail•com> 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...
next prev parent reply other threads:[~2015-06-28 20:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 3:00 Raystonn
2015-06-25 3:19 ` Milly Bitcoin
2015-06-26 11:13 ` Jorge Timón
2015-06-26 12:34 ` Milly Bitcoin
2015-06-27 11:28 ` Jorge Timón
2015-06-27 12:50 ` Milly Bitcoin
2015-06-28 12:30 ` Jorge Timón
2015-06-28 13:13 ` Milly Bitcoin
2015-06-28 15:35 ` Jorge Timón
2015-06-28 16:23 ` Milly Bitcoin
2015-06-28 19:05 ` Patrick Murck
2015-06-28 20:10 ` Milly Bitcoin
2015-06-28 20:16 ` Mark Friedenbach
2015-06-28 20:26 ` Ricardo Filipe
2015-06-28 21:00 ` Adam Back
2015-06-29 0:13 ` Milly Bitcoin
2015-06-29 0:23 ` Andrew Lapp
2015-06-29 1:11 ` Milly Bitcoin
2015-06-28 23:52 ` Milly Bitcoin
2015-06-28 20:21 ` NxtChg [this message]
2015-06-25 19:03 ` Tom Harding
-- strict thread matches above, loose matches on Subject: below --
2015-06-25 3:53 Raystonn
2015-06-25 0:18 Raystonn
2015-06-24 23:41 Raystonn
2015-06-24 23:49 ` Jeff Garzik
2015-06-25 0:11 ` Bryan Bishop
2015-06-25 0:21 ` Milly Bitcoin
2015-06-25 0:07 ` Milly Bitcoin
2015-06-25 1:50 ` Mark Friedenbach
2015-06-25 2:30 ` Alex Morcos
2015-06-25 2:34 ` Milly Bitcoin
2015-06-25 5:07 ` Jeff Garzik
2015-06-25 5:41 ` Milly Bitcoin
2015-06-25 6:06 ` Pindar Wong
2015-06-25 6:15 ` Mark Friedenbach
2015-06-25 6:16 ` Warren Togami Jr.
2015-06-25 6:27 ` Pindar Wong
2015-06-25 7:51 ` cipher anthem
2015-06-25 10:09 ` nxtchg
2015-06-25 12:42 ` Milly Bitcoin
2015-06-25 20:05 ` Tier Nolan
2015-06-26 0:42 ` Milly Bitcoin
2015-07-01 22:34 ` odinn
2015-06-25 3:42 ` Gareth Williams
2015-06-25 4:10 ` Milly Bitcoin
2015-06-25 13:36 ` s7r
2015-06-25 13:41 ` Eric Lombrozo
2015-06-25 13:51 ` s7r
2015-06-25 14:08 ` Milly Bitcoin
2015-06-25 17:03 ` Jeff Garzik
2015-06-25 17:29 ` Milly Bitcoin
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=20150628202127.27DCB41A3E@smtp.hushmail.com \
--to=nxtchg@hush$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=milly@bitcoins$(echo .)info \
--cc=patrick.murck@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