Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0777FC002A for ; Wed, 10 May 2023 16:37:08 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id D65DC404AE for ; Wed, 10 May 2023 16:37:07 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org D65DC404AE Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20221208 header.b=lWWbimH2 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 smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-x9lcaSmh_C for ; Wed, 10 May 2023 16:37:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org B8A32404C8 Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) by smtp2.osuosl.org (Postfix) with ESMTPS id B8A32404C8 for ; Wed, 10 May 2023 16:37:06 +0000 (UTC) Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-51452556acdso4956647a12.2 for ; Wed, 10 May 2023 09:37:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683736626; x=1686328626; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W6eMIc54gScc5YwDj1GomdPeTBOZqb8YTKlbjIPUSBU=; b=lWWbimH2hVh5ZHkfbj8MDmUNNFDsGzO4N72482w1IeMNyyB9qcpgYo0FBXSbQWzqdn 3263N1z6PTkxLjtYFhKdjzv27UE/xOcSNxIUu2GeR5/IZ+aBNdEwAnzc8reQVcR34F+X iW6+l/NTvwkks9vQdqYGLKCpvZ8yCS/iXUD9lpBB0WbXxaReuqVYNtKN9IA9DRGNHoh7 F5Ai2otvxVyZcBRuTG7/Z1FQOGRx4qCiARW/YFaGJSaSRr9U6m0pAFtoZ8K/nD6QHuHR lf840LlTzpGD+xhhWa4F1gVXP28mG2eiomryiAZlnHxjmUKsGRWyoCB/68KSd0jZKGA7 mkpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683736626; x=1686328626; 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=W6eMIc54gScc5YwDj1GomdPeTBOZqb8YTKlbjIPUSBU=; b=bw+6PxD/pDnN4KfZ9dQz8TbRgoU7UK+uuvLt/fS/kriknHFfzjGX/BDBPTfCnRQLgF lSS0Aai7E1kqoevpanjuPr2Oad5ZHNhhaneuBv0p5P/qoVrikPYuRIa7B4SWdycZoUhb 2XLonDeSG3s8IveZahxswf0OVorL7qJ/lec70QkrzWNGUnHtqfP7bS0kyWyBTHT/qknI /tSs2awqnI1MPUNn/OxocVpx1aW5yAo7ohJ5ICti2sZrANS0H1j53g58lnfSrb8ecMOc m0W62Nshh4KIb0bRAZ1+x1g+YZtV/+qJfTUgGKCugNdYpvn8wTIFbYu234EL4DVshhmD U6ig== X-Gm-Message-State: AC+VfDwLVttoufqS8oKROVcx/aqNbrKRsoMYPObYwXQ4M5YIVkM1SMZn foNxcEoCcm4xCMTTlbviOpG4NulJeWLmr402A+A= X-Google-Smtp-Source: ACHHUZ4ohRbm/gdyysACfwM5bq4xK4/OxWoDsT7bAhUSlBqcxLmauFQINP+b1+BKgZhP9LBrRffaAyvbd34CjCplAuU= X-Received: by 2002:a17:90b:4d89:b0:24d:ef23:fe28 with SMTP id oj9-20020a17090b4d8900b0024def23fe28mr17034860pjb.49.1683736625922; Wed, 10 May 2023 09:37:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Steve Lee Date: Wed, 10 May 2023 09:36:54 -0700 Message-ID: To: Michael Folkson Content-Type: multipart/alternative; boundary="0000000000007bc90705fb597b82" X-Mailman-Approved-At: Wed, 10 May 2023 16:37:56 +0000 Cc: Bitcoin Protocol Discussion 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 16:37:08 -0000 --0000000000007bc90705fb597b82 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Blocking Vasil was discussed on a similar GitHub PR. Whether or not one agrees or disagrees, the same process is being used. Anyone can NACK and give a reason for Russ as well. On Wed, May 10, 2023 at 8:55=E2=80=AFAM Michael Folkson < michaelfolkson@protonmail.com> wrote: > Hi Steve > > > 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 > > Nope. The extent to which the rationale for blocking Vasil as a maintaine= r > applies or doesn't apply to ryanofsky (or future potential maintainers) > isn't discussed. From now on the precedent is proposed maintainers can be > blocked for unknown and/or potentially inconsistent reasons by the existi= ng > maintainers. > > Thanks > Michael > > -- > Michael Folkson > Email: michaelfolkson at protonmail.com > GPG: A2CF5D71603C92010659818D2A75D601B23FEE0F > > Learn about Bitcoin: https://www.youtube.com/@portofbitcoin > > ------- Original Message ------- > On Wednesday, May 10th, 2023 at 03:44, Steve Lee via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > > 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 al= so >> 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-ff093c6155= cd >> >> https://bitcoinmagazine.com/culture/a-primer-on-bitcoin-governance-or-wh= y-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 >> > > --0000000000007bc90705fb597b82 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Blocking Vasil was discussed on a similar GitHub PR. Wheth= er or not one agrees or disagrees, the same process is being used. Anyone c= an NACK and give a reason for Russ as well.

On Wed, May 10, 2023 at 8:55=E2= =80=AFAM Michael Folkson <michaelfolkson@protonmail.com> wrote:
Hi Steve

>=C2=A0Isn't this as simple as anyone (in particular Core project cont= ributors) can express their view in this PR?=C2=A0https://github.com/bitcoin/bitco= in/pull/27604

Nope. The extent to which the rationale for blocking Vasil as a maintainer= applies or doesn't apply to ryanofsky (or future potential maintainers= ) isn't discussed. From now on the precedent is proposed maintainers ca= n be blocked for unknown and/or potentially inconsistent reasons by the exi= sting maintainers.=C2=A0

Thanks
Michael

--
Michael Folkson
Email: michaelfolkson = at protonmail.com
GPG: A2CF5D71603C92010659818D2A75D601B23FEE0F
<= span style=3D"font-family:SFMono-Regular,Consolas,"Liberation Mono&quo= t;,Menlo,monospace,monospace">
=20
=20

------- Original Message -------
On Wednesday, May 10th, 2023 at 03:44, Steve Lee via bitcoin-dev &l= t;bitcoin-dev@lists.linuxfoundation.org> wrote:

Isn't this as simple as anyone (in particu= lar Core project contributors) can express their view in this PR? https://github.com/bitcoin/bitcoin/pull/2760= 4

On Mon, May 8, 2023 at 5:03=E2=80=AFAM Bryan Bishop via bitcoin-dev &l= t;bitcoin-dev@lists.linuxfoundation.or= g> wrote:
On Sun, May 7, 2023 at 12:36=E2=80=AFPM David A. Har= ding via bitcoin-dev <bitcoin-dev@l= ists.linuxfoundation.org> wrote:
On 2023-05-06 21:03, Mic= hael 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 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:
https://blog.lopp.net/who-controls-bitcoi= n-core/
https://medium.com/@bergealex4/the-tao-of-bitcoin-development-ff093c= 6155cd
https://bitcoin= magazine.com/culture/a-primer-on-bitcoin-governance-or-why-developers-aren-= t-in-charge-of-the-protocol-1473270427

_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org<= /a>
https://lists.linuxf= oundation.org/mailman/listinfo/bitcoin-dev

--0000000000007bc90705fb597b82--