1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Return-Path: <dave@dtrt.org>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id BD512C002A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 May 2023 17:35:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 917E88204E
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 May 2023 17:35:57 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 917E88204E
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id i0krx0wEQ9e1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 May 2023 17:35:56 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 814F081F51
Received: from smtpauth.rollernet.us (smtpauth.rollernet.us
[IPv6:2607:fe70:0:3::d])
by smtp1.osuosl.org (Postfix) with ESMTPS id 814F081F51
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 7 May 2023 17:35:56 +0000 (UTC)
Received: from smtpauth.rollernet.us (localhost [127.0.0.1])
by smtpauth.rollernet.us (Postfix) with ESMTP id AFE9D2800840;
Sun, 7 May 2023 10:35:53 -0700 (PDT)
Received: from webmail.rollernet.us (webmail.rollernet.us
[IPv6:2607:fe70:0:14::a])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client did not present a certificate)
by smtpauth.rollernet.us (Postfix) with ESMTPSA;
Sun, 7 May 2023 10:35:52 -0700 (PDT)
MIME-Version: 1.0
Date: Sun, 07 May 2023 07:35:52 -1000
From: "David A. Harding" <dave@dtrt.org>
To: Michael Folkson <michaelfolkson@protonmail.com>, Bitcoin Protocol
Discussion <bitcoin-dev@lists.linuxfoundation.org>
In-Reply-To: <qLlgx_AotByY1ZZHTCn3BBK7x1spKEYYd3UP4txYq-RceoclKdVAB1E5MJ4FTV7bWVP1Ilsdbmn43dkrOfqw84EUUQAvnkztN9FY1R5oDOA=@protonmail.com>
References: <uuq_VbxJp50_-m4ufKpEhJOknhZ0pvK8ioDabCkxtDjBYauO3gLKrj2O2tjS6YIFOnJLyaZg6-LENzom1DyQQ3TyMLIIaGz5IRrzrKB8gRs=@protonmail.com>
<qLlgx_AotByY1ZZHTCn3BBK7x1spKEYYd3UP4txYq-RceoclKdVAB1E5MJ4FTV7bWVP1Ilsdbmn43dkrOfqw84EUUQAvnkztN9FY1R5oDOA=@protonmail.com>
User-Agent: Roundcube Webmail/1.4.10
Message-ID: <f2912dbbad28db5139e8df13f52e082d@dtrt.org>
X-Sender: dave@dtrt.org
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
X-Rollernet-Abuse: Contact abuse@rollernet.us to report. Abuse policy:
http://www.rollernet.us/policy
X-Rollernet-Submit: Submit ID 2459.6457e178.b87e0.0
Subject: Re: [bitcoin-dev] Bitcoin Core maintainers and communication on
merge decisions
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sun, 07 May 2023 17:35:57 -0000
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
|
