path: root/76/748a0bb88f59787f7c612f50be2612d9b4789b

Delivery-date: Sun, 10 Mar 2024 10:12:23 -0700
Received: from mail-yb1-f191.google.com ([209.85.219.191])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCYNLXGV3AMRB4GTW6XQMGQEIYVCRXA@googlegroups.com>)
	id 1rjMil-0006qo-25
	for bitcoindev@gnusha.org; Sun, 10 Mar 2024 10:12:23 -0700
Received: by mail-yb1-f191.google.com with SMTP id 3f1490d57ef6-dc6b2682870sf6041469276.0
        for <bitcoindev@gnusha.org>; Sun, 10 Mar 2024 10:12:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1710090737; x=1710695537; 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=zktEatWton3KO9Y7u0sAbn4PE0M5h+/W+vmbeATXOFA=;
        b=Ekv/5flj/ohW2OtMk+ddgrLNSoHn657zFuf0HsSDFSIHotpsbwsyt5v+14/MW2ns+k
         GpUpFBYFlDtpnmC3hVwT+bTALqFOWpnOjXX0j3+NHaDdsgjzUo/7VlxXyLkFaVNLYrnj
         UO4QS7fp5Qr6ztWRflyu74Y6RA+lWZD1Ao8Jec4DCjAyaz60ZrO3rKjEoaG1Q4rwmBfg
         fmDTHYF7gjSL/AN9YymhVD2EXC1AXYt53Gwgr7iGdnGJkH0fe4yjlfWBexTP67E0vbFd
         OxABbhE26jvzfQO9fuvupwJZL57ly+DeCfbLbylLH2mTUAHgf2hAW2v3GEKLjcEhNicK
         8/HQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1710090737; x=1710695537; 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=zktEatWton3KO9Y7u0sAbn4PE0M5h+/W+vmbeATXOFA=;
        b=FGSI4so9IIfa6E0MDUpC7agcm5pgRIWKfBS6m2MtmT/gV0U0bQUaiVHqwrSUZ+oTPS
         XD/iQyjXOXM8DFSRJXa+vJ6j/gjfhURJi1+Zii/LiqM8XiVtJx0ZmuCTpYSwN6qYT15z
         BZaJdnjZsGR/47MuZjVF2CLaN15PsmE9zFIniO2eivg7v8l0kCBXK6PNPQWpqEkKLQCO
         7uA25qqAjB/9FMWYEOk3aUNiXWO8KdEmWb3oqw1rdzyUr1VXZ0DOY3sZWKY8EydnARBB
         IWrps8yQ0sBbPrEMmA4zPpr9py1zHseTZ5Nzqb/Y5byKFEw6nmf+xudybsVpI6jnWkNM
         F+wQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1710090737; x=1710695537;
        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=zktEatWton3KO9Y7u0sAbn4PE0M5h+/W+vmbeATXOFA=;
        b=aPB6Pvz/eC40Vl7zOKYQi9MueRkfFbHAMiuNWqaxwrKXq/o6aM5jrsnvNIwkwH0Cqg
         xKrJ/ZfiggEb7UG33V18N/ashuqpmaH3zJGqUW3xJPubxkOXIAtQhtH5aJZ6fw6uqGrr
         6OkXsc2ASjlIGb+O8cLLKrxT7cE027Zke8WlVlyhnwlNOeX1o5+AsAm8fUQVUEx3kOae
         XHcPPDstDHBi/r5KWrhZMecsy1s+gEwCWlpyKnFHH2cEoY0fY+uVH9rjuJ5Y77m/Wt0W
         YIm60sBgBpn/cX48lYB0swkWgIBQOmQaFkaTj9qE5ICT0kQWizXikb0gz+I64fd5q97b
         TJQQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVt2g/SjIdrHWyVPE3Wp8RF61dkAKWIYN3fW/f5d17bbVuz3CvLx5sina1SaxDZ/aoaaLUv6iI67jgqM3K+X36V1vo3aeM=
X-Gm-Message-State: AOJu0YwQdlnmXJAmPN92gsH5wmoLPJB/LtJkWHHtXKC+0BjJlEU6+EU7
	Q66W0n2jO4iknf4O6eASJyqkG0U1ynhT0tBxXL8GqmNo282g4NME
X-Google-Smtp-Source: AGHT+IEA6hiMB+ysDQg+DJ3ON7OVIIvf0LV7WVjZExXZQNp+ZXt4Az2tuvSuSEZQASk//rej7PR+IA==
X-Received: by 2002:a25:71d6:0:b0:dcc:d5aa:af36 with SMTP id m205-20020a2571d6000000b00dccd5aaaf36mr2853700ybc.44.1710090736701;
        Sun, 10 Mar 2024 10:12:16 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:ce51:0:b0:dcb:b370:7d12 with SMTP id x78-20020a25ce51000000b00dcbb3707d12ls291560ybe.1.-pod-prod-00-us;
 Sun, 10 Mar 2024 10:12:15 -0700 (PDT)
X-Received: by 2002:a81:4ed5:0:b0:609:ed3b:f3bd with SMTP id c204-20020a814ed5000000b00609ed3bf3bdmr1304587ywb.3.1710090735713;
        Sun, 10 Mar 2024 10:12:15 -0700 (PDT)
Received: by 2002:a0d:ea06:0:b0:609:3e5d:63d0 with SMTP id 00721157ae682-60a00a454bams7b3;
        Sat, 9 Mar 2024 02:46:58 -0800 (PST)
X-Received: by 2002:a05:6902:1886:b0:dcd:3172:7279 with SMTP id cj6-20020a056902188600b00dcd31727279mr385944ybb.8.1709981217106;
        Sat, 09 Mar 2024 02:46:57 -0800 (PST)
Date: Sat, 9 Mar 2024 02:46:56 -0800 (PST)
From: Michael Folkson <michaelfolkson@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <27a5460c-518b-45dd-b48b-570c1681887dn@googlegroups.com>
In-Reply-To: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
Subject: [bitcoindev] Re: Adding New BIP Editors
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_190310_1499141845.1709981216691"
X-Original-Sender: michaelfolkson@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_190310_1499141845.1709981216691
Content-Type: multipart/alternative; 
	boundary="----=_Part_190311_1215633467.1709981216691"

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

+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. There=
=20
is the opportunity for a new BIP editor to cause chaos if they were of the=
=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 else)=
=20
they won't censor transcripts of presentations or emails to the bitcoin-dev=
=20
mailing list that contain opposing views to their own. I'm not sure if any=
=20
of the other candidates putting themselves forward here tick the same boxes=
=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 difficult=
=20
circumstances.

Thanks
Michael

On Tuesday, February 27, 2024 at 7:27:57=E2=80=AFPM UTC Ava Chow wrote:

> Hi All,
>
> 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.
>
> 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.
>
> Thanks,
> Ava
>
> [1]:=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/0222=
89.html
> [2]:=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2024-January/0222=
91.html
> [3]: https://twitter.com/LukeDashjr/status/1761127972302459000
> [4]:=20
>
> https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-conte=
nt-BIP_Editor_Responsibilities__Workflow
>
>

--=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/27a5460c-518b-45dd-b48b-570c1681887dn%40googlegroups.com.

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

+1 on Kanzure and RubenSomsen<div><br /></div><div>I would put my name forw=
ard if Kanzure, RubenSomsen weren't willing to do it and I was concerned ab=
out who it might be. I don't think it should be someone the Bitcoin dev com=
munity isn't familiar with and hasn't proven themselves over a long period =
of time like Kanzure, RubenSomsen have. There is the opportunity for a new =
BIP editor to cause chaos if they were of the wrong temperament and weren't=
 willing to acknowledge opposing views and perspectives. Both Kanzure and R=
ubenSomsen have proved over a long period of time that although they have t=
heir own personal views (like anyone else) they won't censor transcripts of=
 presentations or emails to the bitcoin-dev mailing list that contain oppos=
ing views to their own. I'm not sure if any of the other candidates putting=
 themselves forward here tick the same boxes as Kanzure and RubenSomsen. I =
also don't think BIP editors should be Luke Dashjr's personal fiefdom even =
though overall I personally think Luke has done an excellent job over many =
years as BIP editor in sometimes difficult circumstances.</div><div><br /><=
/div><div>Thanks</div><div>Michael<br /><br /></div><div class=3D"gmail_quo=
te"><div dir=3D"auto" class=3D"gmail_attr">On Tuesday, February 27, 2024 at=
 7:27:57=E2=80=AFPM UTC Ava Chow wrote:<br/></div><blockquote class=3D"gmai=
l_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-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" target=3D"_blank" rel=3D"nofollow" 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=3D1710066151779000&amp;usg=3DAOvVaw0KH6aunmNJbolNGC0VZUGL">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" target=3D"_blank" rel=3D"nofollow" 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=3D1710066151779000&amp;usg=3DAOvVaw2eSzSjdsySbLxKtBL5dfX4">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" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=3D"https://www.=
google.com/url?hl=3Den&amp;q=3Dhttps://twitter.com/LukeDashjr/status/176112=
7972302459000&amp;source=3Dgmail&amp;ust=3D1710066151779000&amp;usg=3DAOvVa=
w05Bh0gLtedyjtXO4UxheJf">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" target=3D"_blank" re=
l=3D"nofollow" 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=
=3D1710066151779000&amp;usg=3DAOvVaw1eadH7goOItPGcKx0LrAtH">https://github.=
com/bitcoin/bips/blob/master/bip-0002.mediawiki#user-content-BIP_Editor_Res=
ponsibilities__Workflow</a>
<br>
<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/27a5460c-518b-45dd-b48b-570c1681887dn%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/27a5460c-518b-45dd-b48b-570c1681887dn%40googlegroups.com</a>.=
<br />

------=_Part_190311_1215633467.1709981216691--

------=_Part_190310_1499141845.1709981216691--