Delivery-date: Tue, 27 Feb 2024 15:51:14 -0800
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, 27 Feb 2024 22:57:45 +0000
To: bitcoindev@googlegroups.com
From: "'Ava Chow' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
Message-ID: <b2022288-8bd4-4a26-b074-4dcdf704ea08@achow101.com>
In-Reply-To: <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
Feedback-ID: 53660394:user:proton
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="b1_Forb8COVwhRULFI2t60n4f57oT1qzjXpvzPmTyLQ8"
Reply-To: Ava Chow <lists@achow101.com>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

This is a multi-part message in MIME format.

--b1_Forb8COVwhRULFI2t60n4f57oT1qzjXpvzPmTyLQ8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On 02/27/24 05:40 PM, Luke Dashjr wrote:

> I do think it would be best to have non-devs contribute by triaging what =
doesn't require dev
>
> skills.

Can you clarify what the non-dev triagers would be doing?

> Assigning BIP numbers itself is easy enough. The hard part is evaluating
> if the new proposal meets the criteria - which definitely needs dev
> skills (mainly for technical soundness). So IMO we should move forward
> with more editors ASAP without waiting for a new way to coordinate the
> numbering (we can deal with that later/in parallel to solving the
> immediate need).

While I think having BIP editors who can go through the backlog of PRs that=
 modify BIPs would be useful, I think the primary complaint recently has re=
ally been on the assigning of numbers and subsequently getting those propos=
ed BIPs merged. AJ's original email began with a discussion of open propose=
d BIPs that were (presumably) waiting on numbers. So I think adding editors=
 who can assign numbers should be something we do sooner rather than later.

Ava

--=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/b2022288-8bd4-4a26-b074-4dcdf704ea08%40achow101.com.

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

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8=
">
  </head>
  <body>
    On 02/27/24 05:40 PM, Luke Dashjr wrote:<br>
    <blockquote type=3D"cite"
      cite=3D"mid:9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org"><span
      style=3D"white-space: pre-wrap">I do think it would be </span><span
      style=3D"white-space: pre-wrap">best to have non-devs contribute by t=
riaging what doesn't require dev</span>
      <pre class=3D"moz-quote-pre" wrap=3D"">skills.</pre>
    </blockquote>
    Can you clarify what the non-dev triagers would be doing?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org">
      <pre class=3D"moz-quote-pre" wrap=3D"">Assigning BIP numbers itself i=
s easy enough. The hard part is evaluating
if the new proposal meets the criteria - which definitely needs dev
skills (mainly for technical soundness). So IMO we should move forward
with more editors ASAP without waiting for a new way to coordinate the
numbering (we can deal with that later/in parallel to solving the
immediate need).</pre>
    </blockquote>
    While I think having BIP editors who can go through the backlog of
    PRs that modify BIPs would be useful, I think the primary complaint
    recently has really been on the assigning of numbers and
    subsequently getting those proposed BIPs merged. AJ's original email
    began with a discussion of open proposed BIPs that were (presumably)
    waiting on numbers. So I think adding editors who can assign numbers
    should be something we do sooner rather than later.<br>
    <br>
    Ava<br>
  </body>
</html>

<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/b2022288-8bd4-4a26-b074-4dcdf704ea08%40achow101.com?u=
tm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msgid/bi=
tcoindev/b2022288-8bd4-4a26-b074-4dcdf704ea08%40achow101.com</a>.<br />

--b1_Forb8COVwhRULFI2t60n4f57oT1qzjXpvzPmTyLQ8--