From: Peter R <peter_r@gmx•com>
To: Tom Harding <tomh@thinlink•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] This thread is not about the soft/hard fork technical debate
Date: Mon, 5 Oct 2015 20:20:33 -0700 [thread overview]
Message-ID: <8EF9A9A8-3EBE-4427-9745-1C494DF12E9A@gmx.com> (raw)
In-Reply-To: <561325D4.5030800@thinlink.com>
> On Oct 5, 2015, at 6:37 PM, Tom Harding via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> On 10/5/2015 1:56 PM, Gregory Maxwell via bitcoin-dev wrote:
>> In this case, I don't even believe we have any regulator contributors
>> that disagree.
>
> Since Gavin Andresen chose you to be one of 4 people who decides whose
> contributions are accepted to the Core project, shouldn't you recuse
> yourself from referencing "regular contributor" as some kind of bar to
> an opinion being worthy?
>
> You don't want to be accused of squelching a person's opinions by
> nacking or sitting on commits, then turning around and branding those
> opinions as worthless because they are not from a "regular contributor."
> Do you?
Great point, Tom!
In fact, you’ve just explained the dynamics that create “centralizing pressure” in regards to development: If the weight of a person’s opinion is proportional to how many commits that person has made, and if the probability of getting a commit pulled is proportional to the weight of that person’s opinion, well…I’m pretty sure this results in a differential equation that has a solution that results in ever-increasing centralized control of the code base.
I believe we should work to deprecate the idea that Core is somehow the “core of Bitcoin," in favour of multiple competing implementations. XT and btcd are two working examples of this idea. Let’s make it easier for the community to determine the evolution of Bitcoin by making it easier for the community to express their vote based on the code we choose to run.
Best regards,
Peter
next prev parent reply other threads:[~2015-10-06 3:20 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 15:56 Sergio Demian Lerner
2015-10-05 16:39 ` NxtChg
2015-10-05 16:51 ` Luke Dashjr
2015-10-05 16:56 ` Mike Hearn
2015-10-05 17:01 ` Paul Sztorc
2015-10-05 17:33 ` Peter R
2015-10-05 17:56 ` NxtChg
2015-10-05 22:56 ` Btc Drak
2015-10-05 23:05 ` Milly Bitcoin
2015-10-05 17:35 ` Btc Drak
2015-10-06 18:23 ` Venzen Khaosan
2015-10-06 18:28 ` Venzen Khaosan
2015-10-06 19:34 ` naama.kates
2015-10-05 17:03 ` Btc Drak
2015-10-05 17:26 ` Tom Zander
2015-10-05 17:52 ` Btc Drak
2015-10-05 18:04 ` Gregory Maxwell
2015-10-05 18:33 ` Tom Zander
2015-10-05 18:50 ` NotMike Hearn
2015-10-05 17:33 ` s7r
2015-10-05 18:51 ` Tom Zander
2015-10-05 18:35 ` Gregory Maxwell
2015-10-05 19:13 ` Tom Zander
2015-10-05 19:41 ` Gregory Maxwell
2015-10-05 20:05 ` Steven Pine
2015-10-05 20:21 ` Milly Bitcoin
2015-10-06 7:17 ` cipher anthem
2015-10-06 7:20 ` Eric Lombrozo
2015-10-06 7:29 ` Marcel Jamin
2015-10-06 8:34 ` NotMike Hearn
2015-10-06 19:40 ` naama.kates
2015-10-05 20:28 ` Santino Napolitano
2015-10-05 20:35 ` Tom Zander
2015-10-05 20:54 ` Dave Scotese
2015-10-05 20:56 ` Gregory Maxwell
2015-10-05 21:08 ` Tom Zander
2015-10-05 21:16 ` Milly Bitcoin
2015-10-05 21:26 ` Gregory Maxwell
2015-10-06 7:14 ` Tom Zander
2015-10-05 21:27 ` Peter R
2015-10-05 21:30 ` Gregory Maxwell
2015-10-05 21:36 ` Milly Bitcoin
2015-10-05 21:37 ` Peter R
2015-10-06 1:37 ` Tom Harding
2015-10-06 3:20 ` Peter R [this message]
2015-10-06 3:39 ` Milly Bitcoin
2015-10-06 4:54 ` Luke Dashjr
2015-10-06 5:08 ` Milly Bitcoin
2015-10-06 5:49 ` Milly Bitcoin
2015-10-06 5:53 ` Luke Dashjr
2015-10-06 6:03 ` Milly Bitcoin
2015-10-06 22:14 ` phm
2015-10-06 5:07 ` NotMike Hearn
2015-10-06 5:33 ` Peter R
2015-10-05 19:36 ` Milly Bitcoin
2015-10-05 23:18 ` Eric Lombrozo
2015-10-06 17:28 ` Venzen Khaosan
2015-10-07 0:04 ` Sergio Demian Lerner
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=8EF9A9A8-3EBE-4427-9745-1C494DF12E9A@gmx.com \
--to=peter_r@gmx$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomh@thinlink$(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