From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 27 Feb 2024 15:51:21 -0800 Received: from mail-yb1-f189.google.com ([209.85.219.189]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rf7EG-0005Se-H8 for bitcoindev@gnusha.org; Tue, 27 Feb 2024 15:51:20 -0800 Received: by mail-yb1-f189.google.com with SMTP id 3f1490d57ef6-dcc58cddb50sf8122427276.0 for ; Tue, 27 Feb 2024 15:51:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1709077874; x=1709682674; 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=ybP3ZHgdrI2JtF7VCKg8O/yi5viAxBxaZeUCAFfAaFU=; b=dxqSho6SZUjGIwwlTIKzEMUGi/CkXoCTuEm+ciNfOCGyThV9nCW6aoBFTOytsLOUNX sbQ15k9h41lP6RpJyZiD+Ts+rlIQBxyvGw8T5X2krA9kryqfwLy0hl1NBobntLKUvOAR Wei/5KXEkmLLUpXxTWqQyMhc3VXG86lpwi8vvqmlzUVGOWYY1jxQrzUXRMKItvbPULqn RZUPavgQZzg4RBTIR2kmKQBwd7IBOFD/Y6ykK0i5Y60ZZmF3xsI5bTrh7Orrj5+MFv3V 8lN6xA/DAIGaJsjCfMfYEXPkUMICusyxtQ9As5CUB4A/NAy7B/iyHdEd8cdWHrxxTKHj 4cQQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709077874; x=1709682674; 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=ybP3ZHgdrI2JtF7VCKg8O/yi5viAxBxaZeUCAFfAaFU=; b=YaJ3xmDzKWAXz+A0S5fUbN24dIqQC5ZfMW5xICbG4Dg3CJSe4kCxPZe3RpAOLlZB8n KHCHMTwR/Fd9+E9LDYTdVdtMyFQSqT5WPBOyrc4Hu4ExjREXzCI6z5OVXtzCwqr5S4W8 zNhjElrAxM9ypAKZHrblr0BmOhB31bLlQrBBQGQ9An6OcYK2XMrGm3UeQc047ke8Hj14 rcZeQW2FL+Ro9aUijmiSBiZs8VQxHz91zXKizSCoaV9g5+DG1EUUn9uYRYhwKjsTvYoP ucwE81l3iy+fCL/wso+PKNxAHDOhahkJ0PwqW6/ArT2HQdO+Bmd/tq+9OtHaR26i7yCB KkNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709077874; x=1709682674; 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=ybP3ZHgdrI2JtF7VCKg8O/yi5viAxBxaZeUCAFfAaFU=; b=DG7ivLaKN+m+bovGXM/Kj6/o4zRq90zQ0SQ7Hifk/cmIcNhcqvNZTmaZAEKvmX14/h UfKl7A17Ieu9wt2pPBTKhUbT2YbiIb2R5m0xKoSwLwl9LQbViW31o/yIr8OufR4OeTpo Ow9MSHaL78q8a6rnaYTfUwXRMRmOys1al2usVCLnGc72Ox7WNjInkjdYAb26fmXVAPW7 hyvMrRnS281CvGQ8rDah3SDMhf+stPlsyXUBEeohU2eG+z9ADjMQNX9c6deOk4eddH3l h6f2MUzMcZzAsHC5OrnxziyHYZDh4nduKwXX+zKN6VANP1rl0eHyX7+ND+NVDi+V6DYw 2C4w== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWvmYKBKuwVH1yUqbCnO/oU2mlAOAtGspHccLqPx80cTZRBb1erBiQgAuREDpvoLtLKVFl3FOTkV1SoyQJYi8UAg7jJcYs= X-Gm-Message-State: AOJu0Yy4iG1JTd+VZ7I3VBxc3N+lHyhSJm6SA8RNW2BqtgKB2Mio1apm Aok8NKSK4fiyIhBYih+5aHFPIK6kxGTd3wAp5ljZz4mnthnCDkjR X-Google-Smtp-Source: AGHT+IHx2yCsQz4Om8Jc0rngkauCswR0LBQ9pvHfGX8qkpMJAsxQzNZVYjgrg6zCnY82O6LIY6bqFw== X-Received: by 2002:a25:b84c:0:b0:dc7:47b7:9053 with SMTP id b12-20020a25b84c000000b00dc747b79053mr1033719ybm.15.1709077874160; Tue, 27 Feb 2024 15:51:14 -0800 (PST) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:7406:0:b0:dcc:4b24:c0e3 with SMTP id p6-20020a257406000000b00dcc4b24c0e3ls1238545ybc.1.-pod-prod-07-us; Tue, 27 Feb 2024 15:51:13 -0800 (PST) X-Received: by 2002:a25:c711:0:b0:dc7:5c0d:f177 with SMTP id w17-20020a25c711000000b00dc75c0df177mr259544ybe.6.1709077873210; Tue, 27 Feb 2024 15:51:13 -0800 (PST) Received: by 2002:a0d:cc0f:0:b0:608:91d2:e926 with SMTP id 00721157ae682-6093956e413ms7b3; Tue, 27 Feb 2024 15:10:07 -0800 (PST) X-Received: by 2002:a0d:ccca:0:b0:609:3c46:1885 with SMTP id o193-20020a0dccca000000b006093c461885mr12689ywd.10.1709075406907; Tue, 27 Feb 2024 15:10:06 -0800 (PST) Date: Tue, 27 Feb 2024 15:10:06 -0800 (PST) From: /dev /fd0 To: Bitcoin Development Mailing List Message-Id: In-Reply-To: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> Subject: [bitcoindev] Re: Adding New BIP Editors MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_6988_1677695093.1709075406527" 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_6988_1677695093.1709075406527 Content-Type: multipart/alternative; boundary="----=_Part_6989_1842479278.1709075406527" ------=_Part_6989_1842479278.1709075406527 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Ava, Even though it would be better if the BIPs repository was archived and=20 everyone maintained different repositories for BIPs. However, if it still= =20 remains relevant I would not want mailing list moderators to be same as BIP= =20 editors. So I agree with the 2 names suggested. /dev/fd0 floppy disk guy On Wednesday, February 28, 2024 at 12:57:57=E2=80=AFAM UTC+5:30 Ava Chow wr= ote: > Hi All, > > Following on the recent [discussion][1] about BIP process friction, and= =20 > admissions from Luke that he has not had the time to actively work on=20 > the BIPs repo ([2], [3]), I think it is prudent for us to look at adding= =20 > more BIPs editors. These people would have the same permissions and=20 > responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs=20 > adding new BIPs, merge PRs to fix existing BIPs,and all other=20 > responsibilities as described in [BIP 2][4]. I think this would=20 > significantly help get through the backlog of BIPs PRs, and responding=20 > to them in a timely manner to significantly reduce the friction of=20 > getting BIPs changes merged. Of course, this would require that all BIP= =20 > editors agree on the numbering scheme so that BIPs continue to be=20 > numbered consistently. > > Considering the responsibilities of these tasks, I think any new BIP=20 > editors should be people who have a history of following and being=20 > involved in Bitcoin development, as well as being known to evaluate=20 > proposals objectively, and of course, are willing to do the job. With=20 > that in mind, I think both Kanzure and RubenSomsen are very good=20 > candidates to be BIP editors, and having both of them working on the=20 > BIPs repo would greatly benefit all of us. > > Thanks, > Ava > > [1]:=20 > > https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/0222= 89.html > [2]:=20 > > https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/0222= 91.html > [3]: https://twitter.com/LukeDashjr/status/1761127972302459000 > [4]:=20 > > https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-conte= nt-BIP_Editor_Responsibilities__Workflow > > --=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/dce514e7-c6d7-43c7-8e4d-b354002fc536n%40googlegroups.com. ------=_Part_6989_1842479278.1709075406527 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Ava,

Even though it would be better if the BIPs rep= ository was archived and everyone maintained different repositories for BIP= s. However, if it still remains relevant I would not want mailing list mode= rators to be same as BIP editors. So I agree with the 2 names suggested.

/dev/fd0
floppy disk guy
On Wednesday, Febru= ary 28, 2024 at 12:57:57=E2=80=AFAM UTC+5:30 Ava Chow wrote:
Hi All,

Following on the recent [discussion][1] about BIP process friction, and= =20
admissions from Luke that he has not had the time to actively work on= =20
the BIPs repo ([2], [3]), I think it is prudent for us to look at addin= g=20
more BIPs editors. These people would have the same permissions and=20
responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs= =20
adding new BIPs, merge PRs to fix existing BIPs,and all other=20
responsibilities as described in [BIP 2][4]. I think this would=20
significantly help get through the backlog of BIPs PRs, and responding= =20
to them in a timely manner to significantly reduce the friction of=20
getting BIPs changes merged. Of course, this would require that all BIP= =20
editors agree on the numbering scheme so that BIPs continue to be=20
numbered consistently.

Considering the responsibilities of these tasks, I think any new BIP=20
editors should be people who have a history of following and being=20
involved in Bitcoin development, as well as being known to evaluate=20
proposals objectively, and of course, are willing to do the job. With= =20
that in mind, I think both Kanzure and RubenSomsen are very good=20
candidates to be BIP editors, and having both of them working on the=20
BIPs repo would greatly benefit all of us.

Thanks,
Ava

[1]:=20
https://l= ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022289.html
[2]:=20
https://l= ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022291.html
[3]: https://twitter.com/LukeDashjr/status/176112797230= 2459000
[4]:=20
https://github.= com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-content-BIP_Editor_Res= ponsibilities__Workflow

--
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/dce514e7-c6d7-43c7-8e4d-b354002fc536n%40googlegroups.com.=
------=_Part_6989_1842479278.1709075406527-- ------=_Part_6988_1677695093.1709075406527--