path: root/1b/3830bf95f16eec2700b4f19888242dd6043388

Delivery-date: Thu, 29 Feb 2024 08:55:55 -0800
Received: from mail-yb1-f185.google.com ([209.85.219.185])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCU2P6FJ3EBBBE7OQKXQMGQEUJ5QWTI@googlegroups.com>)
	id 1rfjhK-0007md-QG
	for bitcoindev@gnusha.org; Thu, 29 Feb 2024 08:55:55 -0800
Received: by mail-yb1-f185.google.com with SMTP id 3f1490d57ef6-dccc49ef73esf1985274276.2
        for <bitcoindev@gnusha.org>; Thu, 29 Feb 2024 08:55:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1709225748; x=1709830548; 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=M4DBrt+BzY8/apN5ej2ph++o10vUz5Z0pw/r8LiHwNE=;
        b=ZGAft/Yz65NRrsHXr47loKOXmBfGvpHVAhbyElVRFPQ41SWjC19DAO+Kb/EK/WnvAU
         o2HrOPeDcHHn8Oa1KRLlhCFgmcApDNlhHVnbPQZ/r6rJ7kOE0BjISg2J1446VIX18ioA
         m+ny+URHXNvDF6qaYU16ssdFCq04EBxs4ddIAcxbxC7YyiuSz6JXUqrQtNgXIQlMac4W
         RQT5hVzVcgWHY3H8vtt4+V7UHGRusa2XtJ5bGIWCAtYHGHn7z+wRfe3b0Ie4XfDEijmU
         tfIz9ojCNGncuQqs1g0uMqqCXg7z3Cw3EKRZ0xL8gd9L6uKa1I0RAahUFd2tBcedDoWG
         DJ0w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1709225748; x=1709830548; 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=M4DBrt+BzY8/apN5ej2ph++o10vUz5Z0pw/r8LiHwNE=;
        b=k2k3GMs3acHEXvesWGsZtM+CSbYz7jSUU6SgV1Q7vlZnTuyzY4l65B7qTgA3wNlK2F
         i9dSx5pqWmrTid5acMhE8YA43w4m9M2m2lTY2CCr0HKnXE4/FUTs7ZLvVGI732xGr2+X
         NHAi9qyvEzdkUiEcRAdXo963+n1jnIkAvjQFEHJBjXwjp45OnnX864QzkOpUfs6jaImV
         QA1Xaw5LaXaxUuinrFxfmynP/mKaUSj2FL1KvJxZBZY7KTEM5xRcPGZQkxfr0JbRrDs5
         Z3vXDqr/qsjIkWc5EfqUQIiQ2NzIOzHsnNxZ4HIlXRs/xw8g55D5xshpeSkLv8y6Y1ZZ
         /f5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1709225748; x=1709830548;
        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=M4DBrt+BzY8/apN5ej2ph++o10vUz5Z0pw/r8LiHwNE=;
        b=DMs+g/eTVEsztNyKJf05GgL9NPUW5+/dVy8/xcPIeBCqIFZL5Kza3XebzgJfBwwdG2
         jIMlTmorBps+7Nj5/0VuV4eYubSLMhuimeoDjIKFz+Ytsdmz5zTcQiqF/otcLQ1wBH31
         89aF0o+Hgn4C+adZO8l5MhqaVu+borfIl1WqTd2oC+ZgOI0Rsnd4OijpYKnwPvAAPikU
         yLLgefX0NOf0HHlTzPAgFUfb6VJPJom8At9oEZNUI7yZnu8zP1lDVvl/AdFckvPsi/J0
         iG1jKMr+VGK1c9aSOrxFb8Xk+oYfcKRukj6RmbxToBvFS0uLzdDUsu3ya5X2Yl8LprJy
         2i4w==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCX5mCJBQmUpjBoMevnJUq44/Kmt2Aoqvbu94+m2QsfkPng2+EjA7+dS2oUjlB7diP78MNDFTsUYAplYO4R1ahtnowUD2sE=
X-Gm-Message-State: AOJu0Yzk13TIfHbYtPiqF5ILpqEvERsxo2ogarQLtjmf8rBjBAwn3T9N
	kezzi9oGtK+uUISty4U+uA664/8in/lBn8nOPf0nzfLaQF9Vsxdf
X-Google-Smtp-Source: AGHT+IGR75CqyQmcpatcajeprf0ygi4/AkOTbRZ7TU0Q+rLINzEx8u7XC333vS40zrLEHqCfjE1mcw==
X-Received: by 2002:a25:86cd:0:b0:dcb:f733:88d8 with SMTP id y13-20020a2586cd000000b00dcbf73388d8mr2905146ybm.11.1709225748479;
        Thu, 29 Feb 2024 08:55:48 -0800 (PST)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:df4a:0:b0:dcb:bfe0:81b8 with SMTP id w71-20020a25df4a000000b00dcbbfe081b8ls1562244ybg.0.-pod-prod-09-us;
 Thu, 29 Feb 2024 08:55:47 -0800 (PST)
X-Received: by 2002:a05:690c:3606:b0:609:2fba:12a0 with SMTP id ft6-20020a05690c360600b006092fba12a0mr643747ywb.3.1709225747416;
        Thu, 29 Feb 2024 08:55:47 -0800 (PST)
Received: by 2002:a05:690c:a:b0:608:7da7:c18d with SMTP id 00721157ae682-6093996e4fdms7b3;
        Tue, 27 Feb 2024 20:22:43 -0800 (PST)
X-Received: by 2002:a05:6902:1142:b0:dc6:c2e4:5126 with SMTP id p2-20020a056902114200b00dc6c2e45126mr383364ybu.12.1709094162973;
        Tue, 27 Feb 2024 20:22:42 -0800 (PST)
Date: Tue, 27 Feb 2024 20:22:42 -0800 (PST)
From: /dev /fd0 <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <6cc559b8-5aa4-4886-8e94-ae3a8cfd7463n@googlegroups.com>
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_21192_858625993.1709094162598"
X-Original-Sender: alicexbtong@gmail.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.5 (/)

------=_Part_21192_858625993.1709094162598
Content-Type: multipart/alternative; 
	boundary="----=_Part_21193_1695244008.1709094162598"

------=_Part_21193_1695244008.1709094162598
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 disagree 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/6cc559b8-5aa4-4886-8e94-ae3a8cfd7463n%40googlegroups.com.

------=_Part_21193_1695244008.1709094162598
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ava,<div><br /></div><div>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 disagree with the 2 names suggested.=
</div><div><br /></div><div>/dev/fd0</div><div>floppy disk guy<br /><br /><=
/div><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">On W=
ednesday, February 28, 2024 at 12:57:57=E2=80=AFAM UTC+5:30 Ava Chow wrote:=
<br/></div><blockquote class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; =
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi All,
<br>
<br>Following on the recent [discussion][1] about BIP process friction, and=
=20
<br>admissions from Luke that he has not had the time to actively work on=
=20
<br>the BIPs repo ([2], [3]), I think it is prudent for us to look at addin=
g=20
<br>more BIPs editors. These people would have the same permissions and=20
<br>responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs=
=20
<br>adding new BIPs, merge PRs to fix existing BIPs,and all other=20
<br>responsibilities as described in [BIP 2][4]. I think this would=20
<br>significantly help get through the backlog of BIPs PRs, and responding=
=20
<br>to them in a timely manner to significantly reduce the friction of=20
<br>getting BIPs changes merged. Of course, this would require that all BIP=
=20
<br>editors agree on the numbering scheme so that BIPs continue to be=20
<br>numbered consistently.
<br>
<br>Considering the responsibilities of these tasks, I think any new BIP=20
<br>editors should be people who have a history of following and being=20
<br>involved in Bitcoin development, as well as being known to evaluate=20
<br>proposals objectively, and of course, are willing to do the job. With=
=20
<br>that in mind, I think both Kanzure and RubenSomsen are very good=20
<br>candidates to be BIP editors, and having both of them working on the=20
<br>BIPs repo would greatly benefit all of us.
<br>
<br>Thanks,
<br>Ava
<br>
<br>[1]:=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024=
-January/022289.html" target=3D"_blank" rel=3D"nofollow" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundat=
ion.org/pipermail/bitcoin-dev/2024-January/022289.html&amp;source=3Dgmail&a=
mp;ust=3D1709180470006000&amp;usg=3DAOvVaw0QlFml1-nuiZD_h3Q8eYU9">https://l=
ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022289.html</a>
<br>[2]:=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024=
-January/022291.html" target=3D"_blank" rel=3D"nofollow" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundat=
ion.org/pipermail/bitcoin-dev/2024-January/022291.html&amp;source=3Dgmail&a=
mp;ust=3D1709180470006000&amp;usg=3DAOvVaw0QxQbwnuTurDJEWPWpWjgX">https://l=
ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022291.html</a>
<br>[3]: <a href=3D"https://twitter.com/LukeDashjr/status/17611279723024590=
00" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://www.=
google.com/url?hl=3Den&amp;q=3Dhttps://twitter.com/LukeDashjr/status/176112=
7972302459000&amp;source=3Dgmail&amp;ust=3D1709180470006000&amp;usg=3DAOvVa=
w188Kx5AiJXxUe_prb0DNVV">https://twitter.com/LukeDashjr/status/176112797230=
2459000</a>
<br>[4]:=20
<br><a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0002.mediawi=
ki#user-content-BIP_Editor_Responsibilities__Workflow" target=3D"_blank" re=
l=3D"nofollow" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&a=
mp;q=3Dhttps://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki%23use=
r-content-BIP_Editor_Responsibilities__Workflow&amp;source=3Dgmail&amp;ust=
=3D1709180470006000&amp;usg=3DAOvVaw3aJ_l89dZQU-WQyUWOioTZ">https://github.=
com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-content-BIP_Editor_Res=
ponsibilities__Workflow</a>
<br>
<br></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/6cc559b8-5aa4-4886-8e94-ae3a8cfd7463n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/6cc559b8-5aa4-4886-8e94-ae3a8cfd7463n%40googlegroups.com</a>.=
<br />

------=_Part_21193_1695244008.1709094162598--

------=_Part_21192_858625993.1709094162598--