public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "David A. Harding" <dave@dtrt.org>
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: Sun, 07 May 2023 07:35:52 -1000	[thread overview]
Message-ID: <f2912dbbad28db5139e8df13f52e082d@dtrt.org> (raw)
In-Reply-To: <qLlgx_AotByY1ZZHTCn3BBK7x1spKEYYd3UP4txYq-RceoclKdVAB1E5MJ4FTV7bWVP1Ilsdbmn43dkrOfqw84EUUQAvnkztN9FY1R5oDOA=@protonmail.com>

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.

One alternative to self-perpetuating governance is membership voting, 
but building and maintaining democratic institutions is hard and not a 
good fit for many types of endeavors---the building of highly technical 
software being one of those cases IMO.

I think the questions we want to ask is whether the current set of 
maintainers is capable of moving Bitcoin Core in the direction we want 
and what we can do about it if we conclude that they are ill-suited (or 
malicious).  For the first question, I think that's something everyone 
needs to answer for themselves, as we may each have different visions 
for the future of the project.  That said, I note that several 
initiatives championed by the current maintainers in the IRC meeting you 
mention received overwhelmingly positive support from a significant 
number of current contributors, which seems like a healthy sign to me.

For the second question, I think AJ Towns already answered that quite 
well (though he was talking about a different project): 
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021578.html

Finally, I don't think this matter warranted a post to this mailing 
list.  Discussion about internal project decisions, such as who should 
have merge access and what maintainers should communicate in PRs, belong 
in communication channels dedicated to that project.

-Dave


  reply	other threads:[~2023-05-07 17:35 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 [this message]
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=f2912dbbad28db5139e8df13f52e082d@dtrt.org \
    --to=dave@dtrt.org \
    --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