Delivery-date: Tue, 02 Apr 2024 07:30:35 -0700 Received: from mail-yb1-f185.google.com ([209.85.219.185]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rrf9m-0000eG-Pd for bitcoindev@gnusha.org; Tue, 02 Apr 2024 07:30:35 -0700 Received: by mail-yb1-f185.google.com with SMTP id 3f1490d57ef6-dc743cc50a6sf5979127276.2 for ; Tue, 02 Apr 2024 07:30:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712068228; x=1712673028; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=cQS4nBfaPuJI9bHZbYmRNKxB33P+T0pdEsnMu9hUD60=; b=H3Cfe3IeYJMGnbdC8rPadqJbnEH8LUJft0A1kMjg0ZvreV71lI/gVnyO/wKwgvuvV1 SLm/aSaGSvRhQhW8d1Fuvwf3/TGSg+KIZi4Dyj5T6czgnCulM3fOYKh90OFc2gY/bV9W bjk+6sGf246YHMt/pOFCAcrdKG6o/QUXH63U9S0xr0xH7KdR3C1lA8yktQWqIeKMtb3T ErdG5eDknLPBRrEc36NZr1X+bpmFULYFTLS0LK+XGlbpg7nYFSRykq07WoUrWG96kuah 60ANod+GIDQK0qjMWwmhEiEr5NRlTyRwYvs0O/sDFhYjoba7SgHvsQEwtSFU1rG6Apgp pEyA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712068228; x=1712673028; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=cQS4nBfaPuJI9bHZbYmRNKxB33P+T0pdEsnMu9hUD60=; b=H1pTYnxgTvXCQa/do0jhBXSje1WXdwEM7DgMZWBAcOcCDeX+qGQnBwfrPNkYc3D2ZV 9Bfkjb0zR5PdSK7eJB3TMaWQ30PXZm2ZudDNWh3Wgrjgf1HSPwoEwe4LEcOnzV5wTBvR jBQQyy/2+q0jXMS6phnaH6wZGaAXAcDoBmskdARkgjrcvb8leX+39yvOFkrDqGue3Iah bvUlrcElOuqVI3GTUDEaKAxRAKVDju2X2q53n/0kmZwWkQq82TW/a13NZW/gA94t2SHU H//o7agd5f1cg0TWmEYcV5jpyBWJlO9mWyhkkLPJ2U6kEoh3sNQwsKebiJ9sfA9UCKs1 8M9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712068228; x=1712673028; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=cQS4nBfaPuJI9bHZbYmRNKxB33P+T0pdEsnMu9hUD60=; b=ZCTBwJiE5PaIRDALXgKEQrYTwgE2aSU2TfltGs22nHqLtg1lStz9lgV4hGgW9hqamA MBelG+CPK4w++4jtq2SCKQ4OAddSRsaMcNqtuMVcozdhJAFK3/sjpEFCTf//+Fr/3wYi 6oEqRdtIu68+sB3+u4c6IfAlpKoaclQaTlpgh4iqUMtRd9byeaClTuwN0ETgLWVK1CmZ 5CpauFb36mFmAiTlY+SDFrWJi8i7xsT264pU9vXFdFEnbo7xFwO08WLkYUnTMrA8/rTf ukjS63sTjL1q7Wq6KL2r+XaPLrDnvP2z1UxiHlWVGFib5DF/2xC6S5oyGkLi7xX72NSc zTsA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCVmUuq2tc8tqffyjkkHTsSAXWu+xAjOsq7HV6M5fLmuC/4yJynXXvWx79mMOewEoa5Wo/TkDScK43j04QB6J9EpVa/9HRY= X-Gm-Message-State: AOJu0YxevDHDCLLPIKUdzRMhlVZ4W0kuFPTnTDjZC8HO07j9Zr5+Tolb yAZRhTLSqRL+H9uppB5CwktTXms9F8pCxR1Cm4H0/+6El2et2X00 X-Google-Smtp-Source: AGHT+IFSqY69IZCdEZIuspGZsNt8775l+t2aHOCXL9EYZ7Y0/Dvf0Q+ajeyztolIF/TR+2+MEmB8GQ== X-Received: by 2002:a25:a28f:0:b0:dcf:464d:8ec3 with SMTP id c15-20020a25a28f000000b00dcf464d8ec3mr10243727ybi.3.1712068227544; Tue, 02 Apr 2024 07:30:27 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:ab2c:0:b0:dcc:4b24:c0df with SMTP id u41-20020a25ab2c000000b00dcc4b24c0dfls372674ybi.0.-pod-prod-03-us; Tue, 02 Apr 2024 07:30:25 -0700 (PDT) X-Received: by 2002:a0d:e688:0:b0:614:2598:d7a0 with SMTP id p130-20020a0de688000000b006142598d7a0mr676887ywe.5.1712068225570; Tue, 02 Apr 2024 07:30:25 -0700 (PDT) Received: by 2002:a05:690c:102:b0:611:2a20:d0cc with SMTP id 00721157ae682-614558bcb37ms7b3; Tue, 2 Apr 2024 07:24:22 -0700 (PDT) X-Received: by 2002:a0d:d7d2:0:b0:615:dce:e3e with SMTP id z201-20020a0dd7d2000000b006150dce0e3emr768007ywd.9.1712067861202; Tue, 02 Apr 2024 07:24:21 -0700 (PDT) Date: Tue, 2 Apr 2024 07:24:20 -0700 (PDT) From: nvk To: Bitcoin Development Mailing List Message-Id: <7b4e2223-0b96-4ca0-a441-aebcfc7b0bben@googlegroups.com> In-Reply-To: <77554baa9330c57361c65c1fc85557f1@dtrt.org> References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org> <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one> <84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com> <9baa15e4-062d-478f-8c87-8ff19ab79989@murch.one> <4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com> <6806b22d-043d-4201-841a-95e17cd8d542@mattcorallo.com> <77554baa9330c57361c65c1fc85557f1@dtrt.org> Subject: Re: [bitcoindev] Re: Adding New BIP Editors MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_18282_1476111482.1712067860825" X-Original-Sender: rdlfnvk@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: 1.0 (+) ------=_Part_18282_1476111482.1712067860825 Content-Type: multipart/alternative; boundary="----=_Part_18283_1245753081.1712067860825" ------=_Part_18283_1245753081.1712067860825 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 +1 for Kanzure RubenSomsen Seccour Jon Atack Roasbeef I would prefer having more (9+?) than less folks on this task, so personal= =20 preferences are easily ignored and overwritten by the group majority. BIPs were intended as a means to collect ideas, not enforce ideas. I'd like to return to that. - - NVK (temp gmail account) -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEmKAukUZni40sZANzHN2toLREzdoFAmYMFPwACgkQHN2toLRE zdqjqQgAsCLjBbVF505RJvIo2ZZqjWDjc0kn3pCs2+d9BHJNbd104CHUlb/TlbGL +P1yTDTP9IJoDH833SaLlohtVFBUQbWZmBSav/rSi/4ricXg8XXXDoYb+wPgcdSo 243qh43kjMzL6gU6f4aslCS1fHVL/LDUHiRdarLekKfPsWWEE1BR+qdk+WUJiEkU 09pcZsGG+6osVDP3/oTCkkMH9/vzY+l8zwy8I3rtMByjlhk90t37YUi1dn5vrvhF cSFkys+Um15Wnngb8W1yi4i/gfFYvHapn7KA1WaoeivbMtiJVL8XVWQiWf3Uzy+s w3Tl+sQ3S69fIajI9StfO60Qe5dSJQ=3D=3D =3Dw5DC -----END PGP SIGNATURE----- On Monday, April 1, 2024 at 5:16:54=E2=80=AFPM UTC-4 David A. Harding wrote= : > On 2024-03-28 10:04, Matt Corallo wrote: > > Please provide justification rather than simply saying "I like Bob!". > > Using only comments from the mailing list, the following appears to be > the candidate list along with the current support. Asterisks denote > candidates who indicated their willingness to accept the role. > > - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris Stewart[3], > Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon=20 > Black[11], > Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carvalho[16] > > - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], Michael > Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], John > Carvalho[16] > > - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],=20 > /dev/fd0[5][7], > Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carvalho[16] > > - Olaoluwa "Roasbeef" Osuntokun, recommended by Chris Stewart[3], John > C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine > Riard[12], Ava Chow[14] > > - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Keagan > McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Riard[12], > Ava Chow[14] > > - Michael Folkson* > > Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for "non-dev > triaging", Tonoski proposed himself[18] for "BIP editor", and Antoine > Riard[12] proposed Seccour for "decentralized PM". > > I searched the BIPs repo by commenter to see if any of the above > candidates had been especially active there, which is listed below as: > total PRs they commented on (number still open/number closed). > > - 21 (1/20) commenter:kanzure > - 3 (2/1) commenter:rubensomsen > - 15 (0/15) commenter:jonatack > - 18 (2/16) commenter:roasbeef > - 10 (6/4) commenter:Murchandamus > - 57 (6/51) commenter:michaelfolkson > > I'll also note that Osuntokun is the only member of the set to have a > merged BIP that they co-authored, although I believe there are far-along > draft BIPs for both Murch (terminology) and Somsen (Silent Payments). I > don't think this should be a requirement, but I do think it demonstrates > familiarity with the process. > > Speaking only for myself, I think all of the candidates above with > multiple recommendations from other community participants are fully > qualified for the role, so I'll only provide a detailed justification > for the person who would be my first pick: Murch is not only a > longstanding and broadly liked Bitcoin contributor, but (as Corallo > mentioned) he has worked on standardizing terminology through a draft > BIP. In addition, he provided an extremely detailed review of all 300 > pages of a draft of Mastering Bitcoin (3rd edition) and has reviewed > drafts of over 200 weekly Optech newsletters, in both cases > significantly improving the accuracy and comprehensibility of the > documentation. To me, that seems very similar to the work we'd ask him > to perform as a BIPs editor and it's something that he's already doing, > so I think there's an excellent fit of person to role. > > -Dave > > [1]=20 > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/=20 > > [2]=20 > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/=20 > > [3]=20 > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/= =20 > > [4]=20 > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/= =20 > > [5]=20 > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/= =20 > > [6]=20 > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/= =20 > > [7]=20 > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/= =20 > > [8]=20 > > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5...@mail.gmail.com/=20 > > [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/=20 > > [10]=20 > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/= =20 > > [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/ > [12]=20 > > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.= com/=20 > > [13]=20 > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/=20 > > [14]=20 > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/=20 > > [15]=20 > > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/ > [16]=20 > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/= =20 > > [17]=20 > > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+...@mail.gmail.com/=20 > > --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/= bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com. ------=_Part_18283_1245753081.1712067860825 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

+1 for=
Kanzure
RubenSomsen
Seccour
Jon Atack
Roasbeef
I would prefer having more (9+?) than less folks on this task, so = personal preferences are easily ignored and overwritten by the group majori= ty.

BIPs were intended as a means to collect ideas, not enforce = ideas.

I'd like to return to that.

- - NVK (temp gmai= l account)
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmK= AukUZni40sZANzHN2toLREzdoFAmYMFPwACgkQHN2toLRE
zdqjqQgAsCLjBbVF505RJvI= o2ZZqjWDjc0kn3pCs2+d9BHJNbd104CHUlb/TlbGL
+P1yTDTP9IJoDH833SaLlohtVFBU= QbWZmBSav/rSi/4ricXg8XXXDoYb+wPgcdSo
243qh43kjMzL6gU6f4aslCS1fHVL/LDUH= iRdarLekKfPsWWEE1BR+qdk+WUJiEkU
09pcZsGG+6osVDP3/oTCkkMH9/vzY+l8zwy8I3= rtMByjlhk90t37YUi1dn5vrvhF
cSFkys+Um15Wnngb8W1yi4i/gfFYvHapn7KA1Waoeiv= bMtiJVL8XVWQiWf3Uzy+s
w3Tl+sQ3S69fIajI9StfO60Qe5dSJQ=3D=3D
=3Dw5D= C
-----END PGP SIGNATURE-----

On Monday, April 1, 2024 at 5:16= :54=E2=80=AFPM UTC-4 David A. Harding wrote:
On 2024-03-28 10:04, Matt Corallo wrote:
> Please provide justification rather than simply saying "I lik= e Bob!".

Using only comments from the mailing list, the following appears to be
the candidate list along with the current support. Asterisks denote
candidates who indicated their willingness to accept the role.

- Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris S= tewart[3],
Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon=20
Black[11],
Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carvalho[16]

- Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], Michael
Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], John
Carvalho[16]

- Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],=20
/dev/fd0[5][7],
Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carvalho[16= ]

- Olaoluwa "Roasbeef" Osuntokun, recommended by Chris Stewart= [3], John
C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
Riard[12], Ava Chow[14]

- Mark "Murch" Erhardt*, recommended by Michael Folkson[6], K= eagan
McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Riard[12= ],
Ava Chow[14]

- Michael Folkson*

Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for "non-d= ev
triaging", Tonoski proposed himself[18] for "BIP editor"= , and Antoine
Riard[12] proposed Seccour for "decentralized PM".

I searched the BIPs repo by commenter to see if any of the above
candidates had been especially active there, which is listed below as:
total PRs they commented on (number still open/number closed).

- 21 (1/20) commenter:kanzure
- 3 (2/1) commenter:rubensomsen
- 15 (0/15) commenter:jonatack
- 18 (2/16) commenter:roasbeef
- 10 (6/4) commenter:Murchandamus
- 57 (6/51) commenter:michaelfolkson

I'll also note that Osuntokun is the only member of the set to have= a
merged BIP that they co-authored, although I believe there are far-alon= g
draft BIPs for both Murch (terminology) and Somsen (Silent Payments). = I
don't think this should be a requirement, but I do think it demonst= rates
familiarity with the process.

Speaking only for myself, I think all of the candidates above with
multiple recommendations from other community participants are fully
qualified for the role, so I'll only provide a detailed justificati= on
for the person who would be my first pick: Murch is not only a
longstanding and broadly liked Bitcoin contributor, but (as Corallo
mentioned) he has worked on standardizing terminology through a draft
BIP. In addition, he provided an extremely detailed review of all 300
pages of a draft of Mastering Bitcoin (3rd edition) and has reviewed
drafts of over 200 weekly Optech newsletters, in both cases
significantly improving the accuracy and comprehensibility of the
documentation. To me, that seems very similar to the work we'd ask= him
to perform as a BIPs editor and it's something that he's alread= y doing,
so I think there's an excellent fit of person to role.

-Dave

[1]=20
htt= ps://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/
[2]=20
https:/= /gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/
[3]=20
https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.= com/
[4]=20
https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.co= m/
[5]=20
https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.= com/
[6]=20
https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.= com/
[7]=20
https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.= com/
[8]=20
https://gnusha.org/pi/bitcoindev/CALeFG= L1-LKPWd7YRS110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/
[9] https://gnusha.org/pi/bitcoindev/ZgeP= Pvbf...@petertodd.org/
[10]=20
https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/<= /a>
[11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69= V@console/
[12]=20
https://gnusha.org/pi/bitcoindev/CALZp= t+E8DohYEJ9aO+FiF6+E...@mail.gmail.com/
[13]=20
https://g= nusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/
[14]=20
htt= ps://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/
[15]=20
https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7= 692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@proto= nmail.com/
[16]=20
https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.= com/
[17]=20
https://gnusha.org/pi/bitcoindev/= CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com.=
------=_Part_18283_1245753081.1712067860825-- ------=_Part_18282_1476111482.1712067860825--