š
Original date posted:2023-05-07
šļø Summary of this message: The concern is that current maintainers will decide which proposed new maintainers to add and which to block, but this is how many organizations are run. The questions to ask are whether the current maintainers are capable of moving Bitcoin Core in the right direction and what can be done if they are not. However, this matter should not have been posted to this mailing list.
š Original message: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
David A. Harding [ARCHIVE] /
npub16dā¦x4wrd
2023-06-07 23:21:18
in reply to nevent1qā¦8ld6
Author Public Key
npub16dt55fpq3a8r6zpphd9xngxr46zzqs75gna9cj5vf8pknyv2d7equx4wrdPublished at
2023-06-07 23:21:18Event JSON
{
"id": "d57d164cd194ca341d265e685267ea539ac5e29cf3d1f1d3fdd70033e5da5d15",
"pubkey": "d3574a24208f4e3d0821bb4a69a0c3ae842043d444fa5c4a8c49c369918a6fb2",
"created_at": 1686180078,
"kind": 1,
"tags": [
[
"e",
"2086b54aaa800b8e2856370c0c80add4705e021308f6a7274160ea95b8b060e3",
"",
"root"
],
[
"e",
"5d90187f77a2be901db26b7d50be3766b5ecdb0373a026f2c0cf373da3a78ed9",
"",
"reply"
],
[
"p",
"7c4981f0d3c5eec97631de273b25b6435f0f33e0fa6cce270ddd3f3b8797d26a"
]
],
"content": "š
Original date posted:2023-05-07\nšļø Summary of this message: The concern is that current maintainers will decide which proposed new maintainers to add and which to block, but this is how many organizations are run. The questions to ask are whether the current maintainers are capable of moving Bitcoin Core in the right direction and what can be done if they are not. However, this matter should not have been posted to this mailing list.\nš Original message:On 2023-05-06 21:03, Michael Folkson via bitcoin-dev wrote:\n\u003e Essentially my concern is going forward current maintainers will\n\u003e decide which proposed new maintainers to add and which to block.\n\nThis is how a large percentage of organizations are run. The current \nmembers of a board or other governance group choose who will become a \nnew board member.\n\nOne alternative to self-perpetuating governance is membership voting, \nbut building and maintaining democratic institutions is hard and not a \ngood fit for many types of endeavors---the building of highly technical \nsoftware being one of those cases IMO.\n\nI think the questions we want to ask is whether the current set of \nmaintainers is capable of moving Bitcoin Core in the direction we want \nand what we can do about it if we conclude that they are ill-suited (or \nmalicious). For the first question, I think that's something everyone \nneeds to answer for themselves, as we may each have different visions \nfor the future of the project. That said, I note that several \ninitiatives championed by the current maintainers in the IRC meeting you \nmention received overwhelmingly positive support from a significant \nnumber of current contributors, which seems like a healthy sign to me.\n\nFor the second question, I think AJ Towns already answered that quite \nwell (though he was talking about a different project): \nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-April/021578.html\n\nFinally, I don't think this matter warranted a post to this mailing \nlist. Discussion about internal project decisions, such as who should \nhave merge access and what maintainers should communicate in PRs, belong \nin communication channels dedicated to that project.\n\n-Dave",
"sig": "aa7b9094a2bd89d32d10cc8ff60f3d8b27dc4190cb332b41fc1cb3848c76866270d2aeb1d62b3ad2a1b75f04bf5bf4ae609bf854ce4f14d562f3e2d7fae548b5"
}