Delivery-date: Fri, 29 Mar 2024 14:14:31 -0700
Sender: bitcoindev@googlegroups.com
Date: Fri, 29 Mar 2024 14:08:12 -0700 (PDT)
From: Antoine Riard <antoine.riard@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n@googlegroups.com>
In-Reply-To: <846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com>
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>
 <84309c3f-e848-d333-fd28-bdd55899b713@netpurgatory.com>
 <9baa15e4-062d-478f-8c87-8ff19ab79989@murch.one>
 <4c1462b7-ea1c-4a36-be81-7c3719157fabn@googlegroups.com>
 <6806b22d-043d-4201-841a-95e17cd8d542@mattcorallo.com>
 <846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_113168_262917207.1711746492894"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_113168_262917207.1711746492894
Content-Type: multipart/alternative; 
	boundary="----=_Part_113169_1964206021.1711746492894"

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

> Roasbeef's work on alternative clients and lightning make him technically=
=20
useful

I think one of the aim of the BIP process is to harmonize common mechanisms=
=20
among Bitcoin clients of different langages breeds or at different layers=
=20
(wallet / full-node).
Having someone among BIP editors with a proven track record of contributing=
=20
to other full-node codebase beyond C++ can be valuable in that sense.
Especially for all matters related to compatibility and deployment.

> For example I think Jon Atack would make a great Core maintainer at some=
=20
point in the future and I'm not sure a BIP editor should also be a Core=20
maintainer given the
> independence sometimes required between Core and the BIP process

In a world where both Core and BIP repository are living under a single=20
Github organization, I don't think in matters that much as the highest=20
privilege account will be able to=20
override any BIP merging decision, or even remove on the flight BIP editors=
=20
rights in case of conflicts or controversies. If you're raising the issue=
=20
that the BIP repository should be moved to its own GH repository I think=20
it's a valuable point.

Beyond, I still think we should ensure we have a wider crowd of=20
geographically and culturally diverse BIP editors. As if the role is=20
ensuring high-quality and readability of the terminology of the standards,=
=20
we might have highly-skilled technical BIP champions which are not English=
=20
native. With the current set of proposed BIP editors, to the best of my=20
knowledge, at least we have few langages spoken by the candidates: Dutch,=
=20
French, German, Spanish. This can be very helpful to translate concepts=20
devised in language A to technical english.

Best,
Antoine


Le vendredi 29 mars 2024 =C3=A0 12:33:09 UTC, /dev /fd0 a =C3=A9crit :

> Justification:
>
> 1. Jon Atack: Good at avoiding controversies and technical documentation.
> 2. Roasbeef: Since BIPs are not just related to bitcoin core, it's good t=
o=20
> have btcd maintainer as a BIP editor.
>
> On Friday, March 29, 2024 at 1:47:41=E2=80=AFAM UTC+5:30 Matt Corallo wro=
te:
>
>> Please provide justification rather than simply saying "I like Bob!".=20
>>
>> Matt=20
>>
>> On 3/28/24 12:09 PM, /dev /fd0 wrote:=20
>> > I support Jon Atack and Roasbeef from this list.=20
>> >=20
>> > On Thursday, March 28, 2024 at 6:57:53=E2=80=AFPM UTC+5:30 Murch wrote=
:=20
>> >=20
>> > I just went through the thread, previously mentioned were:=20
>> >=20
>> > - Kanzure=20
>> > - Ruben Somsen=20
>> > - Greg Tonoski=20
>> > - Jon Atack=20
>> > - Roasbeef=20
>> > - Seccour=20
>> >=20
>> > And Matt just suggested me for the role. Hope I didn=E2=80=99t overloo=
k anyone.=20
>> >=20
>> > On 3/27/24 19:39, John C. Vernaleo wrote:=20
>> > > That said, I would find it helpful if someone could go through the=
=20
>> > > thread and list all the people who've been proposed so people know=
=20
>> who=20
>> > > they should be thinking about.=20
>> >=20
>> > --=20
>> > You received this message because you are subscribed to the Google=20
>> Groups "Bitcoin Development=20
>> > Mailing List" group.=20
>> > To unsubscribe from this group and stop receiving emails from it, send=
=20
>> an email to=20
>> > bitcoindev+...@googlegroups.com <mailto:bitcoindev+...@googlegroups.co=
m>.=20
>>
>> > To view this discussion on the web visit=20
>> >=20
>> https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3=
719157fabn%40googlegroups.com=20
>> <
>> https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3=
719157fabn%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter>.=20
>>
>>
>

--=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/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.com.

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

&gt;=C2=A0<span style=3D"caret-color: rgb(80, 0, 80); color: rgb(80, 0, 80)=
;">Roasbeef's work on alternative clients and lightning make him technicall=
y=C2=A0</span><br style=3D"caret-color: rgb(80, 0, 80); color: rgb(80, 0, 8=
0);" /><span style=3D"caret-color: rgb(80, 0, 80); color: rgb(80, 0, 80);">=
useful</span><div><span style=3D"caret-color: rgb(80, 0, 80); color: rgb(80=
, 0, 80);"><br /></span></div><div><font color=3D"#500050"><span style=3D"c=
aret-color: rgb(80, 0, 80);">I think one of the aim of the BIP process is t=
o harmonize common mechanisms among Bitcoin clients of different langages b=
reeds or at different layers (wallet / full-node).</span></font></div><div>=
<font color=3D"#500050">Having someone among BIP editors with a proven trac=
k record of contributing to other full-node codebase beyond C++ can be valu=
able in that sense.</font></div><div><font color=3D"#500050">Especially for=
 all matters related to compatibility and deployment.</font></div><div><br =
/>&gt; For example I think Jon Atack would make a great Core maintainer at =
some point in the future and I'm not sure a BIP editor should also be a Cor=
e maintainer given the</div><div>&gt; independence sometimes required betwe=
en Core and the BIP process</div><div><font color=3D"#500050"><br /></font>=
</div><div><font color=3D"#500050">In a world where both Core and BIP repos=
itory are living under a single Github organization, I don't think in matte=
rs that much as the highest privilege account will be able to=C2=A0</font><=
/div><div><font color=3D"#500050">override any BIP merging decision, or eve=
n remove on the flight BIP editors rights in case of conflicts or controver=
sies.=C2=A0</font><span style=3D"color: rgb(80, 0, 80);">If you're raising =
the issue that the BIP repository should be moved to its own GH repository =
I think it's a valuable point.</span></div><div><br /></div><div><font colo=
r=3D"#500050">Beyond, I still think we should ensure we have a wider crowd =
of geographically and culturally diverse BIP editors. As if the role is ens=
uring high-quality and readability of the terminology of the standards, we =
might have highly-skilled technical BIP champions which are not English nat=
ive.=C2=A0With the current set of proposed BIP editors, to the best of my k=
nowledge, at least we have few langages spoken by the candidates: Dutch, Fr=
ench, German, Spanish. This can be very helpful to translate concepts devis=
ed in language A to technical english.</font></div><div><span style=3D"colo=
r: rgb(80, 0, 80);"><br /></span></div><div><span style=3D"color: rgb(80, 0=
, 80);">Best,</span></div><div><span style=3D"color: rgb(80, 0, 80);">Antoi=
ne</span></div><div><font color=3D"#500050"><br /></font></div><div><font c=
olor=3D"#500050"><br /></font></div><div class=3D"gmail_quote"><div dir=3D"=
auto" class=3D"gmail_attr">Le vendredi 29 mars 2024 =C3=A0 12:33:09 UTC, /d=
ev /fd0 a =C3=A9crit=C2=A0:<br/></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); paddi=
ng-left: 1ex;">Justification:<div><br></div><div>1. Jon Atack: Good at avoi=
ding controversies and technical documentation.</div><div>2. Roasbeef: Sinc=
e BIPs are not just related to bitcoin core, it&#39;s good to have btcd mai=
ntainer as a BIP editor.<br><br></div><div class=3D"gmail_quote"><div dir=
=3D"auto" class=3D"gmail_attr">On Friday, March 29, 2024 at 1:47:41=E2=80=
=AFAM UTC+5:30 Matt Corallo wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Please provide justification rather than simply saying &quot;I=
 like Bob!&quot;.
<br>
<br>Matt
<br>
<br>On 3/28/24 12:09 PM, /dev /fd0 wrote:
<br>&gt; I support Jon Atack and Roasbeef from this list.
<br>&gt;=20
<br>&gt; On Thursday, March 28, 2024 at 6:57:53=E2=80=AFPM UTC+5:30 Murch w=
rote:
<br>&gt;=20
<br>&gt;     I just went through the thread, previously mentioned were:
<br>&gt;=20
<br>&gt;     - Kanzure
<br>&gt;     - Ruben Somsen
<br>&gt;     - Greg Tonoski
<br>&gt;     - Jon Atack
<br>&gt;     - Roasbeef
<br>&gt;     - Seccour
<br>&gt;=20
<br>&gt;     And Matt just suggested me for the role. Hope I didn=E2=80=99t=
 overlook anyone.
<br>&gt;=20
<br>&gt;     On 3/27/24 19:39, John C. Vernaleo wrote:
<br>&gt;      &gt; That said, I would find it helpful if someone could go t=
hrough the
<br>&gt;      &gt; thread and list all the people who&#39;ve been proposed =
so people know who
<br>&gt;      &gt; they should be thinking about.
<br>&gt;=20
<br>&gt; --=20
<br>&gt; You received this message because you are subscribed to the Google=
 Groups &quot;Bitcoin Development=20
<br>&gt; Mailing List&quot; group.
<br>&gt; To unsubscribe from this group and stop receiving emails from it, =
send an email to=20
<br>&gt; <a rel=3D"nofollow">bitcoindev+...@googlegroups.com</a> &lt;mailto=
:<a rel=3D"nofollow">bitcoindev+...@googlegroups.com</a>&gt;.
<br>&gt; To view this discussion on the web visit=20
<br>&gt; <a href=3D"https://groups.google.com/d/msgid/bitcoindev/4c1462b7-e=
a1c-4a36-be81-7c3719157fabn%40googlegroups.com" rel=3D"nofollow" target=3D"=
_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Dfr&amp;q=3D=
https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-be81-7c3719=
157fabn%2540googlegroups.com&amp;source=3Dgmail&amp;ust=3D1711832076949000&=
amp;usg=3DAOvVaw2Ew0KfWv9-1WcsFlMQSgdC">https://groups.google.com/d/msgid/b=
itcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn%40googlegroups.com</a> &lt;=
<a href=3D"https://groups.google.com/d/msgid/bitcoindev/4c1462b7-ea1c-4a36-=
be81-7c3719157fabn%40googlegroups.com?utm_medium=3Demail&amp;utm_source=3Df=
ooter" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"https://w=
ww.google.com/url?hl=3Dfr&amp;q=3Dhttps://groups.google.com/d/msgid/bitcoin=
dev/4c1462b7-ea1c-4a36-be81-7c3719157fabn%2540googlegroups.com?utm_medium%3=
Demail%26utm_source%3Dfooter&amp;source=3Dgmail&amp;ust=3D1711832076950000&=
amp;usg=3DAOvVaw1A1JP9zFfkkPxAMdghR-w4">https://groups.google.com/d/msgid/b=
itcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn%40googlegroups.com?utm_medi=
um=3Demail&amp;utm_source=3Dfooter</a>&gt;.
<br></blockquote></div></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/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.com</a>.=
<br />

------=_Part_113169_1964206021.1711746492894--

------=_Part_113168_262917207.1711746492894--