Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 9597FC002A for ; Mon, 8 May 2023 12:03:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 5AA264003B for ; Mon, 8 May 2023 12:03:26 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5AA264003B Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20221208 header.b=EiiFBT80 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SC1p5tKA3bHQ for ; Mon, 8 May 2023 12:03:25 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org ADDA640903 Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) by smtp4.osuosl.org (Postfix) with ESMTPS id ADDA640903 for ; Mon, 8 May 2023 12:03:24 +0000 (UTC) Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-4f139de8cefso27338806e87.0 for ; Mon, 08 May 2023 05:03:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683547402; x=1686139402; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=f8XvkGCtoBn8AgKhUgoFd8ngnnLKoPanpSu1cz71Clo=; b=EiiFBT806NWuiMf5Wxz/rWrPQSr+SoulmJsmMgxR86IrGHSQJtqVnUP944LNmJXG2z xMRFJyp5L3F/t/FaDEKFJxiOJmOL7lgUYtngO2tsbstXw8WCiO14qs/x6QSu6SRoGD5c /Ac/ufRLs1Ut+OYMfgShKNy8rz/mlaxIyOEXNsdH73zt+LD09xgO5+WpuTRSPLVgU0Se ueKaV56vjg19DmcNFnpUnh3fM7WEXfbNilZ7hbBtTykiuJD2KIuupLTzFo2t4u6Hy4Om 1MBrf0lhpTaAsTUGC26yeKGxVd8fLk47OSgQNWzY5tLvgGmRRDdBFGkwCk/EPYjsBp2P Ox7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683547402; x=1686139402; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=f8XvkGCtoBn8AgKhUgoFd8ngnnLKoPanpSu1cz71Clo=; b=XeAYRP75FNUdO/Vq8Dllj7cNYVOn4UTbwppjnKkemhzLKAcvWIxp9N+yvoK/U4t9FT eXxMA7l80xre/vwW+dR48u2gFEArSoGc2aRN4n2jd6qS0n7kkOVvTU6IyF4HYKK2PGu5 9Mb358BBCcHej6GMHA5tkErAH3Njp+9BFMkbdRvZ2D+w5rrxtKqKPUx9o0IfwFBYf3id RMAGLCqV00O5TiEWJEnvTNNSj6I+6dsvXQZd/jgQZJSU5twTveQO66LObP8FAEfwSt6q 399bRytmiQTHUwsNR/hMYV3sf4zf0Vgb2lZD9EWU9aS+oRXeHRGoJlfDIFLx+CDY2Zpk niwA== X-Gm-Message-State: AC+VfDy+Ua9P0TchXVNFg7TOUG0yZICjN2Ce0UQgNQhmhbVrhvvkCP1j ln+dGKy5fea3O7a1NLQQ1oYKq1Oy8nWnSz9QjgI= X-Google-Smtp-Source: ACHHUZ7aQcngPXD3jF1/kQUypcOs1cVojQ4PDrEUtFzkmrdrGSzgRksBIAr/3jzhBxoj7db0abQfx4wkgGME13W252Q= X-Received: by 2002:a05:6512:14d:b0:4ec:ae17:81d9 with SMTP id m13-20020a056512014d00b004ecae1781d9mr2399325lfo.32.1683547402313; Mon, 08 May 2023 05:03:22 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bryan Bishop Date: Mon, 8 May 2023 07:03:10 -0500 Message-ID: To: "David A. Harding" , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000e0a68d05fb2d6c2d" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2023 12:03:26 -0000 --000000000000e0a68d05fb2d6c2d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, May 7, 2023 at 12:36=E2=80=AFPM 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-d= evelopers-aren-t-in-charge-of-the-protocol-1473270427 - Bryan https://twitter.com/kanzure --000000000000e0a68d05fb2d6c2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, May 7, 2023 at 12:36=E2=80=AFPM David A. Hard= ing 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.=C2=A0 The current =
members of a board or other governance group choose who will become a
new board member.

Yes but it's unrelated to wh= at Bitcoin Core is-- a volunteer project of independent contributors mergin= g different pull requests or patches. The github controls are merely becaus= e that is how github works. There is also a secondary issue of people tendi= ng to confuse Bitcoin Core with the bitcoin protocol in general:
htt= ps://blog.lopp.net/who-controls-bitcoin-core/
https://medium.com/@bergealex4/the-tao-of-bitcoin-development-ff093= c6155cd
https://bitcoinmagazine.com/culture/a-primer-on-bit= coin-governance-or-why-developers-aren-t-in-charge-of-the-protocol-14732704= 27

--000000000000e0a68d05fb2d6c2d--