Delivery-date: Tue, 02 Apr 2024 06:58:49 -0700 Received: from mail-yw1-f192.google.com ([209.85.128.192]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rref2-0000HW-4r for bitcoindev@gnusha.org; Tue, 02 Apr 2024 06:58:49 -0700 Received: by mail-yw1-f192.google.com with SMTP id 00721157ae682-61510f72bb3sf19757607b3.0 for ; Tue, 02 Apr 2024 06:58:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712066322; x=1712671122; 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=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=; b=Z6yNYMJGi7cKVTEg16ryOGpoIl8uiqQt2QUkq2GbHwgE/hGC55VhScefq6Jcv+qjuZ rJYYyU8hsowqiGzf6PcgAyqmv50TPhQYqAmYV0U5Yc9M/DrmwRgRkNxVL7moLF7jiyLe 8BpvucMBw7VvKLCiqew5DHNMBZMjAsjtgPpiJlCg4NnXbsT/1+ng7ndTIOEJ4ymMO/ZH 0KVqg8NVTW1AFsh7iN0tkv6iAjx6VJOzFP+qNVJWPDtFm2h0k1r1H+55vrnSTf/A7Ai8 wghWTp8txTAAliRUY5bPMXnK3QLWIO+ZIlLvH7O+Y64cFk/rZNZoWFQbpJktIkkBk9Tb 2tyA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712066322; x=1712671122; 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=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=; b=drs2Ru73aGQXB3OESO1BazMcEuEYKTZY+1PwQdjkYvSGPFAHHMsHY8t06Q7sFFedXy befuKPgZ3zlvYYKfpSJVY394ihTKVelfFO3zQhxQyYLAOOQ0AiVor2IJZMLmuDqAW/7y Qoq69dFKFdUgdyBdPJk9hSOIRNeuuX5mnCRjNkfjQlPEvVdr4W4/+RRCeZw5tDYXUYxd V3+XmxiV0O0AwHyMeK/S2xP0x6OVUs6TFhm1vu1iNf1+55H2lOV9wOkhmDzxszaLryPu h3QwKyWY+Tz7eBN0XnZIDxn3GD8teYSG+SfSbiyCadRooGBzPKaIPY9F5+18Qr3ziFP4 PXtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712066322; x=1712671122; 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=Zadsu5nyn5Oj/L9kcoO0DAA+l35vjiivJhfOh8fNr08=; b=QdoFqNKXbAjU/x6tgqTfFdC7Sa5rmTZXMcKR8UsuY6vYngEvLdtLTijs9v76IC/JbF rWdk8zxX2t5iS0StzttWKQiUYuLbNhPJUsFToU/+aROceXFL+UB9QPKNLXn5aKlne/0o 5OfnHiYEjq7dpNrwZiNGJN4QBt0efBA7YKrrvcY/ITHWABGGqLG6gYowDcwTB3FoxJD8 9Hu9x/dA2ep88kUIhzh0p9aUnvN2ERrGwVunnTYrgd+RwNo7qoRGdSDHwjeluP6OVhqw aronPMMfgLfuTOiljXl0sIHbdoO/XEw6q0+lX9lTNomRGfq2+dWKj0yRj6BMt7lU8I2E Nq9Q== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWVDcW7MA2IuiDYysg6DVAS84qvu1xXSvNcVjuLbf/W+91XpklpXzgKRUPo4dsRp1maLuX8tEEQbZpRsGP2Q4e48twE0Rk= X-Gm-Message-State: AOJu0YyY1HcalVltQ6fz6O0AIR7i/iCV1wk9yQPVJccab8EGNMeUI/Au 1tLhf51dvUWIOgP5nceTijrrHmH9g/WpUYl4qeZ+lInmlSR56OBH X-Google-Smtp-Source: AGHT+IFInNLcLWpBwdEIsgCfKYC4uLmrAZLloqiKhbYJxpq5hKUmx5GpRIV54/z9P30nl837X54snQ== X-Received: by 2002:a25:3546:0:b0:dcd:5635:5c11 with SMTP id c67-20020a253546000000b00dcd56355c11mr10849301yba.45.1712066321560; Tue, 02 Apr 2024 06:58:41 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:d8d7:0:b0:dcc:4b24:c0dd with SMTP id p206-20020a25d8d7000000b00dcc4b24c0ddls1607477ybg.0.-pod-prod-08-us; Tue, 02 Apr 2024 06:58:40 -0700 (PDT) X-Received: by 2002:a05:690c:24c:b0:614:2c5c:d275 with SMTP id ba12-20020a05690c024c00b006142c5cd275mr3247834ywb.4.1712066320285; Tue, 02 Apr 2024 06:58:40 -0700 (PDT) Received: by 2002:a05:690c:399:b0:609:3e5d:63d0 with SMTP id 00721157ae682-614306bf5bcms7b3; Tue, 2 Apr 2024 06:49:25 -0700 (PDT) X-Received: by 2002:a05:6902:2306:b0:dcc:50ca:e153 with SMTP id do6-20020a056902230600b00dcc50cae153mr3992633ybb.7.1712065763341; Tue, 02 Apr 2024 06:49:23 -0700 (PDT) Date: Tue, 2 Apr 2024 06:49:22 -0700 (PDT) From: /dev /fd0 To: Bitcoin Development Mailing List Message-Id: <16a728e9-e987-4e7b-bace-2629143d173fn@googlegroups.com> In-Reply-To: References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <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_46188_1726060605.1712065762908" 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_46188_1726060605.1712065762908 Content-Type: multipart/alternative; boundary="----=_Part_46189_192944896.1712065762908" ------=_Part_46189_192944896.1712065762908 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > Does it matter? The number that a proposal gets has no impact on > literally anything else. They could do it sequentially and it wouldn't > actually make a difference as long as there are no collisions. Process followed to assign the number started this whole debate recently=20 and creation of BINANA. Previous BIP editor refused to assign numbers to=20 some BIPs. Kanzure had [tweeted][0] asking users on twitter if a BIP should= =20 be assigned number. So I am curious what process exactly would be followed= =20 by new BIP editors. > For example, this was done when Luke was hacked - > all of his permissions were immediately removed as soon as the news came > out, and were only returned several months later once verified > communication with Luke were established and he was certain that his > GitHub account was no longer (at risk of being) compromised. Thanks for sharing. I wasn't aware of this. [0]: https://x.com/kanzure/status/1752663903715168280 /dev/fd0 floppy disk guy On Tuesday, April 2, 2024 at 8:22:16=E2=80=AFAM UTC Ava Chow wrote: > > > On 04/01/2024 07:55 PM, /dev /fd0 wrote: > > I think before we decide new BIP editors its important to discuss some= =20 > > things about the process itself: > >=20 > > 1. Quoting first paragraph from BIPs repo README: "People wishing to=20 > > submit BIPs, first should propose their idea or document to the=20 > > bitco...@lists.linuxfoundation.org mailing list (do not assign a=20 > > number - read BIP 2 for the full process). After discussion, please ope= n=20 > > a PR. After copy-editing and acceptance, it will be published here." > >=20 > > If Kanzure and Ruben are BIP editors, does it mean they can censor=20 > > someone from submitting BIPs? This question makes sense because they=20 > > will have control over the whole improvement process for "bitcoin" by= =20 > > being moderators for mailing list and BIP editors. > > If the only requirement is that a BIP shows up on the mailing list=20 > first, then they can already censor them. Having them as BIP editors=20 > wouldn't change that. It's not clear to me that this requirement is=20 > strictly enforced anyways. > > Furthermore, they would not have the permissions to delete PRs or=20 > issues, so once a PR is opened, even if closed, would still be there.=20 > The status quo w.r.t that would not be any different. At worst, they=20 > could refuse to assign a BIP a number, but that's no different than what= =20 > already happens today. In fact, the situation would likely be better=20 > because there would be multiple BIP editors and so what goes into the=20 > repo is not at the whim of a single person. > > > 2. How are numbers going to be assigned to BIPs? > > Does it matter? The number that a proposal gets has no impact on=20 > literally anything else. They could do it sequentially and it wouldn't=20 > actually make a difference as long as there are no collisions. > > > 3. Will there be copy of BIPs and pull requests maintained elsewhere=20 > > like bitcoin core? > > I'm not sure why this is relevant to this discussion, but presumably=20 > there already are, and if there aren't, you can do it yourself. It's=20 > just like any other repo on GitHub. > > > 4. What are the expectations from new BIP editors? In what situation do= =20 > > we look for next BIP editors or in other words, what will be the proces= s=20 > > to remove an editor if lot of people are unhappy with their work? > > The expectations are as outlined to BIP 2, and that they are actually=20 > active. The situation for looking for new BIP editors in the future is=20 > presumably similar to the one we are in currently - people who write=20 > BIPs are frustrated with things taking a long time to be merged with the= =20 > root cause being slow response times from the current editor. The=20 > process would likely be very similar: names are proposed, there is=20 > discussion about those people, and eventually some are added. > > As for removal, this has not been something we've ever done before, so=20 > the process for this is undefined. However, it would presumably be a=20 > similar procedure as for adding someone. It begins with someone raising= =20 > a complaint about one of the editors on this mailing list or some other= =20 > place a discussion, and a community discussion commences about whether=20 > or not to remove them. > > There are certainly situations where one of the GitHub org owners may=20 > take emergency action and remove a maintainer's privileges. This is only= =20 > done when there is a clear danger than the account may do something=20 > malicious, and the privileges would be returned if there is clarity that= =20 > it is safe to do so. For example, this was done when Luke was hacked -=20 > all of his permissions were immediately removed as soon as the news came= =20 > out, and were only returned several months later once verified=20 > communication with Luke were established and he was certain that his=20 > GitHub account was no longer (at risk of being) compromised. > > Ava > > >=20 > > /dev/fd0 > > floppy disk guy > >=20 > > On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Harding wro= te: > >=20 > > On 2024-03-28 10:04, Matt Corallo wrote: > > > Please provide justification rather than simply saying "I like > > Bob!". > >=20 > > 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. > >=20 > > - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris Stewart[3], > > Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon > > Black[11], > > Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carvalho[16] > >=20 > > - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], Michael > > Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], John > > Carvalho[16] > >=20 > > - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3], > > /dev/fd0[5][7], > > Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carvalho[16] > >=20 > > - 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] > >=20 > > - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Keagan > > McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Riard[12], > > Ava Chow[14] > >=20 > > - Michael Folkson* > >=20 > > 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". > >=20 > > 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). > >=20 > > - 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 > >=20 > > 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. > >=20 > > 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. > >=20 > > -Dave > >=20 > > [1] > > https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.com/ > > > > > > [2] > > https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/ > > > > > > [3] > > https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com= /=20 > > > > > [4] > > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com= /=20 > > > > > [5] > > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com= /=20 > > > > > [6] > > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com= /=20 > > > > > [7] > > 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 > < > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazRA= 5...@mail.gmail.com/=20 > > > > > [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/ > > > > > [10] > > 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 > < > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.= com/=20 > > > > > [13] > > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/ > > > > > > [14] > > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/ > > > > > > [15] > >=20 > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/=20 > < > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh= 7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@prot= onmail.com/ > > > > [16] > > 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 > < > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qr= st+...@mail.gmail.com/=20 > > > > >=20 > > --=20 > > You received this message because you are subscribed to the Google=20 > > Groups "Bitcoin Development Mailing List" group. > > To unsubscribe from this group and stop receiving emails from it, send= =20 > > an email to bitcoindev+...@googlegroups.com=20 > > . > > To view this discussion on the web visit=20 > >=20 > https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c= 0e0eb047n%40googlegroups.com=20 > < > https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c= 0e0eb047n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter > >. > > --=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/16a728e9-e987-4e7b-bace-2629143d173fn%40googlegroups.com. ------=_Part_46189_192944896.1712065762908 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable >=C2=A0 Does it matter? The number that a proposal gets has no impact on
> = literally anything else. They could do it sequentially and it wouldn't
> actually make a difference as long as there are no collisions.
Process followed to assign the number started this whole deb= ate recently and creation of BINANA. Previous BIP editor refused to assign = numbers to some BIPs. Kanzure had [tweeted][0] asking users on twitter if a= BIP should be assigned number. So I am curious what process exactly would = be followed by new BIP editors.

> For example= , this was done when Luke was hacked -
> all of his permissions wer= e immediately removed as soon as the news came
> out, and were only= returned several months later once verified
> communication with L= uke were established and he was certain that his
> GitHub account w= as no longer (at risk of being) compromised.

Thanks fo= r sharing. I wasn't aware of this.

[0]:=C2=A0htt= ps://x.com/kanzure/status/1752663903715168280

/d= ev/fd0
floppy disk guy

On Tuesday, April 2, 2024 at= 8:22:16=E2=80=AFAM UTC Ava Chow wrote:


On 04/01/2024 07:55 PM, /dev /fd0 wrote:
> I think before we decide new BIP editors its important to discuss = some=20
> things about the process itself:
>=20
> 1. Quoting first paragraph from BIPs repo README: "People wis= hing to=20
> submit BIPs, first should propose their idea or document to the=20
> bitco...@lists.linuxfou= ndation.org mailing list (do not assign a=20
> number - read BIP 2 for the full process). After discussion, pleas= e open=20
> a PR. After copy-editing and acceptance, it will be published here= ."
>=20
> If Kanzure and Ruben are BIP editors, does it mean they can censor= =20
> someone from submitting BIPs? This question makes sense because th= ey=20
> will have control over the whole improvement process for "bit= coin" by=20
> being moderators for mailing list and BIP editors.

If the only requirement is that a BIP shows up on the mailing list=20
first, then they can already censor them. Having them as BIP editors=20
wouldn't change that. It's not clear to me that this requiremen= t is=20
strictly enforced anyways.

Furthermore, they would not have the permissions to delete PRs or=20
issues, so once a PR is opened, even if closed, would still be there.= =20
The status quo w.r.t that would not be any different. At worst, they=20
could refuse to assign a BIP a number, but that's no different than= what=20
already happens today. In fact, the situation would likely be better=20
because there would be multiple BIP editors and so what goes into the= =20
repo is not at the whim of a single person.

> 2. How are numbers going to be assigned to BIPs?

Does it matter? The number that a proposal gets has no impact on=20
literally anything else. They could do it sequentially and it wouldn= 9;t=20
actually make a difference as long as there are no collisions.

> 3. Will there be copy of BIPs and pull requests maintained elsewhe= re=20
> like bitcoin core?

I'm not sure why this is relevant to this discussion, but presumabl= y=20
there already are, and if there aren't, you can do it yourself. It&= #39;s=20
just like any other repo on GitHub.

> 4. What are the expectations from new BIP editors? In what situati= on do=20
> we look for next BIP editors or in other words, what will be the p= rocess=20
> to remove an editor if lot of people are unhappy with their work?

The expectations are as outlined to BIP 2, and that they are actually= =20
active. The situation for looking for new BIP editors in the future is= =20
presumably similar to the one we are in currently - people who write=20
BIPs are frustrated with things taking a long time to be merged with th= e=20
root cause being slow response times from the current editor. The=20
process would likely be very similar: names are proposed, there is=20
discussion about those people, and eventually some are added.

As for removal, this has not been something we've ever done before,= so=20
the process for this is undefined. However, it would presumably be a=20
similar procedure as for adding someone. It begins with someone raising= =20
a complaint about one of the editors on this mailing list or some other= =20
place a discussion, and a community discussion commences about whether= =20
or not to remove them.

There are certainly situations where one of the GitHub org owners may= =20
take emergency action and remove a maintainer's privileges. This is= only=20
done when there is a clear danger than the account may do something=20
malicious, and the privileges would be returned if there is clarity tha= t=20
it is safe to do so. For example, this was done when Luke was hacked -= =20
all of his permissions were immediately removed as soon as the news cam= e=20
out, and were only returned several months later once verified=20
communication with Luke were established and he was certain that his=20
GitHub account was no longer (at risk of being) compromised.

Ava

>=20
> /dev/fd0
> floppy disk guy
>=20
> On Monday, April 1, 2024 at 9:16:54=E2=80=AFPM UTC David A. Hardin= g wrote:
>=20
> On 2024-03-28 10:04, Matt Corallo wrote:
> > Please provide justification rather than simply saying &= quot;I like
> Bob!".
>=20
> Using only comments from the mailing list, the following appea= rs to be
> the candidate list along with the current support. Asterisks d= enote
> candidates who indicated their willingness to accept the role.
>=20
> - Bryan "Kanzure" Bishop, recommended by Ava Chow[1]= , Chris Stewart[3],
> Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon
> Black[11],
> Antoine Riard[12], Murch[13], Antoine Poinsot[15], John Carval= ho[16]
>=20
> - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3], = Michael
> Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15],= John
> Carvalho[16]
>=20
> - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],
> /dev/fd0[5][7],
> Brandon Black[11], Antoine Riard[12], Ava Chow[14], John Carva= lho[16]
>=20
> - Olaoluwa "Roasbeef" Osuntokun, recommended by Chri= s Stewart[3], John
> C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
> Riard[12], Ava Chow[14]
>=20
> - Mark "Murch" Erhardt*, recommended by Michael Folk= son[6], Keagan
> McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine Ri= ard[12],
> Ava Chow[14]
>=20
> - Michael Folkson*
>=20
> Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for &q= uot;non-dev
> triaging", Tonoski proposed himself[18] for "BIP edi= tor", and Antoine
> Riard[12] proposed Seccour for "decentralized PM".
>=20
> I searched the BIPs repo by commenter to see if any of the abo= ve
> candidates had been especially active there, which is listed b= elow as:
> total PRs they commented on (number still open/number closed).
>=20
> - 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
>=20
> I'll also note that Osuntokun is the only member of the se= t 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 Pay= ments). I
> don't think this should be a requirement, but I do think i= t
> demonstrates
> familiarity with the process.
>=20
> 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 ju= stification
> for the person who would be my first pick: Murch is not only a
> longstanding and broadly liked Bitcoin contributor, but (as Co= rallo
> 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 re= viewed
> 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&#= 39;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.
>=20
> -Dave
>=20
> [1]
> https://gnusha.org/pi/b= itcoindev/2092f7ff-4860-47f8...@achow101.com/
> <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101.c= om/>
> [2]
> https://gnusha.org/pi/bitcoi= ndev/9288df7b-f2e9-4106...@dashjr.org/
> <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.org/>
> [3]
> https://gnusha.= org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/ <htt= ps://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegroups.com/&g= t;
> [4]
> https://gnusha.= org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/ <http= s://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.com/>= ;
> [5]
> https://gnusha.= org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/ <htt= ps://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.com/&g= t;
> [6]
> https://gnusha.= org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/ <htt= ps://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.com/&g= t;
> [7]
> https://gnusha.= org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/ <htt= ps://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.com/&g= t;
> [8]
> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7Y= RS110ut8tX=3DwruqgLEazRA5...@mail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3Dwr= uqgLEazRA5...@mail.gmail.com/>
> [9] https://gnusha.org/pi/bitcoindev/ZgePP= vbf...@petertodd.org/
> <https://gnusha.org/pi/bitco= indev/ZgePPvbf...@petertodd.org/>
> [10]
> https://gnusha.org= /pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/ <https://gnusha= .org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.com/>
> [11] https://gnusha.org/pi/bitcoindev/ZgWRu3= 2FXzqqg69V@console/
> <https://gnusha.org/pi/bitcoindev/ZgWRu32= FXzqqg69V@console/>
> [12]
> https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.c= om/ <https://gnusha.org/pi/bitcoin= dev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gmail.com/>
> [13]
> https://gnusha.org/pi/bitcoind= ev/53a0015c-b76a-441a...@murch.one/
> <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/&g= t;
> [14]
> https://gnusha.org/pi/b= itcoindev/ae482890-bce3-468f...@achow101.com/
> <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.c= om/>
> [15]
> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSB= Xsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo= =3D@protonmail.com/ <https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmI= BVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH= 4gwU1c2jS4xojo=3D@protonmail.com/>
> [16]
> https://gnusha.= org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/ <htt= ps://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.com/&g= t;
> [17]
> https://gnusha.org/pi/bitcoindev/CAMHHROw9= mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo= 76PdqwJU=3D=3DYJMvd9Qrst+...@mail.gmail.com/>
>=20
> --=20
> You received this message because you are subscribed to the Google= =20
> Groups "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, = send=20
> an email to bitcoindev+= ...@googlegroups.com=20
> <mailto:bitcoindev+.= ..@googlegroups.com>.
> To view this discussion on the web visit=20
> https://groups.google.com/d/msgid/b= itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com <= https://groups.google.com/d/msgid/b= itcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c0e0eb047n%40googlegroups.com?utm_medi= um=3Demail&utm_source=3Dfooter>.

--
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/16a728e9-e987-4e7b-bace-2629143d173fn%40googlegroups.com.=
------=_Part_46189_192944896.1712065762908-- ------=_Part_46188_1726060605.1712065762908--