From: Anthony Towns <aj@erisian.com.au>
To: Michael Folkson <michaelfolkson@protonmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
Date: Thu, 20 Apr 2023 12:27:13 +1000 [thread overview]
Message-ID: <ZECjAWr1cYtBKb+U@erisian.com.au> (raw)
In-Reply-To: <uuq_VbxJp50_-m4ufKpEhJOknhZ0pvK8ioDabCkxtDjBYauO3gLKrj2O2tjS6YIFOnJLyaZg6-LENzom1DyQQ3TyMLIIaGz5IRrzrKB8gRs=@protonmail.com>
On Tue, Apr 18, 2023 at 12:40:44PM +0000, Michael Folkson via bitcoin-dev wrote:
> I do think the perception that it is “the one and only” staging
> ground for consensus changes is dangerous
If you think that about any open source project, the answer is simple:
create your own fork and do a better job. Competition is the only answer
to concerns about the bad effects from a monopoly. (Often the good effects
from cooperation and collaboration -- less wasted time and duplicated
effort -- turn out to outweigh the bad effects, however)
In any event, inquisition isn't "the one and only staging ground for
consensus changes" -- every successful consensus change to date has
been staged through the developers' own repo then the core PR process,
and that option still exists.
Cheers,
aj
next prev parent reply other threads:[~2023-04-20 2:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 12:40 [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions Michael Folkson
2023-04-19 0:56 ` Erik Aronesty
2023-04-19 10:09 ` Michael Folkson
2023-04-19 12:24 ` alicexbt
2023-04-19 13:33 ` Michael Folkson
2023-04-19 21:13 ` alicexbt
2023-04-19 15:17 ` Aymeric Vitte
2023-04-19 21:33 ` Andrew Chow
2023-04-20 8:45 ` Michael Folkson
2023-04-20 10:54 ` Aymeric Vitte
2023-04-20 13:59 ` Erik Aronesty
2023-04-20 14:25 ` Aymeric Vitte
2023-04-20 2:27 ` Anthony Towns [this message]
2023-04-20 9:24 ` Michael Folkson
2023-05-07 7:03 ` Michael Folkson
2023-05-07 17:35 ` David A. Harding
2023-05-08 9:36 ` Michael Folkson
2023-05-08 12:03 ` Bryan Bishop
2023-05-10 2:44 ` Steve Lee
2023-05-10 15:55 ` Michael Folkson
2023-05-10 16:36 ` Steve Lee
2023-05-10 17:22 ` Michael Folkson
2023-05-10 18:29 ` Steve Lee
2023-05-10 21:24 ` Andrew Chow
2023-05-11 12:34 ` Michael Folkson
2023-05-11 16:49 ` alicexbt
2023-05-11 18:04 ` Steve Lee
2023-05-11 18:48 ` Erik Aronesty
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=ZECjAWr1cYtBKb+U@erisian.com.au \
--to=aj@erisian.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=michaelfolkson@protonmail.com \
/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