From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 28 Mar 2024 13:19:17 -0700 Received: from mail-oo1-f59.google.com ([209.85.161.59]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rpwDU-0000FR-CY for bitcoindev@gnusha.org; Thu, 28 Mar 2024 13:19:17 -0700 Received: by mail-oo1-f59.google.com with SMTP id 006d021491bc7-5a55e232107sf867953eaf.3 for ; Thu, 28 Mar 2024 13:19:16 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1711657150; cv=pass; d=google.com; s=arc-20160816; b=0YPHLyCtTgqKplQUzZvh1/mN9IFWWL8vsWYhFMxdPF0F1+TzERtNHk+sAFK58XKwVQ ryziRrh4vsPjMrQ4YAub69kvAFJxJfNYzDuw3f6wf44r6NQE5rzvsCsiC6PIyT49pn64 OYs7xVWZHDii9uoJ8oe9lv6SG6kWq0u6WGeXgiAAT9dAn/GzrGNBiqLYuXZdLY6ONuiA P57nMUJi7R6p15nT03cwa67xO5Wjftakc1mJgs5v3UGtxhoYdND/S2jnOF2dWPcB1PTt LSQzfOS3BYCp/xeivRoD7uxvlZCdiknf8R1tktOU2jFjSfozC6rt6f47jrgwv8bboEst d5QA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:sender:dkim-signature :dkim-signature; bh=bs6jUfGRPoxnLF+cqSXMu5R5Id6hVAesb0VDhKB3iRg=; fh=CTrMPHMEGLLxm6nclx4ukcihvSI2DMN7k12dBEupnZM=; b=yb4uMQoU0/lV18bwVpuSkv/bSunj8UnCRKiiHJizSaQ9Tst+Wxd0PcE7OK8n35zqN7 rB9K2YhBuzw4zbsj5gtmRrQeHKffzCrZyAEodzVOWIJbAoYvg7W+Hqwf+j3RNboUyO5j SEdBtQLQk7/Ds5Rey484MoUcpMhj1MgdqaYrQ/OtFw6TCWSabr0nvT5qJsCKl6qngL5b xwfJqbOlgglB48/KR0v4o54p72kwybSFJLVGOO8un7Bycrn5qRcQLxM7iDS5bG7Tr3gV P70NK628sJp5N+gdS5OL6w3cEhA0u6117/TvNJ/EKZBSlnst1mHvmS57Mq+pQMUc2Fr3 5iSg==; darn=gnusha.org ARC-Authentication-Results: i=2; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=h9ivP+KX; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d32 as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1711657150; x=1712261950; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:sender:from:to:cc:subject:date:message-id :reply-to; bh=bs6jUfGRPoxnLF+cqSXMu5R5Id6hVAesb0VDhKB3iRg=; b=f+0Wf0BQzHcDaPzaoWi0yJKPt46hWOhPWCLsO5P7grJvQFGwNLpMvrykopaPd93FVW +F8mzeC8bDtzWRYgjo2e7EHf1l9T7k7C/ep8+T5oj5pxgfrJ7rjnNDEV7cTEOZBVVWs0 WjrDLQz5BAQxPmpcYvOFHom9B6GnY8MWy1Ft+UiZUhSwUaccWU3ICAMe52UKNAFGemal yGubPdQqsCH+vp3fB5F4JfgR5EtwOXXDmkCPCkg5zBqyeBaFsf2NIp537V1fTxBZRa1I qb2ang5J0JTCLB5h2gEi/slGRwx0odg9Rxy3nxxl6qUIPXh3V0D8IBmVtZ7IwonlCuAU uTsA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711657150; x=1712261950; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bs6jUfGRPoxnLF+cqSXMu5R5Id6hVAesb0VDhKB3iRg=; b=Umcop0+cGXaBAO4Mqs9qR/1G2kRbDVDhDcH7nxDt+Y0mUkERyVtsb9uW5KrIWdTjgz o7G7Di0a2Y1phKOXJr2YIUWhJGBcxS4tJzmuLsqpGcG3PP5jlPxJi+K8LgbyAFL4EMLD cvngige2VA7QR67dnbqaiB+b0+PW2w5UOhVWPzLyyXjL1cDsDZ/MsOA0qu1bwRCE/3l3 UAdYUdhtDgdU0lfKH0mH7mI5zu3qBKRHHMyLKF4emGdvmoww2laYRu37WoXKkjrZVyXq paTsx7o5NdkFL5FB/k6nVPlAyrbK0z6Wka+pqRVlEMJvOVsnsj9QpcAp+PV+fntWDIPT EAZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711657150; x=1712261950; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-authentication-results :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-beenthere:x-gm-message-state:sender:from :to:cc:subject:date:message-id:reply-to; bh=bs6jUfGRPoxnLF+cqSXMu5R5Id6hVAesb0VDhKB3iRg=; b=CiXWKA4OnCr9s8ZcfF85Mvsuu3+PBGzn1tD08t45DCyXHk8kJFaxL73cPmYDX1bhFI jU6iX1udsFLZDYs/QsizS6s+q6RZIDcu58hLeSPh8qnHieGcEgNFjY3I4DqiNrW0s3uP sUCbDyMWhOkh4t6PHzNHQrXThyHwGGI4oEeWxewc/nFBbSJQOax7u8hU1J8XNcTcUea9 m/pDw7JzkTidEgx+8YSSMeTQbsvXD6rrLDHoZGrCA8jItYH2scVX6D5hfROiN73BReo6 ZNrqe/ToMhVN4DeL6ApNSziYZZWPN2xF3HOCQvH7VRt5XjfpijLQImzDzWPqpoxilv0E /eUA== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=2; AJvYcCWAY93gJJhlDRayLs3ALt7eKxtW7GkSi2L8e2cIAxJulzHfHw2FomPLY58jyY/PysjIKzXMS3RrOPt3nYZP66owF49x4sQ= X-Gm-Message-State: AOJu0Ywu7bCoVaxjQbYjK3IV+DRbOkAuTsG1kmzpY3Q1ZxZQZIbyPo2N 7Ilfexozwqi4WK9AzvkNJXHafqfcVxlR/o1aNJZ7RNBg7wFty3p4 X-Google-Smtp-Source: AGHT+IFLCh5p6oVdn5M9lVyOOOH1xSExQC9LyO/4GyQ/LBuHsYOEXjDiKXD+LxJchKJMU6xRspogrg== X-Received: by 2002:a05:6820:1f01:b0:5a5:2244:6b1c with SMTP id dl1-20020a0568201f0100b005a522446b1cmr204364oob.9.1711657150082; Thu, 28 Mar 2024 13:19:10 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a4a:c18a:0:b0:5a4:be52:5f48 with SMTP id w10-20020a4ac18a000000b005a4be525f48ls419544oop.0.-pod-prod-00-us; Thu, 28 Mar 2024 13:19:09 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWG2GuHGWSk4Auw36OMImifgsLNr0OhdCJLqXWz02dYGDTzuRoZBDlSqXhaYaWV320wiEfGiEL8IdFN7V3dOYmWD4HPb+ptHgCWYKY= X-Received: by 2002:a05:6820:1614:b0:5a5:2923:30c7 with SMTP id bb20-20020a056820161400b005a5292330c7mr42518oob.0.1711657149264; Thu, 28 Mar 2024 13:19:09 -0700 (PDT) Received: by 2002:a05:6808:219c:b0:3c3:cc09:ef6d with SMTP id 5614622812f47-3c3ef57ad9cmsb6e; Thu, 28 Mar 2024 12:42:28 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCU4SYmqml1Oo/CruCR0NicB/htDwWflO3bNDuk9HXN8NxFPTCjmQcUXQnxOYEKI/Wy40mnzjz8iQMrX+JnSPQ1bFHpCYIhZY6/vvMs= X-Received: by 2002:a17:902:d2c5:b0:1e0:b76b:cfb8 with SMTP id n5-20020a170902d2c500b001e0b76bcfb8mr589014plc.19.1711654946888; Thu, 28 Mar 2024 12:42:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1711654946; cv=none; d=google.com; s=arc-20160816; b=yQuWOqR1Bu5xWssmjq30CkX9+hXJyTli+BJcHett2yHYD1OLuvNeoA6E7srrIVmCjX OLWZAQj2cO/qPjeUFy7boM3vZk2LkABX9to7YxOp9FBmLpw/tx74WKwAYEZeszgCzS9b gHfVsmy55ceFbE5EShoo7XWjCSymtKeq3uY9N84+ZNzhvbDQvJRzktWT6l5d3iHXgMET Ah88vhHs/BZxfe6EQEbSt3hTfYiHXcStglT/O/hixEezhFNMJpmCae3yyyjlmXrd15+o IFV0hvXAVoygc+s13YVkZmZ23rf6DcP0ksjAhCkKsYm9mJQqm1Vtrr0esdI/Vdxqd0y2 SlDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=gmRQtym+SVUOWxXHAL43bQW8F9LgjLJ6b/QP4vq41so=; fh=EI4o13+DXJE4rLlxYwERaInyZLyUG0EIYbXWd4vq9AM=; b=vrKB16sTDwZmBy0ewOf6nBEMtiYurUGGbwLb/OB+lm8O5y8bkTNJ6y0RsfaWgOxGID l1ufMP0ziuYmafBYKmidv8zGkiDValNVHceeSrJ6oGDhYbNZ2GgRWvxs0w9HWhDG4KFu OwgoYjUbVnD+8caOB86ETCVeMOpjZgOiZLxTQ/NtXEW5eiJuVFbZc1dTxsulO5Lxvj+V s4m4Ly4SDFuFrZNHzuE28abo9gC2XUVdhS0SZo8j3EVuT5zuQgqidrwJVOjtSNA1i6oK V8ihGBMdPrVDuNyb+kBXRIYWfVn3+lusdAlM//U4CsE8zKF3iXoAy8WPBMU6v188xk69 GV8A==; dara=google.com ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=h9ivP+KX; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d32 as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com. [2607:f8b0:4864:20::d32]) by gmr-mx.google.com with ESMTPS id ku3-20020a170903288300b001dd6f638c0bsi146800plb.2.2024.03.28.12.42.26 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Mar 2024 12:42:26 -0700 (PDT) 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; Received: by mail-io1-xd32.google.com with SMTP id ca18e2360f4ac-7d026c0a08aso56442139f.1 for ; Thu, 28 Mar 2024 12:42:26 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCXUnOPagg9iP8mr0efa6cuhtsFBRhxGY0/NALczocoaxQ1ERgIqVILJOACVmxIhIYStYrxcYH2CSlcBxBCemndI2MrrxrGhHHrGgbY= X-Received: by 2002:a6b:4e18:0:b0:7d0:86da:8511 with SMTP id c24-20020a6b4e18000000b007d086da8511mr183457iob.14.1711654946109; Thu, 28 Mar 2024 12:42:26 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: From: Antoine Riard Date: Thu, 28 Mar 2024 19:42:15 +0000 Message-ID: Subject: Re: [bitcoindev] Re: Adding New BIP Editors To: Brandon Black Cc: Matt Corallo , Murch , bitcoindev@googlegroups.com Content-Type: multipart/alternative; boundary="0000000000000a84300614bdb96c" X-Original-Sender: antoine.riard@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=h9ivP+KX; spf=pass (google.com: domain of antoine.riard@gmail.com designates 2607:f8b0:4864:20::d32 as permitted sender) smtp.mailfrom=antoine.riard@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=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 (/) --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 = 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
Hi all,

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.

There is a CoreDev editi= on happening in April and it's better to not conflict the appointment o= f new BIP editors with any of the CoreDev dates by transparency towards the= wider community.
This avoids=C2=A0last-minute "Hong-Kong Ag= reement" 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 "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" styl= e privileges for PR / issues sorting.
I think it's good to le= t technical relevance=C2=A0of the proposal be appreciated by the wider comm= unity, 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=C2=A0(i t= hink it's good to have someone for all inter-compatibility clients thin= gs)
- Murch (top bitcoin stackoverflow=C2=A0contributor)
- Jon Atack (much experience with bitcoin core codebase and great respons= iveness too)

As new BIP "decentralized PM&quo= t;, I'm supporting the following list:
- Seccour=C2=A0
<= div>
I don't know the Bitcoin technical credentials of Gr= eg Tonoski.

I think a good thing is to have no= t-only US-based BIP editors for higher timezones coverage and BIP process r= esponsiveness.

Best,
Antoine=C2=A0
=


Le=C2=A0jeu. 28 mars 2024 =C3=A0=C2=A016:16, Brandon Black = <freedom@reardencode.com&= gt; a =C3=A9crit=C2=A0:
I agree with Matt's s= uggestions, 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 fin= e BIP
> editors, I'd suggest Kanzure and Murch as clear candidates over ot= hers:
>
>=C2=A0 * Kanzure has been around for longer than any other candidate as= far as 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<= br> > responsive, which I believe is part of the goal in appointing new edit= ors
> here.
>=C2=A0 * Murch similarly has lots of experience dealing with lots of va= rious ideas
> around Bitcoin, but importantly here also has worked extensively to do= cument
> appropriate terminology for all things Bitcoin [1]. This makes him an<= br> > excellent copy editor of Bitcoin technical proposals, which is basical= ly 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 cr= iteria 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 Goog= le Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bitcoindev/cuMZ77KEQAA/unsubscribe<= /a>.
To unsubscribe from this group and all its topics, send an email to bit= coindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZgWRu32FXzqqg69V%4= 0console.

--
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://group= s.google.com/d/msgid/bitcoindev/CALZpt%2BE8DohYEJ9aO%2BFiF6%2BEKMCP5oEbHSKS= Xpq0VKVBhJLhrw%40mail.gmail.com.
--0000000000000a84300614bdb96c--