From: Bryan Bishop <kanzure@gmail.com>
To: "David A. Harding" <dave@dtrt.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
Date: Mon, 8 May 2023 07:03:10 -0500 [thread overview]
Message-ID: <CABaSBaxbAknhqBnOmtBn8Gt44xJz7jYjS-wyVE36RkJTPhPxdw@mail.gmail.com> (raw)
In-Reply-To: <f2912dbbad28db5139e8df13f52e082d@dtrt.org>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Sun, May 7, 2023 at 12:36 PM David A. Harding via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 2023-05-06 21:03, Michael Folkson via bitcoin-dev wrote:
> > Essentially my concern is going forward current maintainers will
> > decide which proposed new maintainers to add and which to block.
>
> This is how a large percentage of organizations are run. The current
> members of a board or other governance group choose who will become a
> new board member.
>
Yes but it's unrelated to what Bitcoin Core is-- a volunteer project of
independent contributors merging different pull requests or patches. The
github controls are merely because that is how github works. There is also
a secondary issue of people tending to confuse Bitcoin Core with the
bitcoin protocol in general:
https://blog.lopp.net/who-controls-bitcoin-core/
https://medium.com/@bergealex4/the-tao-of-bitcoin-development-ff093c6155cd
https://bitcoinmagazine.com/culture/a-primer-on-bitcoin-governance-or-why-developers-aren-t-in-charge-of-the-protocol-1473270427
- Bryan
https://twitter.com/kanzure
[-- Attachment #2: Type: text/html, Size: 1879 bytes --]
next prev parent reply other threads:[~2023-05-08 12:03 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
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 [this message]
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=CABaSBaxbAknhqBnOmtBn8Gt44xJz7jYjS-wyVE36RkJTPhPxdw@mail.gmail.com \
--to=kanzure@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=dave@dtrt.org \
/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