Delivery-date: Sun, 10 Mar 2024 10:12:19 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of keagan.mcclelland@gmail.com designates 2607:f8b0:4864:20::c34 as permitted sender) client-ip=2607:f8b0:4864:20::c34;
MIME-Version: 1.0
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
 <e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
In-Reply-To: <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Thu, 7 Mar 2024 14:39:54 -0800
Message-ID: <CALeFGL2=N+JcQC_feq97+-CSi47esgz82v2LsvCzs-PCVQZArg@mail.gmail.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoindev@googlegroups.com
Content-Type: multipart/alternative; boundary="000000000000b07cc7061319c196"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

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

NACK on Tonoski. He's so far shown far too little interest in understanding
the history of technical decisions and has been rather extreme in rhetoric.
These are not qualities I want in a BIP Editor whose job should be a
facilitator rather than an advocate. While I don't expect any BIP Editor to
be devoid of their own opinions, I do not trust that he won't use the seat
as a means of pushing his own agenda.

Keags

On Tue, Feb 27, 2024 at 2:45=E2=80=AFPM Luke Dashjr <luke@dashjr.org> wrote=
:

> On 2/27/24 15:11, 'L=C3=A9o Haf' via Bitcoin Development Mailing List wro=
te:
> > Luke should choose the new editors himself, especially since he has
> > already made a call for applications.
>
> Thanks, but this is for the broader development community to decide, not
> just any one person.
>
> My tweet got many people volunteering in response, and while I agree
> another dev reviewing new BIPs would be helpful, I do think it would be
> best to have non-devs contribute by triaging what doesn't require dev
> skills.
>
> Of those who actually put their names forward, Jon Atack and Roasbeef
> stand out as long-time devs to consider (though I have reservations
> about Roasbeef for this role). (Kanzure and Ruben both seem undecided if
> they're even available to help at this time.) For non-dev triaging, I
> would suggest we consider testing out the idea with perhaps Seccour
> and/or Greg Tonoski.
>
> 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).
>
> Luke
>
> --
> 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/9288df7b-f2e9-4106-b843-c1ff=
8f8a62a3%40dashjr.org
> .
>

--=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/CALeFGL2%3DN%2BJcQC_feq97%2B-CSi47esgz82v2LsvCzs-PCVQZArg%40mail=
.gmail.com.

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

<div dir=3D"ltr">NACK on Tonoski. He&#39;s so far shown far too little inte=
rest in understanding the history of technical decisions and has been rathe=
r extreme in rhetoric. These are not qualities I want in a BIP Editor whose=
 job should be a facilitator rather than an advocate. While I don&#39;t exp=
ect any BIP Editor to be devoid of their own opinions, I do not trust that =
he won&#39;t use the seat as a means of pushing his own agenda.<div><br></d=
iv><div>Keags</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Tue, Feb 27, 2024 at 2:45=E2=80=AFPM Luke Dashjr &lt;=
<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">On 2/27/24 15:11, &#39;L=
=C3=A9o Haf&#39; via Bitcoin Development Mailing List wrote:<br>
&gt; Luke should choose the new editors himself, especially since he has <b=
r>
&gt; already made a call for applications.<br>
<br>
Thanks, but this is for the broader development community to decide, not <b=
r>
just any one person.<br>
<br>
My tweet got many people volunteering in response, and while I agree <br>
another dev reviewing new BIPs would be helpful, I do think it would be <br=
>
best to have non-devs contribute by triaging what doesn&#39;t require dev <=
br>
skills.<br>
<br>
Of those who actually put their names forward, Jon Atack and Roasbeef <br>
stand out as long-time devs to consider (though I have reservations <br>
about Roasbeef for this role). (Kanzure and Ruben both seem undecided if <b=
r>
they&#39;re even available to help at this time.) For non-dev triaging, I <=
br>
would suggest we consider testing out the idea with perhaps Seccour <br>
and/or Greg Tonoski.<br>
<br>
Assigning BIP numbers itself is easy enough. The hard part is evaluating <b=
r>
if the new proposal meets the criteria - which definitely needs dev <br>
skills (mainly for technical soundness). So IMO we should move forward <br>
with more editors ASAP without waiting for a new way to coordinate the <br>
numbering (we can deal with that later/in parallel to solving the <br>
immediate need).<br>
<br>
Luke<br>
<br>
-- <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%2Bunsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3%40dashjr.org" re=
l=3D"noreferrer" target=3D"_blank">https://groups.google.com/d/msgid/bitcoi=
ndev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3%40dashjr.org</a>.<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/CALeFGL2%3DN%2BJcQC_feq97%2B-CSi47esgz82v2LsvCzs-PCVQ=
ZArg%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://group=
s.google.com/d/msgid/bitcoindev/CALeFGL2%3DN%2BJcQC_feq97%2B-CSi47esgz82v2L=
svCzs-PCVQZArg%40mail.gmail.com</a>.<br />

--000000000000b07cc7061319c196--