Delivery-date: Thu, 28 Mar 2024 13:19:17 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d32 as permitted sender) client-ip=2607:f8b0:4864:20::d32;
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>
 <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
 <d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
 <f9435999-42df-46b5-86e2-7ba0336a9bf2@mattcorallo.com> <ZgWRu32FXzqqg69V@console>
In-Reply-To: <ZgWRu32FXzqqg69V@console>
From: Antoine Riard <antoine.riard@gmail.com>
Date: Thu, 28 Mar 2024 19:42:15 +0000
Message-ID: <CALZpt+E8DohYEJ9aO+FiF6+EKMCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
To: Brandon Black <freedom@reardencode.com>
Cc: Matt Corallo <lf-lists@mattcorallo.com>, Murch <murch@murch.one>, 
	bitcoindev@googlegroups.com
Content-Type: multipart/alternative; boundary="0000000000000a84300614bdb96c"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

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

Hi all,

On the timeframe of the new appointment of new BIP editors, I would suggest
to postpone the effective date to the 1st May or after.

There is a CoreDev edition happening in April and it's better to not
conflict the appointment of new BIP editors with any of the CoreDev dates
by transparency towards the wider community.
This avoids last-minute "Hong-Kong Agreement" decision-making-style and
anyone present in the room with the GH administrative rights on the BIP
repository making the change in a "fait accompli".

On all the other concerns, I think it's still better to split the
administrative rights between 1) editors who can merge and 2)
"product-management" style privileges for PR / issues sorting.
I think it's good to let technical relevance of the proposal be appreciated
by the wider community, marking them as "rejected" if necessary.

As new BIP editors, I'm supporting the following list:
- Kanzure (great responsiveness in my experience)
- Ruben (very knowledgeable in all part of Bitcoin stack)
- Roasbeef (i think it's good to have someone for all inter-compatibility
clients things)
- Murch (top bitcoin stackoverflow contributor)
- Jon Atack (much experience with bitcoin core codebase and great
responsiveness too)

As new BIP "decentralized PM", I'm supporting the following list:
- Seccour

I don't know the Bitcoin technical credentials of Greg Tonoski.

I think a good thing is to have not-only US-based BIP editors for higher
timezones coverage and BIP process responsiveness.

Best,
Antoine


Le jeu. 28 mars 2024 =C3=A0 16:16, Brandon Black <freedom@reardencode.com> =
a
=C3=A9crit :

> I agree with Matt's suggestions, and also support Jon Atack as a BIP
> editor.
>
> * Jon's work in bitcoin has focused on practical concerns of users of
> the bitcoin software, a valuable perspective for the BIP process as
> well. He's been a steady contributor to the bitcoin node software for 4
> continuous years, this steadiness would be a boon to the BIP process.
>
> Best,
>
> --Brandon
>
> On 2024-03-27 (Wed) at 19:54:53 -0400, Matt Corallo wrote:
> > Seems reasonable to me.
> >
> > While there are plenty of competent technical folks who would make fine
> BIP
> > editors, I'd suggest Kanzure and Murch as clear candidates over others:
> >
> >  * Kanzure has been around for longer than any other candidate as far a=
s
> I
> > can tell, and has certainly seen more proposals for changes to Bitcoin
> than
> > anyone. This makes him a great candidate to point new BIP authors to
> > appropriate citations. Similarly, he has a long history of being very
> > responsive, which I believe is part of the goal in appointing new edito=
rs
> > here.
> >  * Murch similarly has lots of experience dealing with lots of various
> ideas
> > around Bitcoin, but importantly here also has worked extensively to
> document
> > appropriate terminology for all things Bitcoin [1]. This makes him an
> > excellent copy editor of Bitcoin technical proposals, which is basicall=
y
> the
> > only thing the BIP editors are supposed to do.
> >
> > While there are a handful of other candidates mentioned in this thread
> who
> > are technically quite competent, that isn't really the relevant criteri=
a
> for
> > BIP editors.
> >
> > Matt
> >
> > [1] https://github.com/murchandamus/bips/pull/1/files
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Bitcoin Development Mailing List" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bitcoindev/ZgWRu32FXzqqg69V%40console.
>

--=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/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEbHSKSXpq0VKVBhJLhrw%40mail=
.gmail.com.

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

<div dir=3D"ltr">Hi all,<div><br></div><div>On the timeframe of the new app=
ointment of new BIP editors, I would suggest to postpone the effective date=
 to the 1st May or after.</div><div><br></div><div>There is a CoreDev editi=
on happening in April and it&#39;s better to not conflict the appointment o=
f new BIP editors with any of the CoreDev dates by transparency towards the=
 wider community.</div><div>This avoids=C2=A0last-minute &quot;Hong-Kong Ag=
reement&quot; decision-making-style and anyone=C2=A0present in the room wit=
h the GH administrative=C2=A0rights on the BIP repository making the change=
 in a &quot;fait accompli&quot;.</div><div><br></div><div>On all the other =
concerns, I think it&#39;s still better to split the administrative rights =
between 1) editors who can merge and 2) &quot;product-management&quot; styl=
e privileges for PR / issues sorting.</div><div>I think it&#39;s good to le=
t technical relevance=C2=A0of the proposal be appreciated by the wider comm=
unity, marking them as &quot;rejected&quot; if necessary.</div><div><br></d=
iv><div>As new BIP editors, I&#39;m supporting the following list:</div><di=
v>- Kanzure (great responsiveness in my experience)</div><div>- Ruben (very=
 knowledgeable in all part of Bitcoin stack)</div><div>- Roasbeef=C2=A0(i t=
hink it&#39;s good to have someone for all inter-compatibility clients thin=
gs)</div><div>- Murch (top bitcoin stackoverflow=C2=A0contributor)</div><di=
v>- Jon Atack (much experience with bitcoin core codebase and great respons=
iveness too)</div><div><br></div><div>As new BIP &quot;decentralized PM&quo=
t;, I&#39;m supporting the following list:</div><div>- Seccour=C2=A0</div><=
div><br></div><div>I don&#39;t know the Bitcoin technical credentials of Gr=
eg Tonoski.<br></div><div><br></div><div>I think a good thing is to have no=
t-only US-based BIP editors for higher timezones coverage and BIP process r=
esponsiveness.</div><div><br></div><div>Best,</div><div>Antoine=C2=A0</div>=
<div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">Le=C2=A0jeu. 28 mars 2024 =C3=A0=C2=A016:16, Brandon Black =
&lt;<a href=3D"mailto:freedom@reardencode.com">freedom@reardencode.com</a>&=
gt; a =C3=A9crit=C2=A0:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;bor=
der-left-color:rgb(204,204,204);padding-left:1ex">I agree with Matt&#39;s s=
uggestions, and also support Jon Atack as a BIP<br>
editor.<br>
<br>
* Jon&#39;s work in bitcoin has focused on practical concerns of users of<b=
r>
the bitcoin software, a valuable perspective for the BIP process as<br>
well. He&#39;s been a steady contributor to the bitcoin node software for 4=
<br>
continuous years, this steadiness would be a boon to the BIP process.<br>
<br>
Best,<br>
<br>
--Brandon<br>
<br>
On 2024-03-27 (Wed) at 19:54:53 -0400, Matt Corallo wrote:<br>
&gt; Seems reasonable to me.<br>
&gt; <br>
&gt; While there are plenty of competent technical folks who would make fin=
e BIP<br>
&gt; editors, I&#39;d suggest Kanzure and Murch as clear candidates over ot=
hers:<br>
&gt; <br>
&gt;=C2=A0 * Kanzure has been around for longer than any other candidate as=
 far as I<br>
&gt; can tell, and has certainly seen more proposals for changes to Bitcoin=
 than<br>
&gt; anyone. This makes him a great candidate to point new BIP authors to<b=
r>
&gt; appropriate citations. Similarly, he has a long history of being very<=
br>
&gt; responsive, which I believe is part of the goal in appointing new edit=
ors<br>
&gt; here.<br>
&gt;=C2=A0 * Murch similarly has lots of experience dealing with lots of va=
rious ideas<br>
&gt; around Bitcoin, but importantly here also has worked extensively to do=
cument<br>
&gt; appropriate terminology for all things Bitcoin [1]. This makes him an<=
br>
&gt; excellent copy editor of Bitcoin technical proposals, which is basical=
ly the<br>
&gt; only thing the BIP editors are supposed to do.<br>
&gt; <br>
&gt; While there are a handful of other candidates mentioned in this thread=
 who<br>
&gt; are technically quite competent, that isn&#39;t really the relevant cr=
iteria for<br>
&gt; BIP editors.<br>
&gt; <br>
&gt; Matt<br>
&gt; <br>
&gt; [1] <a href=3D"https://github.com/murchandamus/bips/pull/1/files" rel=
=3D"noreferrer" target=3D"_blank">https://github.com/murchandamus/bips/pull=
/1/files</a><br>
<br>
-- <br>
You received this message because you are subscribed to a topic in the Goog=
le Groups &quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this topic, visit <a href=3D"https://groups.google.com/=
d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe" rel=3D"noreferrer" target=3D"_b=
lank">https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe<=
/a>.<br>
To unsubscribe from this group and all its topics, send an email to <a href=
=3D"mailto:bitcoindev%2Bunsubscribe@googlegroups.com" target=3D"_blank">bit=
coindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/ZgWRu32FXzqqg69V%40console" rel=3D"noreferrer" target=
=3D"_blank">https://groups.google.com/d/msgid/bitcoindev/ZgWRu32FXzqqg69V%4=
0console</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/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEbHSKSXpq0VKVBhJ=
Lhrw%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://group=
s.google.com/d/msgid/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEbHSKS=
Xpq0VKVBhJLhrw%40mail.gmail.com</a>.<br />

--0000000000000a84300614bdb96c--