From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 02 Apr 2024 01:22:23 -0700 Received: from mail-qt1-f191.google.com ([209.85.160.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 1rrZPS-0004QV-Hr for bitcoindev@gnusha.org; Tue, 02 Apr 2024 01:22:23 -0700 Received: by mail-qt1-f191.google.com with SMTP id d75a77b69052e-432eb9ba95dsf16567021cf.2 for ; Tue, 02 Apr 2024 01:22:22 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1712046136; cv=pass; d=google.com; s=arc-20160816; b=OxTt4TQQlVhgz83pmzx4qKWX3qZE6PUhRJOKwFejDPaRE8KeWv7te4ZnL3JRGxgcK7 xiVmg0oWNBLOYzHKVCFqhlgp39F3aGUyBLGP1xpuIloUfEeQnR+W2bT4y4IjnHlYhPh0 3/ElOnQh48tIfv/Lo3kZjhP1dEysEJ1CgSaYmDAuSibgdAp69NPpWlMgGXvrYNBiARfi OjtH507dOeW5pwY+czqOgCKNVqpvLNSJLe4pulQ2rDoFg1j45CJnZvSYZsY4oCFupgAQ Lpl6z3Wt8So+w6515DtEgmUKkEJPa16VYVFifxg7Rd/9Bep4igHqbBCZHukkNRDRYkNU I0pQ== 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:reply-to:content-transfer-encoding :mime-version:feedback-id:references:in-reply-to:message-id:subject :from:to:date:dkim-signature; bh=1Mx6MU0sUI1eOmZLVanxXLCvN0gv1O8qJQpb/Asb0ac=; fh=+QyZpU4GV6XX3Bv7GqBi465jNxaSLu23HMi7h2j0D24=; b=d3VwOXsDVPIskQbyuZk0L93Gk1p1aRAY0kvNd/FhGLo4kirg7SQ828XA7RGb0hTwYv /kddcsnhL0AHZGJdqMPUZcObobrSuI832fVjUcDpSDZUMkn3NKFHFnV4eK0bS9ZCHR8h Zl7Sizbl0dW40gS/h4TrVizJtluzVjB5yOJ0htg/4/dI/fsPi/950cOONYn8gm2mm9p2 CT71mEXGNdIlYN04fWfYyQK3uLuh0n2oyKv30iYTW/TfVUkyc9+wbm6jIQj4ygWwHV3J SMsyhdAdM2QkVSMwsFsaeMVOH/GNYsoZEeFa3AscQfXIvtcgl5Xn/2osg9X3KjGfJxmT QikQ==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail3 header.b=cCjBJjaK; spf=pass (google.com: domain of lists@achow101.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1712046136; x=1712650936; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender :content-transfer-encoding:mime-version:feedback-id:references :in-reply-to:message-id:subject:from:to:date:from:to:cc:subject:date :message-id:reply-to; bh=1Mx6MU0sUI1eOmZLVanxXLCvN0gv1O8qJQpb/Asb0ac=; b=w/sh074SYArGthOqKRweKTK6ydXCnOfD+Hfp7+8AkNSrAbjZLKB9iE8R9ONek5Fx0Z 2j528HeURNSHz+YInGqFMmZCeGwMSQi9ETu3kin9oUHXHRRH6TYxIHBCMekGCRXlyl4j RgKWZjetI6BKvmpHiiJT7gJx9WhBHsNAb33UWG2wDX3FNlrXmO+yUQ1UQ+VSHmE72iXn YEEcdEMebisOSzF1atuUKL5zwrBetkhqqKVlocmZIl4mCiSKsc6JhO5yZK1niZXKc+Q/ 0AmAgrNpoHHHe1vPJ7yAh9vbscS9Muui/T9124s8bd6UUatSNjHKd5YJEeJqQPT3MiKg GYrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712046136; x=1712650936; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to :x-original-authentication-results:x-original-sender :content-transfer-encoding:mime-version:feedback-id:references :in-reply-to:message-id:subject:from:to:date:x-beenthere :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1Mx6MU0sUI1eOmZLVanxXLCvN0gv1O8qJQpb/Asb0ac=; b=jRxhpMnK+pP/DxFfXAdiH3tyL3t1cAcieVBOllf7vsmORpaRqGeAhaaokVvpZrjzo4 oK6Lgzv4C/3zR3Bd5Kq+Ux078aVqyoEezXy55kkg4Hx+/XL/zP94h/laT0QOq+Cg0LQM jqH8k7vpcMMHnxO+4XVo8xp5ALeL/8O5C7tuqRUR+EgKzmwJvVFuj7YkY5nLXTCmhp8n BioEWwvu/KFIdqbsHR8YB0KY0cC9KV5vqZDvq0idNwtpVev+92ncR//4gtIQSLPe5y7l umstUcLH2UDFeUlgkvm4AejUJPPPCape0lJyGkSzRRb9QMBBDk9RRxS7KoZKNutfZoW6 dFFA== X-Forwarded-Encrypted: i=2; AJvYcCURFtBmx0gg1idGwV+xzk/jOXUvpxUMrLNrS/UadyyaTKvf6erKIUytoDAJJIhL025Xqwn5rp0Sbyj0eAmSRc5CPOZXO4c= X-Gm-Message-State: AOJu0YybhW37pvY2lgwQDb6vtPFafqgliS0nMRyfhwTGjl2PsraSam9B ZDZxshYo1NHbk5cAh8yNLg+VVYQqIXwIiTiu9CA2agVxIpxGwlEf X-Google-Smtp-Source: AGHT+IFL3Frl3dq/FBVDbv94FdRgi1EVPOmHiYi2YwCrFrGtbkJ1P2zYq7fMlCNnM5VcKToUEhRgqw== X-Received: by 2002:ac8:7f55:0:b0:434:39f0:d4f with SMTP id g21-20020ac87f55000000b0043439f00d4fmr478798qtk.44.1712046136102; Tue, 02 Apr 2024 01:22:16 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:ac8:5d0e:0:b0:432:e560:1d2d with SMTP id f14-20020ac85d0e000000b00432e5601d2dls69785qtx.2.-pod-prod-02-us; Tue, 02 Apr 2024 01:22:15 -0700 (PDT) X-Received: by 2002:a05:620a:4625:b0:78c:8587:7522 with SMTP id br37-20020a05620a462500b0078c85877522mr79085qkb.0.1712046134862; Tue, 02 Apr 2024 01:22:14 -0700 (PDT) Received: by 2002:a05:620a:4627:b0:78b:e8c6:6138 with SMTP id af79cd13be357-78be8c66507ms85a; Mon, 1 Apr 2024 17:38:04 -0700 (PDT) X-Received: by 2002:a05:6000:a88:b0:341:d3b0:ae7d with SMTP id dh8-20020a0560000a8800b00341d3b0ae7dmr9552935wrb.45.1712018283038; Mon, 01 Apr 2024 17:38:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1712018283; cv=none; d=google.com; s=arc-20160816; b=RI+caPlwp3Y685T5OzUUfFKd3s4juTrQ7yvRpL04HAQGeW4oobjq9CXZEFrStc1VsA OBt68522hpIE6PV5Src6VdJQhWcYLXxyhMRbjU+R7Fska3C0PKRzkOubEuALhTjQnzB/ E3mFaKj6/u7sxqgfen8NSmVmm7GgmFOQYI3AJa6QkuiSi6ztgs99kxAapkLDZ7RH3ReQ YnujNKeRogPc0I2bY4AeE/8Ssf15jobrk7NVYxlqxoEI3Crydub2blTct5zozSIrIPQK iDoU15vhFbOdrdsW1syxqp7G5geyLW1BQabKxrY00MMbKzNER3pqyNj1s1izXbLrcZpw Z5FA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:feedback-id:references :in-reply-to:message-id:subject:from:to:date:dkim-signature; bh=BrLGr1ffoK7Y3V9cbYI9k9zUVAgYsPlNM2OIQ73ylIc=; fh=VcGcg+Zjs9gw1uDcHbxsAILhBAcecnbJzZRdxgKVDIc=; b=V3t0yO/z6sjfqqoUNgWBwAQzscn5QseCViwBpaNJ+cY4mUxALkRt9E2nhuCNP2eydb jbS//qOW38uEPC2HOolKhkRq+Vw9o27cgusjiwVYfrpAGiKfmUvLxEawKtpXISASvUeL L6AT9wHNF4Btg4/A8dHU1SoJ1TyiupNgu5qqlcmvC/Mzz5y6A5ubeo8tJfUJIdDvSdeH qU8pvsnIWD9ur/TQfpj5ot5FTkaIcxZvrXdXsC8oUATKTWhIHUgPqqLwYgvw4r1Ii8vr v+7MXqRXr/4dBkIYD10NeOV+NXFGsfc8qaETUOm9klmHu1BrqdGF5WC8hbjbcBusAtpF Tf8A==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail3 header.b=cCjBJjaK; spf=pass (google.com: domain of lists@achow101.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com Received: from mail-4022.proton.ch (mail-4022.proton.ch. [185.70.40.22]) by gmr-mx.google.com with ESMTPS id k8-20020a5d6d48000000b0033cddf15870si338101wri.6.2024.04.01.17.38.02 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 01 Apr 2024 17:38:02 -0700 (PDT) Received-SPF: pass (google.com: domain of lists@achow101.com designates 185.70.40.22 as permitted sender) client-ip=185.70.40.22; Date: Tue, 02 Apr 2024 00:37:57 +0000 To: bitcoindev@googlegroups.com From: "'Ava Chow' via Bitcoin Development Mailing List" Subject: Re: [bitcoindev] Re: Adding New BIP Editors Message-ID: 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> Feedback-ID: 53660394:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Original-Sender: lists@achow101.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@achow101.com header.s=protonmail3 header.b=cCjBJjaK; spf=pass (google.com: domain of lists@achow101.com designates 185.70.40.22 as permitted sender) smtp.mailfrom=lists@achow101.com; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=achow101.com X-Original-From: Ava Chow Reply-To: Ava Chow 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 (-) 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 > bitcoin-dev@lists.linuxfoundation.org mailing list (do not assign a=20 > number - read BIP 2 for the full process). After discussion, please 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 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 process= =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 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 appears to b= e > 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], Joh= n > 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 hi= m > to perform as a BIPs editor and it's something that he's already doin= g, > 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.c= om/ > [4] > https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurgatory.c= om/ > [5] > https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegroups.c= om/ > [6] > https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegroups.c= om/ > [7] > https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegroups.c= om/ > [8] > https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3DwruqgLE= azRA5...@mail.gmail.com/ > [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/ > > [10] > https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcorallo.co= m/ > [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/ > > [12] > https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@mail.gm= ail.com/ > [13] > https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.one/ > > [14] > https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101.com/ > > [15] > https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXs= uizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=3D@= protonmail.com/ > [16] > https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegroups.c= om/ > [17] > https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=3DYJMv= d9Qrst+...@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+unsubscribe@googlegroups.com=20 > . > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/bitcoindev/cbb0b74f-c60b-4c8a-9e97-9b1c= 0e0eb047n%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/f14cf0de-20f2-4786-bb92-d686a73c1218%40achow101.com.