From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 01 Apr 2024 16:56:50 -0700 Received: from mail-yw1-f191.google.com ([209.85.128.191]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rrRWD-0007V6-MN for bitcoindev@gnusha.org; Mon, 01 Apr 2024 16:56:50 -0700 Received: by mail-yw1-f191.google.com with SMTP id 00721157ae682-611e89cf3b5sf75503987b3.3 for ; Mon, 01 Apr 2024 16:56:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712015803; x=1712620603; 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=2NbOzjEwthKf55k/WWSniIxOAIrsg0Xc5N1mkrKZ5OE=; b=aYFiEYlA4094k4rwu8ut1uDv5xQ0X/XEG3sbmzbqAF1RjpSpfwIxk54OEZPncPXWb5 QNV4K1SolGklXCi9WcQiEBLVRoDNeUR0tfx9WUowesLSQ3dzY+6JXHP5yUkopvicWXEs n6YbRM4OiVn3/LGsc3NmWrMLtp8Rwb3fryXG6BYZgwh0wkNeLF7WRnfAad88RcgMV3tu UDozA+0n5EGtq0BcmFuJGeQi87RUFz4CvDpu5/7ge1auSGnwA6kItB9/k5yLRigqsOd9 onDsCS8I1CKL6AvNly6oNPDciyqK8UmvObX5GMj+StKCHzWKbc13XjBGlDV1MMSqB4rz jm2Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712015803; x=1712620603; 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=2NbOzjEwthKf55k/WWSniIxOAIrsg0Xc5N1mkrKZ5OE=; b=UES0+TvxJ90aWaBibk6F6zWRiPy7WwyzeXza7lOK/USziJ0kZpp0rY8W53GKOaD0dr 0v7Dp4BVIPOD6bGn++dZQ3w6MI/HtGpayXcLEXVxN8K8X+6dNbMGL6FM4gaferVKe4Fx +QoFDPwETYvOfVF2mzBmEhzHyunkpI41pIOm7XJlSV6hG/dwXuy0YXn0v2OAqWnOa+nI 9MFiLhvK840EM0xTqnHuNkE9ux0gKvpstjctzTXpP39rQUgDgAhP+bxFAX3kCFJ9Mufj CaC/K09Lbiu+NDX9Fx7D4L0rUDHLyq+ir9UiSp19xX6MXDgCJHo7bxzvs/q3IFxpS0gr SEdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712015803; x=1712620603; 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=2NbOzjEwthKf55k/WWSniIxOAIrsg0Xc5N1mkrKZ5OE=; b=XrgRsWVTNmrZR/wBxgkHN67WgmQBH/f++OUgEdA/ANtjE4aJHuSICcYvnaaE23WAwF YceHTtZ2aaCpxFokh13JvFNTuB4fh4+chaT80WsRZjNTVDEUZcJVkkTNH7YmdTMqZK/Y uTJV76p9AVK3GPfQyMMjUXUoXpwXsNJlRG1yJDMw6u22yOtr+/PTD+GMOa6ALVwnIn1i twd3N/OtyNmLXAEtluwQlj0bMC9qfxe6ynDaR/rB5pjzwQU/pPHB2KzQatUWIApVuiyS PvLgn1c/wf5tZ6L/fTyMxM7TktJeXyG07miULeZWolQauyY9k4DYQNrhQAMZ7NUOYqxL VcVw== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCVZtsHdnt3w/LeB1ErQYU/iRymZG6ajAtlUY884vxs3sCwj97SSWKiFZvlUrk/NvwuCrw0Fi3hQC19eCW8go2GcKmpl21E= X-Gm-Message-State: AOJu0YyLGx2MeGBjX9gE/ffUaFZuloyHWwEhkJUMmjVorWmWjaKa6auB ONwcq/VML/eTyauVA35MUtwj72jQyif9UPyMFW5ptXuLcb9i6FjL X-Google-Smtp-Source: AGHT+IEIBEMKivwGrB+cvNEOcaKzesrJnJ6MZKifqoPEv+JsU56XwWmbwYqaiP7Qy3xQfwaNWUiB3g== X-Received: by 2002:a25:cd42:0:b0:db5:3b32:b1c3 with SMTP id d63-20020a25cd42000000b00db53b32b1c3mr7812417ybf.21.1712015802964; Mon, 01 Apr 2024 16:56:42 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:69c4:0:b0:dc7:465d:fb81 with SMTP id e187-20020a2569c4000000b00dc7465dfb81ls1346873ybc.2.-pod-prod-09-us; Mon, 01 Apr 2024 16:56:42 -0700 (PDT) X-Received: by 2002:a05:690c:dcf:b0:611:22f9:66a4 with SMTP id db15-20020a05690c0dcf00b0061122f966a4mr1698501ywb.8.1712015801910; Mon, 01 Apr 2024 16:56:41 -0700 (PDT) Received: by 2002:a05:690c:102:b0:611:2a20:d0cc with SMTP id 00721157ae682-614558bcb37ms7b3; Mon, 1 Apr 2024 16:55:12 -0700 (PDT) X-Received: by 2002:a05:6902:2841:b0:dcb:bc80:8333 with SMTP id ee1-20020a056902284100b00dcbbc808333mr3371950ybb.13.1712015711200; Mon, 01 Apr 2024 16:55:11 -0700 (PDT) Date: Mon, 1 Apr 2024 16:55:10 -0700 (PDT) From: /dev /fd0 To: Bitcoin Development Mailing List Message-Id: 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_16318_364283349.1712015710782" X-Original-Sender: alicexbtong@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: -0.5 (/) ------=_Part_16318_364283349.1712015710782 Content-Type: multipart/alternative; boundary="----=_Part_16319_2045201215.1712015710782" ------=_Part_16319_2045201215.1712015710782 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think before we decide new BIP editors its important to discuss some=20 things about the process itself: 1. Quoting first paragraph from BIPs repo README: "People wishing to submit= =20 BIPs, first should propose their idea or document to the=20 bitcoin-dev@lists.linuxfoundation.org mailing list (do not assign a number= =20 - read BIP 2 for the full process). After discussion, please open a PR.=20 After copy-editing and acceptance, it will be published here." If Kanzure and Ruben are BIP editors, does it mean they can censor someone= =20 from submitting BIPs? This question makes sense because they will have=20 control over the whole improvement process for "bitcoin" by being=20 moderators for mailing list and BIP editors. 2. How are numbers going to be assigned to BIPs? 3. Will there be copy of BIPs and pull requests maintained elsewhere like= =20 bitcoin core? 4. What are the expectations from new BIP editors? In what situation do we= =20 look for next BIP editors or in other words, what will be the process to=20 remove an editor if lot of people are unhappy with their work? /dev/fd0 floppy disk guy On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC 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/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com. ------=_Part_16319_2045201215.1712015710782 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think before we decide new BIP editors its important to discuss some thin= gs about the process itself:

1. Quoting first paragrap= h from BIPs repo README: "People wishing to submit BIPs, first should propo= se their idea or document to the bitcoin-dev@lists.linuxfoundation.org mail= ing list (do not assign a number - read BIP 2 for the full process). After = discussion, please open a PR. After copy-editing and acceptance, it will be= published here."

If Kanzure and Ruben are BIP e= ditors, does it mean they can censor someone from submitting BIPs? This que= stion makes sense because they will have control over the whole improvement= process for "bitcoin" by being moderators for mailing list and BIP editors= .

2. How are numbers going to be assigned to BIP= s?

3. Will there be copy of BIPs and pull reques= ts maintained elsewhere like bitcoin core?

4. Wh= at are the expectations from new BIP editors? In what situation do we look = for next BIP editors or in other words, what will be the process to remove = an editor if lot of people are unhappy with their work?

/dev/fd0
floppy disk guy

On Monday, April 1, 2024= at 9:16:54=E2=80=AFPM UTC David A. Harding wrote:
On 2024-03-28 10:04, Matt Corallo wro= te:
> 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/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com.=
------=_Part_16319_2045201215.1712015710782-- ------=_Part_16318_364283349.1712015710782--