path: root/d4/cfffbe0725fbbcf1278d01d92c7d0d9bc5c826

Delivery-date: Tue, 12 Mar 2024 03:20:52 -0700
Received: from mail-yb1-f187.google.com ([209.85.219.187])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCJ6NONR3AHRB7GYYCXQMGQEAO6535A@googlegroups.com>)
	id 1rjzFb-0006KI-G3
	for bitcoindev@gnusha.org; Tue, 12 Mar 2024 03:20:52 -0700
Received: by mail-yb1-f187.google.com with SMTP id 3f1490d57ef6-dcdc3db67f0sf7082928276.1
        for <bitcoindev@gnusha.org>; Tue, 12 Mar 2024 03:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1710238845; x=1710843645; 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=3P+LmOkUZYmEBbM+LO7lkf89/Qj6qF6NLVIj55ThiEU=;
        b=mBnlZC8qS5wjH4ZAWIOVRTwfXs5qjK01+TI89IVHIREUBmGKRtpGBg/oIYNBnDIpKG
         AXxnJiFUvLGAbNA2CMY0KYWb7NSxaZX1ccUQTEC9TeKER0vlSklpeBwcWNZoCYT9TBh3
         v+Uw48o27WgYVTfVAKDdgn+w3h7xGfGn4P50JZYz7cR7jlFD8Kc471kttvJExi7DiEP+
         sNIMfb+40K8kYTRG4J5yJRg2bvfc+TDzk+LdeMCCsD1/zCUJVzJJvzmcnutXqtDxvfkU
         W+2sf0am081VyRKzwKMKYOxfrfufsLN8JgiJ6x1Rl6MJQJo97HFWP90Kn7yaPyK/ZiFW
         qVVA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1710238845; x=1710843645; 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=3P+LmOkUZYmEBbM+LO7lkf89/Qj6qF6NLVIj55ThiEU=;
        b=Agysa4GdU3QG3UXGxup23xX3vqWKx7D0Qe7d4Quk06uom0vTpplr91URkqy5qQhBG0
         byL34E3bUm5lWS2tW9OXNbw/sUbbPqT5tErB37FonnhQ0TeGjLm+onNZsnPr67T/g9gW
         1VTWK+P3GJAW0JW+ASYgUKlX1CKLV0uw8A3stV6hxiyDszFQ4hqret/cVyfUz2jexTeI
         KmeeDlLORbXuVLBvJ2PCk+DsUooy+QtoptLmL9SmhqBqOg2rbKDhX+Tqs04H52rBK2Gw
         E5Tr2q/BYbte/4WubIrOmD23Cfk2uMnorXbo2JMeZ4siTGieTP46bWvHCaj1yqADuki7
         ZW8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1710238845; x=1710843645;
        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=3P+LmOkUZYmEBbM+LO7lkf89/Qj6qF6NLVIj55ThiEU=;
        b=GzODJjlpImV2Orxk3GDJUL3yiiHwjxPy7DUCnuSCf3wntbT6tp1D4Y62o/wvmgMYHg
         GmWhuE1cACEZad0RnYMmCL0srwg1mIUL7YNUlDWmIX0OCoqsQEYMWxTiXbdNDgi4gTIf
         nu65pufABJruRb88/BFe6gSNon7Y2UEAc9Ju3gXU9yXEBB+lbnXtbHG67NyEzbRhDbbg
         Gn0k0b25xhjjLwnEArRDSzMCMZOb8280W9WcgJu20PpCe90fMjNa2E4X+AP7FlJj/lhI
         bGTf2ZKaHB2dISB4fGq9HXP9/0qZwVCan/2NKNbGB0kLTAlQ/X/qbmeWH+9TU1boaNWQ
         23iA==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVrE5jl2qj5uvM7M84otBPKQKbUZTLUraX1RSIkBXw6V13ewfCEOk5Ts/QjyIvBLNtDhkWHskyavrMMgLRWxodkYhLQWx4=
X-Gm-Message-State: AOJu0YyfoWuniS7Xd5HbC9ZGyXOmCGNu0axtX3LgMD9mqYWrAGsv7NLI
	Zr5J7V7wAZLNr5XFxXlLHTT/p5CclNwn/rYkTeGSS8nNaE4e6AB/
X-Google-Smtp-Source: AGHT+IF66PpfM6/OdnrYZbFyxYZjP0q/wplsVn3ieldeFSlH9sAHzIhNPZyMye1aoYEgEADZHXy2DA==
X-Received: by 2002:a25:b05:0:b0:dcf:a42b:7e2b with SMTP id 5-20020a250b05000000b00dcfa42b7e2bmr6577369ybl.3.1710238844765;
        Tue, 12 Mar 2024 03:20:44 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:c752:0:b0:dcc:4b24:c0e0 with SMTP id w79-20020a25c752000000b00dcc4b24c0e0ls1654871ybe.0.-pod-prod-06-us;
 Tue, 12 Mar 2024 03:20:44 -0700 (PDT)
X-Received: by 2002:a05:6902:2705:b0:dc6:519b:5425 with SMTP id dz5-20020a056902270500b00dc6519b5425mr2384180ybb.11.1710238843925;
        Tue, 12 Mar 2024 03:20:43 -0700 (PDT)
Received: by 2002:a0d:ea06:0:b0:609:3e5d:63d0 with SMTP id 00721157ae682-60a00a454bams7b3;
        Sun, 10 Mar 2024 10:27:49 -0700 (PDT)
X-Received: by 2002:a81:5e88:0:b0:60a:3c86:f1ea with SMTP id s130-20020a815e88000000b0060a3c86f1eamr151661ywb.2.1710091668590;
        Sun, 10 Mar 2024 10:27:48 -0700 (PDT)
Date: Sun, 10 Mar 2024 10:27:48 -0700 (PDT)
From: Bitcoin Error Log <bitcoinerrorlog@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <ad284018-e99c-4552-88ca-11b9ed340661n@googlegroups.com>
In-Reply-To: <27a5460c-518b-45dd-b48b-570c1681887dn@googlegroups.com>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
 <27a5460c-518b-45dd-b48b-570c1681887dn@googlegroups.com>
Subject: [bitcoindev] Re: Adding New BIP Editors
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_97318_14580928.1710091668229"
X-Original-Sender: bitcoinerrorlog@gmail.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.5 (/)

------=_Part_97318_14580928.1710091668229
Content-Type: multipart/alternative; 
	boundary="----=_Part_97319_810522981.1710091668229"

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

I'd support Atak, Bishop, or Somsen, fwiw.=20

On Sunday, March 10, 2024 at 5:12:16=E2=80=AFPM UTC Michael Folkson wrote:

> +1 on Kanzure and RubenSomsen
>
> I would put my name forward if Kanzure, RubenSomsen weren't willing to do=
=20
> it and I was concerned about who it might be. I don't think it should be=
=20
> someone the Bitcoin dev community isn't familiar with and hasn't proven=
=20
> themselves over a long period of time like Kanzure, RubenSomsen have. The=
re=20
> is the opportunity for a new BIP editor to cause chaos if they were of th=
e=20
> wrong temperament and weren't willing to acknowledge opposing views and=
=20
> perspectives. Both Kanzure and RubenSomsen have proved over a long period=
=20
> of time that although they have their own personal views (like anyone els=
e)=20
> they won't censor transcripts of presentations or emails to the bitcoin-d=
ev=20
> mailing list that contain opposing views to their own. I'm not sure if an=
y=20
> of the other candidates putting themselves forward here tick the same box=
es=20
> as Kanzure and RubenSomsen. I also don't think BIP editors should be Luke=
=20
> Dashjr's personal fiefdom even though overall I personally think Luke has=
=20
> done an excellent job over many years as BIP editor in sometimes difficul=
t=20
> circumstances.
>
> Thanks
> Michael
>
> On Tuesday, February 27, 2024 at 7:27:57=E2=80=AFPM UTC Ava Chow wrote:
>
>> Hi All,=20
>>
>> Following on the recent [discussion][1] about BIP process friction, and=
=20
>> admissions from Luke that he has not had the time to actively work on=20
>> the BIPs repo ([2], [3]), I think it is prudent for us to look at adding=
=20
>> more BIPs editors. These people would have the same permissions and=20
>> responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs=
=20
>> adding new BIPs, merge PRs to fix existing BIPs,and all other=20
>> responsibilities as described in [BIP 2][4]. I think this would=20
>> significantly help get through the backlog of BIPs PRs, and responding=
=20
>> to them in a timely manner to significantly reduce the friction of=20
>> getting BIPs changes merged. Of course, this would require that all BIP=
=20
>> editors agree on the numbering scheme so that BIPs continue to be=20
>> numbered consistently.=20
>>
>> Considering the responsibilities of these tasks, I think any new BIP=20
>> editors should be people who have a history of following and being=20
>> involved in Bitcoin development, as well as being known to evaluate=20
>> proposals objectively, and of course, are willing to do the job. With=20
>> that in mind, I think both Kanzure and RubenSomsen are very good=20
>> candidates to be BIP editors, and having both of them working on the=20
>> BIPs repo would greatly benefit all of us.=20
>>
>> Thanks,=20
>> Ava=20
>>
>> [1]:=20
>>
>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022=
289.html=20
>> [2]:=20
>>
>> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022=
291.html=20
>> [3]: https://twitter.com/LukeDashjr/status/1761127972302459000=20
>> [4]:=20
>>
>> https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-cont=
ent-BIP_Editor_Responsibilities__Workflow=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/ad284018-e99c-4552-88ca-11b9ed340661n%40googlegroups.com.

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

I'd support Atak, Bishop, or Somsen, fwiw.=C2=A0<div><br /></div><div class=
=3D"gmail_quote"><div dir=3D"auto" class=3D"gmail_attr">On Sunday, March 10=
, 2024 at 5:12:16=E2=80=AFPM UTC Michael Folkson wrote:<br/></div><blockquo=
te class=3D"gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px sol=
id rgb(204, 204, 204); padding-left: 1ex;">+1 on Kanzure and RubenSomsen<di=
v><br></div><div>I would put my name forward if Kanzure, RubenSomsen weren&=
#39;t willing to do it and I was concerned about who it might be. I don&#39=
;t think it should be someone the Bitcoin dev community isn&#39;t familiar =
with and hasn&#39;t proven themselves over a long period of time like Kanzu=
re, RubenSomsen have. There is the opportunity for a new BIP editor to caus=
e chaos if they were of the wrong temperament and weren&#39;t willing to ac=
knowledge opposing views and perspectives. Both Kanzure and RubenSomsen hav=
e proved over a long period of time that although they have their own perso=
nal views (like anyone else) they won&#39;t censor transcripts of presentat=
ions or emails to the bitcoin-dev mailing list that contain opposing views =
to their own. I&#39;m not sure if any of the other candidates putting thems=
elves forward here tick the same boxes as Kanzure and RubenSomsen. I also d=
on&#39;t think BIP editors should be Luke Dashjr&#39;s personal fiefdom eve=
n though overall I personally think Luke has done an excellent job over man=
y years as BIP editor in sometimes difficult circumstances.</div><div><br><=
/div><div>Thanks</div><div>Michael<br><br></div><div class=3D"gmail_quote">=
<div dir=3D"auto" class=3D"gmail_attr">On Tuesday, February 27, 2024 at 7:2=
7:57=E2=80=AFPM UTC Ava Chow wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Hi All,
<br>
<br>Following on the recent [discussion][1] about BIP process friction, and=
=20
<br>admissions from Luke that he has not had the time to actively work on=
=20
<br>the BIPs repo ([2], [3]), I think it is prudent for us to look at addin=
g=20
<br>more BIPs editors. These people would have the same permissions and=20
<br>responsibilities that Luke has, i.e. can assign BIP numbers, merge PRs=
=20
<br>adding new BIPs, merge PRs to fix existing BIPs,and all other=20
<br>responsibilities as described in [BIP 2][4]. I think this would=20
<br>significantly help get through the backlog of BIPs PRs, and responding=
=20
<br>to them in a timely manner to significantly reduce the friction of=20
<br>getting BIPs changes merged. Of course, this would require that all BIP=
=20
<br>editors agree on the numbering scheme so that BIPs continue to be=20
<br>numbered consistently.
<br>
<br>Considering the responsibilities of these tasks, I think any new BIP=20
<br>editors should be people who have a history of following and being=20
<br>involved in Bitcoin development, as well as being known to evaluate=20
<br>proposals objectively, and of course, are willing to do the job. With=
=20
<br>that in mind, I think both Kanzure and RubenSomsen are very good=20
<br>candidates to be BIP editors, and having both of them working on the=20
<br>BIPs repo would greatly benefit all of us.
<br>
<br>Thanks,
<br>Ava
<br>
<br>[1]:=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024=
-January/022289.html" rel=3D"nofollow" target=3D"_blank" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundat=
ion.org/pipermail/bitcoin-dev/2024-January/022289.html&amp;source=3Dgmail&a=
mp;ust=3D1710177974989000&amp;usg=3DAOvVaw0f7Buhl1zrSTvZyBW8o3bu">https://l=
ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022289.html</a>
<br>[2]:=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024=
-January/022291.html" rel=3D"nofollow" target=3D"_blank" data-saferedirectu=
rl=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundat=
ion.org/pipermail/bitcoin-dev/2024-January/022291.html&amp;source=3Dgmail&a=
mp;ust=3D1710177974989000&amp;usg=3DAOvVaw39DncPVhidZ29Ajr78-XS1">https://l=
ists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/022291.html</a>
<br>[3]: <a href=3D"https://twitter.com/LukeDashjr/status/17611279723024590=
00" rel=3D"nofollow" target=3D"_blank" data-saferedirecturl=3D"https://www.=
google.com/url?hl=3Den&amp;q=3Dhttps://twitter.com/LukeDashjr/status/176112=
7972302459000&amp;source=3Dgmail&amp;ust=3D1710177974989000&amp;usg=3DAOvVa=
w3LeNVUDAwA0fTcEsRikr38">https://twitter.com/LukeDashjr/status/176112797230=
2459000</a>
<br>[4]:=20
<br><a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0002.mediawi=
ki#user-content-BIP_Editor_Responsibilities__Workflow" rel=3D"nofollow" tar=
get=3D"_blank" data-saferedirecturl=3D"https://www.google.com/url?hl=3Den&a=
mp;q=3Dhttps://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki%23use=
r-content-BIP_Editor_Responsibilities__Workflow&amp;source=3Dgmail&amp;ust=
=3D1710177974989000&amp;usg=3DAOvVaw2_yY_GSBosX4jBZu23jfAI">https://github.=
com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-content-BIP_Editor_Res=
ponsibilities__Workflow</a>
<br>
<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/ad284018-e99c-4552-88ca-11b9ed340661n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/ad284018-e99c-4552-88ca-11b9ed340661n%40googlegroups.com</a>.=
<br />

------=_Part_97319_810522981.1710091668229--

------=_Part_97318_14580928.1710091668229--