From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 29 Mar 2024 14:14:31 -0700 Received: from mail-yw1-f187.google.com ([209.85.128.187]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rqJYU-0004IF-Df for bitcoindev@gnusha.org; Fri, 29 Mar 2024 14:14:30 -0700 Received: by mail-yw1-f187.google.com with SMTP id 00721157ae682-60ccc3cfa39sf41394017b3.2 for ; Fri, 29 Mar 2024 14:14:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1711746864; x=1712351664; 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=momj5VnIp8o7J1OuIm1vgwbLfRtjVHUgPO4JxcGYSTI=; b=QPUUA22BHwEaDOGV2A4QeMD7ziWSzkTDqTdyR8W0UIEPI1DK+DOetjsVMoVstFVieB H2xOVFHUCGM4+CzR/4QgLvAZ5JWn9VvA2z0AsG6r3dSQReu5UQMqFgMWiu9j6T18ohcc RvAOJfMYtB2SPPsRePZtYrEVKYxO8II5CxQRt5b8thjcvsSOzUsj/9aO71PRq9+hcbmA QZtDKWfc8Oj1+HYqvdxyWxE9AbBhYJhaWB4qa5CLdzdoY1TzxWXYwacqHEACYLZO+zL2 HGlIJOJz0dX78b+bfgkay+q4FdjRP4OnWNVlzGM8nURvbfEv02rPE3sCkFiaO1eK7oIK 1uWg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711746864; x=1712351664; 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=momj5VnIp8o7J1OuIm1vgwbLfRtjVHUgPO4JxcGYSTI=; b=PcVcHL7QNy4/1Se+P2zPJsDiCdNyJt8QWujOi+Z1Rem5JUrsflW0fiG1hZFl66tkW+ jmgx6sCHT4jLbb6Bx9ILAnoIIHKXPMRMaIJ1/0i4qaydemP+iCo609klS3DRPiqyBd2K BMlxnmkNo363P+w/RojGWtwZI5Ty65ahVROkw3pIVuLaSgI1lCFBzGtu2qqdIlOP1zp/ q8XemX+uTEHj/8ee8IrCePuNBKhKbBXDzX1pnza0JwHN6znhc8EmTiwX5CvnrV4qWdzd mdpMdn1/0z9bA7Nk3dRkB35zgekAq601f5HxKZ5Lly5+M3AqyFJXsm6CDl1SV3SQTO11 7uWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711746864; x=1712351664; 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=momj5VnIp8o7J1OuIm1vgwbLfRtjVHUgPO4JxcGYSTI=; b=I0X5VgsFlAb8mxa6KDmcOB59I7Euh+UXzNHr8tChoMjcX8gz7Le1AMyuiWotPbsFf2 +f7wGwGhX4kcmRyg9eZeZd3PojtgbdKzCi4PgJOC1bDMtzUenNxGBcQRh0Ou+5UucrBk 99igRJX+z2ZmKPNcZW+CLBKJgfVh6eDLgUe+zFSg8QrMwZWd0XdrAb4eJFXTRZL3V3c+ uFc8dpnsAwDD+02TFF1JSORjAD+vHL05ooO4LlrkCz9Bi2ypg7TM5+acjuzmhDNEpDjc CIt7diCDy4MscxAQ/R9TgEGis0IHurylF+7f49ZauOnVvZFeBJWiYAXUC+tZeX3Lc3Io 8nFA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCWo75zzeQq+ZJ4bLc7upDitOsByqm1k/wgZ0BBkmPy7xlhW+kbBvymlLtGourKhC3TSy2ERUChutCvtiLyc3JcFm3BycoE= X-Gm-Message-State: AOJu0YyhbNyYIRCtmtJGosxoHHGrlaLaCQAVk/V+9nV37dONZRDtC5De BegKhCyj7To8yEsdQEOm/mD2336Qcc7gWyKdhQVI8unxuBT/8YSE X-Google-Smtp-Source: AGHT+IF8T4oRxQ5Oj62b/4s59AwH0cywqvDe5lLlHmPTcUu/8uJ7wd8IR3Kr0TE5bFMAwmNXetynlQ== X-Received: by 2002:a25:c4c3:0:b0:dc7:5018:4022 with SMTP id u186-20020a25c4c3000000b00dc750184022mr3424095ybf.44.1711746864198; Fri, 29 Mar 2024 14:14:24 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a25:abef:0:b0:dcd:a08f:c840 with SMTP id v102-20020a25abef000000b00dcda08fc840ls793983ybi.1.-pod-prod-09-us; Fri, 29 Mar 2024 14:14:23 -0700 (PDT) X-Received: by 2002:a05:6902:e06:b0:dcc:c57c:8873 with SMTP id df6-20020a0569020e0600b00dccc57c8873mr1005482ybb.9.1711746863035; Fri, 29 Mar 2024 14:14:23 -0700 (PDT) Received: by 2002:a05:690c:9e:b0:611:296f:7027 with SMTP id 00721157ae682-614318a78d8ms7b3; Fri, 29 Mar 2024 14:08:15 -0700 (PDT) X-Received: by 2002:a05:6902:18d4:b0:dc6:f877:ea7b with SMTP id ck20-20020a05690218d400b00dc6f877ea7bmr1018672ybb.9.1711746493359; Fri, 29 Mar 2024 14:08:13 -0700 (PDT) Date: Fri, 29 Mar 2024 14:08:12 -0700 (PDT) From: Antoine Riard To: Bitcoin Development Mailing List Message-Id: In-Reply-To: <846b668f-8386-4869-a3b1-55d346efbea1n@googlegroups.com> References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com> <9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org> <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de> <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" X-Original-Sender: antoine.riard@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_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 .=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 >=C2=A0Roasbeef's work on alternative clients and lightning make him technicall= y=C2=A0
= useful

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).
= 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.
Especially for= all matters related to compatibility and deployment.

> 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
> independence sometimes required betwe= en Core and the BIP process

=
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<= /div>
override any BIP merging decision, or eve= n remove on the flight BIP editors rights in case of conflicts or controver= sies.=C2=A0If you're raising = the issue that the BIP repository should be moved to its own GH repository = I think it's a valuable point.

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.

Best,
Antoi= ne


Le vendredi 29 mars 2024 =C3=A0 12:33:09 UTC, /d= ev /fd0 a =C3=A9crit=C2=A0:
Justification:

1. Jon Atack: Good at avoi= ding controversies and technical documentation.
2. Roasbeef: Sinc= e BIPs are not just related to bitcoin core, it's good to have btcd mai= ntainer as a BIP editor.

On Friday, March 29, 2024 at 1:47:41=E2=80= =AFAM UTC+5:30 Matt Corallo wrote:
Please provide justification rather than simply saying "I= like Bob!".

Matt

On 3/28/24 12:09 PM, /dev /fd0 wrote:
> I support Jon Atack and Roasbeef from this list.
>=20
> On Thursday, March 28, 2024 at 6:57:53=E2=80=AFPM UTC+5:30 Murch w= rote:
>=20
> I just went through the thread, previously mentioned were:
>=20
> - Kanzure
> - Ruben Somsen
> - Greg Tonoski
> - Jon Atack
> - Roasbeef
> - Seccour
>=20
> And Matt just suggested me for the role. Hope I didn=E2=80=99t= overlook anyone.
>=20
> On 3/27/24 19:39, John C. Vernaleo wrote:
> > That said, I would find it helpful if someone could go t= hrough the
> > thread and list all the people who've been proposed = so people know who
> > they should be thinking about.
>=20
> --=20
> You received this message because you are subscribed to the Google= Groups "Bitcoin Development=20
> Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, = send an email to=20
> bitcoindev+...@googlegroups.com <mailto= :bitcoindev+...@googlegroups.com>.
> To view this discussion on the web visit=20
> https://groups.google.com/d/msgid/b= itcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn%40googlegroups.com <= https://groups.google.com/d/msgid/b= itcoindev/4c1462b7-ea1c-4a36-be81-7c3719157fabn%40googlegroups.com?utm_medi= um=3Demail&utm_source=3Dfooter>.

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/f8fa1a55-644f-4cf1-b8c1-4fdef22d1869n%40googlegroups.com.=
------=_Part_113169_1964206021.1711746492894-- ------=_Part_113168_262917207.1711746492894--