Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 1507FC002A for ; Wed, 10 May 2023 02:45:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id DD6B460C14 for ; Wed, 10 May 2023 02:45:12 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org DD6B460C14 Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20221208 header.b=Wlk3XUZz 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 smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpfeVKQZ2nV3 for ; Wed, 10 May 2023 02:45:12 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E420460B38 Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by smtp3.osuosl.org (Postfix) with ESMTPS id E420460B38 for ; Wed, 10 May 2023 02:45:11 +0000 (UTC) Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-24df161f84bso4746986a91.3 for ; Tue, 09 May 2023 19:45:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683686711; x=1686278711; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=X3UwH/TxOcFAIc/3Hczxi55U2fpur6VPaTxD6au8JEo=; b=Wlk3XUZztuzEJef6UQovxRa92Qw93d4b3Dh0XLL25ur4TCIFwrDM783qSdpvSMtkcM cOqpqqQGMkWEOChMXsVQF4AibkKLAh9zf2Au1xjNudr9vwFnWTi05dE+xVrJom1s8bfL sOX/DV03dnbTWi1/Jl8bJtbMazfCoPYbvTHFaSAi6bAbrhxFYkzuu/bIvkK6txG8Fya5 beNIpKJFI0dyp1GD3/eRhXJeCOSQz9A3q+i8Le35wtUnSJ3Kg4jzB5fxNfuXtDhsJrBs 5b0HXTBNLf6/FLwizAopmM4MXFVWjILDJZlm8ye7kPzraL1/2e8vEYEenBBF6I+/JLtY Rilg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683686711; x=1686278711; 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=X3UwH/TxOcFAIc/3Hczxi55U2fpur6VPaTxD6au8JEo=; b=C8uS0Q42n6uTELayjyl+NoG8bbHjhr0gUwV2pPiNwDcSVjJ/CO/Uz0gL/Pm0yOAGsU 4QsjzoX8t3pvwFrkDa3J5aHuOcy/jmCqMc8Lhr3nTynXDlUXfyjj6OPEBiavL+j1MgaX zOkm2kiVL3TAMbuSx6W29qSx1MZ+T494fD6GwzpHR670K8b0hbrCltC4FmrwsbYjJiOz Yctz3vFR3K6yjVEN5NKDViKhJlmEY3GH6CmYcxvajUQjred+eD5QnVYZZFRgn06eFOY3 wMYVtfjUP6gLCqeRit4D4a9z3eNCHqIdzGJE5/0nvghDTE8ISSOvbk7FA4Ht9f1A7842 4YBQ== X-Gm-Message-State: AC+VfDzlsQchJasOF/s6gPOuCschrnCrFm1uJy+qKp95SgSNH7gzLoeh sBztsH5cz6sj1iVR5Z/MYRbd/3iCeVnVpZLUgqk= X-Google-Smtp-Source: ACHHUZ5FP4hHh8TFoYGOOSbl6r/BSaNSayAelNEE6lFXH5vsSkHTcBGVZyPJDcQadg5XRyWfzTawdf8go1s1B9aVD+Y= X-Received: by 2002:a17:90a:8d16:b0:250:faff:e201 with SMTP id c22-20020a17090a8d1600b00250faffe201mr153977pjo.36.1683686710638; Tue, 09 May 2023 19:45:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Steve Lee Date: Tue, 9 May 2023 19:44:59 -0700 Message-ID: To: Bryan Bishop , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000004cfca105fb4ddc52" X-Mailman-Approved-At: Wed, 10 May 2023 15:38:39 +0000 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: Wed, 10 May 2023 02:45:13 -0000 --0000000000004cfca105fb4ddc52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Isn't this as simple as anyone (in particular Core project contributors) can express their view in this PR? https://github.com/bitcoin/bitcoin/pull/27604 On Mon, May 8, 2023 at 5:03=E2=80=AFAM Bryan Bishop via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 als= o > 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-ff093c6155c= d > > 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 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --0000000000004cfca105fb4ddc52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Isn't this as simple as anyone (in particular Core pro= ject contributors) can express their view in this PR?=C2=A0https://github.com/bitcoin/bitcoi= n/pull/27604

On Mon, May 8, 2023 at 5:03=E2=80=AFAM Bryan Bishop via bit= coin-dev <bitco= in-dev@lists.linuxfoundation.org> wrote:
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.=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

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--0000000000004cfca105fb4ddc52--