Delivery-date: Tue, 02 Apr 2024 07:31:07 -0700 Received: from mail-oo1-f55.google.com ([209.85.161.55]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rrfAI-0000ej-5k for bitcoindev@gnusha.org; Tue, 02 Apr 2024 07:31:07 -0700 Received: by mail-oo1-f55.google.com with SMTP id 006d021491bc7-5a5547dbbc3sf6180768eaf.2 for ; Tue, 02 Apr 2024 07:31:05 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1712068260; cv=pass; d=google.com; s=arc-20160816; b=uMxEolko2H31yY+SI22ETGy48OmMIwR3pGR1788HCCwBBU+IiJZUdZNIzDXW120luT cVabHZIWS3lsdA5b4oV8k6L+Rpag/y9RDyDZ2G229k9bp0tPFFQuGvKUXY7k6DvQC+08 dUQ9DGEifB8+PDZuIh3aWoZRG4LrhXRZeG1BjsE/+EYZVT5DKUcWAWEjmdYUV8SEFkir 6PtC6Vx9mH+OOXNvE4TMGee0luocLDKp/ZFXqUpEzGj6HIuj5e5o/+BdK6XMupMrdIRo UfmtEatytjDQbc582cYzBug1M/axhUIKdbed9dCyWfQIC0EJYTzjjbU12uGx+xc65b20 d+6g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:content-transfer-encoding :mime-version:message-id:references:in-reply-to:user-agent:subject :to:from:date:sender:dkim-signature; bh=YhK2otL27r2kT+yFEPK//LpNqDF/b0ip0wr7vG0jMgY=; fh=NOJTVD3Sx6wvtwP5N7GZ6dbfyWcM490XyR4/tfvAGtk=; b=Cih/Ucw2SAN9hbgHwOcXDvnM3MWFTPDZOPO7BnJVUljHCwH5uL1HF2jGFAgfKT+wOG DCm9zVITgiRQsMNtoVJXwLZ/z4mmHU4vlHk8cJHcMHHCNipLWUx373UnmTeEtUw6xp3K Da12rEp64+z0Hs03MwfjkuX62EARFihFpsmTuxSBZX6A/UzPFkx5mrnoSuwC9yHyOBEu FniiZ6gXstw240ZAdm9OQZZaSF4AKu4qpO2WWLjTLC9Q/QNonHpPLq3uXtG5vPzqXQjS frsKVqiZfmVbMTrpPZbbae7j+IcQ1pAiXtSD7PPPJ0vZ8mMufqzge4AL9ASmmaD+C172 xgGw==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass (test mode) header.i=@dashjr.org header.s=zinan header.b=n+g70YpV; spf=pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) smtp.mailfrom=luke@dashjr.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dashjr.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712068260; x=1712673060; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:mime-version:message-id :references:in-reply-to:user-agent:subject:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=YhK2otL27r2kT+yFEPK//LpNqDF/b0ip0wr7vG0jMgY=; b=qsIAolv3mdfwmfbgiMn7csjATvxT5t0EMZMbOIRMQDhtw2QLgPLQLD/y98ZCniBCSu +7szogM6VKvjlB6bm6Fb6PXCNR/Mquu+ggh0C4dmS2SKwwMSqZMPi+vZzb/wbH53yZxp YOlLC/mp886aAR+4NFLOLe2jX3+PoXDT2KGGzFMqLHDoSk2ZHxWmBx53mDqJFGyXV9+e uoKV6q0yUGz0FZVWWzB5YV36Qsrnu0QHftC2GeLVIqDm2QTxBbTy4Lvb8UopsRWlhMKc AZY1fiYBqo+LuItPNpaTr47PVAEoMXoRIGtHeA/IswcvCOvACDp/rJ+MbezmrXKUDWQP ibhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712068260; x=1712673060; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:content-transfer-encoding:mime-version:message-id :references:in-reply-to:user-agent:subject:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=YhK2otL27r2kT+yFEPK//LpNqDF/b0ip0wr7vG0jMgY=; b=m7gvWn/VzMAdt/GH01JxFl+aeES9k/zJEI+VWhz+ABLFX1QnBQxxhX34jSSlnxzPMQ jOyYMArGjcHmU0PAGUOLRXZzAllLpTR+VL1mpjMu33qHeCMfk4/BC8B8/B5zLPIc8rA5 2tEwLskteIOoiuU8sVlF4+/bQ0hhX9M7t59/WtZrIXtzNwQ+yW79b9mppNdYFy3eK5ks /xzJKYoUdOOp55ubC1ZHkJCUCsx9qJCMGMg2eXS+Q6Dlcs26Y+Rvzuif4azQqvnYpe6+ /NBmWuxiBET5S14kxMA1PvUZ2YlVJSTgcw6J2KuNL6xKzQcSDKzr5524SJYa75tbwKoS nP6A== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCWVdxl1d3LdJmEgPTObx7zISOTanzjMIr1Id90wOOqNzojNSO6X5y10jto8hz2iCgUQkMDElhOGkvismeilqbjOD+nUpow= X-Gm-Message-State: AOJu0Yw/Aye5yMxa+9zxgTo7Bld1YlXNNDZ4UqO2wsA+TioaARiZlUav OU6vkfVwOhaNHME2cC4O7y0+M7oA+0rX38OMr3bzQGZ4O1xayAhZ X-Google-Smtp-Source: AGHT+IGy+qa+0E+h4kxmYHEHxYDNgjb9uGIDUFolzFjFpCukG5so2cX0TVbMnUrnMXQofyN9ZMdmDw== X-Received: by 2002:a05:6870:6108:b0:22e:7b39:bc52 with SMTP id s8-20020a056870610800b0022e7b39bc52mr1266860oae.17.1712068258434; Tue, 02 Apr 2024 07:30:58 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:6870:780a:b0:22a:b2ba:b4cf with SMTP id hb10-20020a056870780a00b0022ab2bab4cfls507317oab.0.-pod-prod-08-us; Tue, 02 Apr 2024 07:30:57 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCXKj56QrIUBoXxwBzZeqQ3H+d52Y58eBQzuEW6K7WgrqalJpkqElucKePHKFbzsvMqjEw4rxnGNAy4sCZwyX4KXw3tQ3fNUaZQzMqw= X-Received: by 2002:a05:6870:ac0b:b0:220:9f66:4fdf with SMTP id kw11-20020a056870ac0b00b002209f664fdfmr490182oab.9.1712068257580; Tue, 02 Apr 2024 07:30:57 -0700 (PDT) Received: by 2002:a05:6808:219c:b0:3c3:cc09:ef6d with SMTP id 5614622812f47-3c3ef57ad9emsb6e; Tue, 2 Apr 2024 07:28:45 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWAjg1Ch0NqRSrSn9NJQaLzuZPwlUWpZy4E9D4cLDqJ645MbdSfMvQtGq/7tg73fxeT+1NR+gVf7bH2jk2FODpAmzihWWospimZ+PE= X-Received: by 2002:a05:6871:520a:b0:22e:8907:e7bf with SMTP id ht10-20020a056871520a00b0022e8907e7bfmr583859oac.40.1712068124410; Tue, 02 Apr 2024 07:28:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1712068124; cv=none; d=google.com; s=arc-20160816; b=yQ3K6MJm/Q1qRfj3cA/qkiEqfILIceEfYLlj4PMS6yWYYJBnnfHpnjW9O+n/Sv2+zn Czmsr0SCaI6E7y6P6nUR45+QfgwJy+WlU9bD9JWUrPkj+rHbbTBHaux+LLj3KR1vlW+t jmKP5RYLrLp9Fnf1gjDJSMe3KI8wPNZrZOh9GY84+frq+Kuqav/BDvgqqGOCwoHaqkyi 0Qi0FabaVUihfB5SrwTJ3c0rZTeohqb72I1qpNbLhFnkpgSvLwMsgNI0BcIK06/wNETq yyAzS6fNsIP/nUiDTaWOemJfSQfx1P/6q0T8ANNsIFA8cuTDOTuqPl7SlbwrxGh/hppL OvAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:message-id:references :in-reply-to:user-agent:subject:to:from:date:dkim-signature; bh=KeFxW5S2CZPnBYQN3lP/CSxwVziv1vykvCWWWe81z18=; fh=kh+jsPuvlD1rducGId1VCRTYoySQDOGqwHdZzgwawv8=; b=g7pgbzufs5qVGrR7bGTUlPr73+4zfaaBjrmtA4rHX6yPiRalQGXxrCgVihaEQ+iXW1 q7+TwyrP9t886hY3l/MKR+0/5/VJ/mMnsx9Vtu838WLzmJBJiMGzqRfiPXzyAUKJwNuD w415wBbUTrgbpSNL0wtk3KJiA7xDYtS5FSrpi/9mJ6FGdxg5geeC+5RIq4Torpx2eYfm CP/cjgLZ2iXizdWiiNluHw6R3QxWtPSMu3rzOG164F2aEOeTxXmYoyLHFBdExAuFeb5l CrAOwnYj9C2Gjucvcm5JSvdCKbwab7I33t8plOS/2sb2h2MljIan42WQABJyT4cij2+h 3jKQ==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass (test mode) header.i=@dashjr.org header.s=zinan header.b=n+g70YpV; spf=pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) smtp.mailfrom=luke@dashjr.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dashjr.org Received: from zinan.dashjr.org (zinan.dashjr.org. [192.3.11.21]) by gmr-mx.google.com with ESMTP id p12-20020a05683019cc00b006e6c1c91f24si866729otp.1.2024.04.02.07.28.43 for ; Tue, 02 Apr 2024 07:28:44 -0700 (PDT) Received-SPF: pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) client-ip=192.3.11.21; Received: from [127.0.0.1] (unknown [172.58.30.138]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id A6B2B2219F0; Tue, 2 Apr 2024 14:28:35 +0000 (UTC) X-Hashcash: 1:23:240402:bitcoindev@googlegroups.com::2BVNRXRtayYiJAUT:kffG X-Hashcash: 1:23:240402:alicexbtong@gmail.com::fz1mx0f+H66dElmC:mcvo Date: Tue, 02 Apr 2024 08:28:26 -0600 From: Luke Dashjr To: bitcoindev@googlegroups.com, /dev /fd0 , Bitcoin Development Mailing List Subject: Re: [bitcoindev] Re: Adding New BIP Editors User-Agent: K-9 Mail for Android In-Reply-To: <16a728e9-e987-4e7b-bace-2629143d173fn@googlegroups.com> 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> <16a728e9-e987-4e7b-bace-2629143d173fn@googlegroups.com> Message-ID: <64FDB7CF-CBFB-416D-8BCF-2DC50CD2E4B7@dashjr.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----4OW0HPXMT6P3O7AMS0YXSQ1HZVQCNW Content-Transfer-Encoding: 7bit X-Original-Sender: luke@dashjr.org X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass (test mode) header.i=@dashjr.org header.s=zinan header.b=n+g70YpV; spf=pass (google.com: domain of luke@dashjr.org designates 192.3.11.21 as permitted sender) smtp.mailfrom=luke@dashjr.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=dashjr.org 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.7 (/) ------4OW0HPXMT6P3O7AMS0YXSQ1HZVQCNW Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No, there was no such refusal. The ONLY issue at hand with regard to more B= IP editors is that I don't have time to keep up with it by myself. If your = goal is anything else, please sit this discussion out (aside from perhaps r= easonable objections to new editors). BIP number assignments are trivial an= d not a concern. It seems there's an attempt to take advantage of the need for more BIP edit= ors to change or bypass the BIP process without proper procedures followed.= While there may be arguments for improving the BIP process, that is unrela= ted and would need to go through a BIP, not simply fiat of a new editor. An= y potential new editor will need to follow the BIP process as it currently = is defined until such a new BIP is accepted. Luke On April 2, 2024 7:49:22 AM CST, /dev /fd0 wrote: >> 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 shoul= d=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 op= en=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 d= o=20 >> > we look for next BIP editors or in other words, what will be the proce= ss=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 wr= ote: >> >=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.co= m/=20 >> > >> > >> > [4] >> > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.co= m/=20 >> > >> > >> > [5] >> > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.co= m/=20 >> > >> > >> > [6] >> > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.co= m/=20 >> > >> > >> > [7] >> > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.co= m/=20 >> > >> > >> > [8] >> >=20 >> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazR= A5...@mail.gmail.com/=20 >> < >> https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLEazR= A5...@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_oSBXsuiz= h7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@pro= tonmail.com/=20 >> < >> https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuiz= h7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@pro= tonmail.com/ >> > >> > [16] >> > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.co= m/=20 >> > >> > >> > [17] >> >=20 >> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Q= rst+...@mail.gmail.com/=20 >> < >> https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Q= rst+...@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-9b1= c0e0eb047n%40googlegroups.com=20 >> < >> https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1= c0e0eb047n%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 = email 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. --=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/64FDB7CF-CBFB-416D-8BCF-2DC50CD2E4B7%40dashjr.org. ------4OW0HPXMT6P3O7AMS0YXSQ1HZVQCNW Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No, there was no such refusal. T= he ONLY issue at hand with regard to more BIP editors is that I don't have = time to keep up with it by myself. If your goal is anything else, please si= t this discussion out (aside from perhaps reasonable objections to new edit= ors). BIP number assignments are trivial and not a concern.

It seems= there's an attempt to take advantage of the need for more BIP editors to c= hange or bypass the BIP process without proper procedures followed. While t= here may be arguments for improving the BIP process, that is unrelated and = would need to go through a BIP, not simply fiat of a new editor. Any potent= ial new editor will need to follow the BIP process as it currently is defin= ed until such a new BIP is accepted.

Luke


On April 2, 2024 7:49:22 AM CST, /dev /fd0 = <alicexbtong@gmail.com> wrote:
>  Does it matter? The number that a proposal gets has no impact on
> li= terally 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 re= cently and creation of BINANA. Previous BIP editor refused to assign number= s to some BIPs. Kanzure had [tweeted][0] asking users on twitter if a BIP s= hould be assigned number. So I am curious what process exactly would be fol= lowed by new BIP editors.

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

Thanks for sharing. I was= n't aware of this.

[0]: https://x.com/kanzure/s= tatus/1752663903715168280

/dev/fd0
flopp= y disk guy

On Tuesday, April 2, 2024 at 8:22:16=E2=80=AFAM UTC Av= a 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.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 "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 wha= t=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 elsewhe= re=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 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 onl= y=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 "= 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 St= ewart[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 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], Ke= agan
> 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 "n= on-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 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 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 Pay= ments). 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 justif= ication
> 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'd= ask him
> to perform as a BIPs editor and it's something that he's alrea= dy 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/msgid/bitc= oindev/64FDB7CF-CBFB-416D-8BCF-2DC50CD2E4B7%40dashjr.org.
------4OW0HPXMT6P3O7AMS0YXSQ1HZVQCNW--