Delivery-date: Sat, 20 Apr 2024 12:30:42 -0700
Received-SPF: pass (google.com: domain of lists@achow101.com designates 185.70.43.17 as permitted sender) client-ip=185.70.43.17;
Date: Sat, 20 Apr 2024 19:14:34 +0000
To: bitcoindev@googlegroups.com
From: "'Ava Chow' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
Message-ID: <070755a0-10e9-4903-9524-dd8ef98c1c8b@achow101.com>
In-Reply-To: <fb52ccb5-9942-4db8-b880-3c06ebc47cd1@achow101.com>
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.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> <77554baa9330c57361c65c1fc85557f1@dtrt.org> <7b4e2223-0b96-4ca0-a441-aebcfc7b0bben@googlegroups.com> <CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e=CGHGuSCgm+-4WxT9w@mail.gmail.com> <fb52ccb5-9942-4db8-b880-3c06ebc47cd1@achow101.com>
Feedback-ID: 53660394:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Reply-To: Ava Chow <lists@achow101.com>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

Since we're now past the deadline of April 19th, I'd like to inform=20
everyone of what will happen on Monday.

There has not been any actual objections to the nominees nor have there=20
been any suggestions on choosing a subset of them since my last email.=20
As such, there is rough consensus on adding Kanzure, Murch, Jonatack,=20
Ruben, and Roasbeef as BIP editors, and they will be added on Monday=20
April 22nd.

Ava

On 04/16/2024 01:08 PM, 'Ava Chow' via Bitcoin Development Mailing List=20
wrote:
> While I don't disagree that 5 or 6 people seems like a lot to add at
> once, it's not clear to me how we should decide which subset of the
> nominees should be added. As it is now, I have only seen an actual
> objection to Kanzure and Ruben from /dev/fd0, and no explicit objections
> to anyone else. It seems like the vast majority of people don't share
> their concerns either as both Kanzure and Ruben continue to be endorsed
> by many others.
>=20
> Looking at the endorsements each candidate has received, the current
> counts are:
> * Kanzure - 17 for, 1 against
> * Murch - 13 for
> * Jonatack - 13 for
> * Ruben - 12 for, 1 against
> * Roasbeef - 9 for
> * Michael Folkson - none
>=20
> However, I don't want this process to become a popularity contest and
> require some kind of formal voting. Rather I'd prefer that this process
> be something more like how Bitcoin Core maintainers are added - by
> achieving rough consensus. Without any explicit objections to any of
> these candidates, I'm inclined to move forward with adding the 5 who
> have received endorsements. Having to pick "winners" from this list
> seems like a quick way to stir up drama that I don't think anyone really
> wants to deal with.
>=20
> I do want to note that neither Kanzure, Ruben, nor Roasbeef have posted
> on this list that they are willing to be BIP editors. I have reached out
> to all 3 of them privately, and received responses from Kanzure and
> Ruben that indicate that they probably are willing, but public
> confirmation from them on this list would also be nice. I have not
> received a response from Roasbeef.
>=20
> Ava
>=20
> On 04/11/2024 10:22 AM, Sergi Delgado Segura wrote:
>>   > I would prefer having more (9+?) than less folks on this task, so
>> personal preferences are easily ignored and overwritten by the group
>> majority.
>>
>> I disagree with that, the more doesn't really the better here. Having
>> too many editors may result in a tragedy of the commons, in which people
>> just commit to the job because many others do, and they do not end up
>> doing as much because they expect others to do the it. This does not
>> only make the process look bad but may burnout the ones that end up
>> doing the job, given their time commitment ends up being too far from
>> their expectations.
>>
>> I think being more moderate with the amount of people is better, and
>> gives us leeway in case the workload ends up being excessive and we need
>> to add more people (plus discourage people from joining and slacking off=
).
>>
>> I think 3 more people should be a good number to start from.
>> I'd personally vouch for Murch, Kanzure, and Ruben based on their track
>> record in the space
>>
>> On Tue, Apr 2, 2024 at 4:30=E2=80=AFPM nvk <rdlfnvk@gmail.com
>> <mailto:rdlfnvk@gmail.com>> wrote:
>>
>> +1 for
>> Kanzure
>> RubenSomsen
>> Seccour
>> Jon Atack
>> Roasbeef
>>
>> I would prefer having more (9+?) than less folks on this task, so
>> personal preferences are easily ignored and overwritten by the group
>> majority.
>>
>> BIPs were intended as a means to collect ideas, not enforce ideas.
>>
>> I'd like to return to that.
>>
>> - NVK (temp gmail account)
>>
>>      On Monday, April 1, 2024 at 5:16:54=E2=80=AFPM UTC-4 David A. Hardi=
ng wrote:
>>
>>          On 2024-03-28 10:04, Matt Corallo wrote:
>>           > Please provide justification rather than simply saying "I
>>          like Bob!".
>>
>>          Using only comments from the mailing list, the following appear=
s
>>          to be
>>          the candidate list along with the current support. Asterisks de=
note
>>          candidates who indicated their willingness to accept the role.
>>
>>          - Bryan "Kanzure" Bishop, recommended by Ava Chow[1], Chris
>>          Stewart[3],
>>          Michael Folkson[6], Peter Todd[9], Matt Corallo[10], Brandon
>>          Black[11],
>>          Antoine Riard[12], Murch[13], Antoine Poinsot[15], John
>>          Carvalho[16]
>>
>>          - Ruben Somsen, recommended by Ava Chow[1], Chris Stewart[3],
>>          Michael
>>          Folkson[6], Antoine Riard[12], Murch[13], Antoine Poinsot[15], =
John
>>          Carvalho[16]
>>
>>          - Jon Atack*, recommended by Luke Dashjr[2], Chris Stewart[3],
>>          /dev/fd0[5][7],
>>          Brandon Black[11], Antoine Riard[12], Ava Chow[14], John
>>          Carvalho[16]
>>
>>          - Olaoluwa "Roasbeef" Osuntokun, recommended by Chris
>>          Stewart[3], John
>>          C. Vernaleo[4], /dev/fd0[5][7], Keagan McClelland[8], Antoine
>>          Riard[12], Ava Chow[14]
>>
>>          - Mark "Murch" Erhardt*, recommended by Michael Folkson[6], Kea=
gan
>>          McClelland[8], Matt Corallo[10], Brandon Black[11], Antoine
>>          Riard[12],
>>          Ava Chow[14]
>>
>>          - Michael Folkson*
>>
>>          Note: Luke Dashjr proposed[17] Seccour and Greg Tonoski for
>>          "non-dev
>>          triaging", Tonoski proposed himself[18] for "BIP editor", and
>>          Antoine
>>          Riard[12] proposed Seccour for "decentralized PM".
>>
>>          I searched the BIPs repo by commenter to see if any of the abov=
e
>>          candidates had been especially active there, which is listed
>>          below as:
>>          total PRs they commented on (number still open/number closed).
>>
>>          - 21 (1/20) commenter:kanzure
>>          - 3 (2/1) commenter:rubensomsen
>>          - 15 (0/15) commenter:jonatack
>>          - 18 (2/16) commenter:roasbeef
>>          - 10 (6/4) commenter:Murchandamus
>>          - 57 (6/51) commenter:michaelfolkson
>>
>>          I'll also note that Osuntokun is the only member of the set to
>>          have a
>>          merged BIP that they co-authored, although I believe there are
>>          far-along
>>          draft BIPs for both Murch (terminology) and Somsen (Silent
>>          Payments). I
>>          don't think this should be a requirement, but I do think it
>>          demonstrates
>>          familiarity with the process.
>>
>>          Speaking only for myself, I think all of the candidates above w=
ith
>>          multiple recommendations from other community participants are
>>          fully
>>          qualified for the role, so I'll only provide a detailed
>>          justification
>>          for the person who would be my first pick: Murch is not only a
>>          longstanding and broadly liked Bitcoin contributor, but (as Cor=
allo
>>          mentioned) he has worked on standardizing terminology through a
>>          draft
>>          BIP. In addition, he provided an extremely detailed review of
>>          all 300
>>          pages of a draft of Mastering Bitcoin (3rd edition) and has
>>          reviewed
>>          drafts of over 200 weekly Optech newsletters, in both cases
>>          significantly improving the accuracy and comprehensibility of t=
he
>>          documentation. To me, that seems very similar to the work we'd
>>          ask him
>>          to perform as a BIPs editor and it's something that he's alread=
y
>>          doing,
>>          so I think there's an excellent fit of person to role.
>>
>>          -Dave
>>
>>          [1]
>>          https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8...@achow101=
.com/ <https://gnusha.org/pi/bitcoindev/2092f7ff-4860-47f8-ba1a-c9d97927551=
e@achow101.com/>
>>          [2]
>>          https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106...@dashjr.o=
rg/ <https://gnusha.org/pi/bitcoindev/9288df7b-f2e9-4106-b843-c1ff8f8a62a3@=
dashjr.org/>
>>          [3]
>>          https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a...@googlegr=
oups.com/ <https://gnusha.org/pi/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f=
129a2n@googlegroups.com/>
>>          [4]
>>          https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333...@netpurga=
tory.com/ <https://gnusha.org/pi/bitcoindev/84309c3f-e848-d333-fd28-bdd5589=
9b713@netpurgatory.com/>
>>          [5]
>>          https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36...@googlegr=
oups.com/ <https://gnusha.org/pi/bitcoindev/4c1462b7-ea1c-4a36-be81-7c37191=
57fabn@googlegroups.com/>
>>          [6]
>>          https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2...@googlegr=
oups.com/ <https://gnusha.org/pi/bitcoindev/a116fba3-5948-48d2-a787-639a356=
4d006n@googlegroups.com/>
>>          [7]
>>          https://gnusha.org/pi/bitcoindev/846b668f-8386-4869...@googlegr=
oups.com/ <https://gnusha.org/pi/bitcoindev/846b668f-8386-4869-a3b1-55d346e=
fbea1n@googlegroups.com/>
>>          [8]
>>          https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=3Dw=
ruqgLEazRA5...@mail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CALeFGL1-L=
KPWd7YRS110ut8tX=3DwruqgLEazRA5nVw9siYCPj4A@mail.gmail.com/>
>>          [9] https://gnusha.org/pi/bitcoindev/ZgePPvbf...@petertodd.org/
>>          <https://gnusha.org/pi/bitcoindev/ZgePPvbfrr4wZG7k@petertodd.or=
g/>
>>          [10]
>>          https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5...@mattcora=
llo.com/ <https://gnusha.org/pi/bitcoindev/f9435999-42df-46b5-86e2-7ba0336a=
9bf2@mattcorallo.com/>
>>          [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/
>>          <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/>
>>          [12]
>>          https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+E...@m=
ail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CALZpt+E8DohYEJ9aO+FiF6+EK=
MCP5oEbHSKSXpq0VKVBhJLhrw@mail.gmail.com/>
>>          [13]
>>          https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a...@murch.on=
e/ <https://gnusha.org/pi/bitcoindev/53a0015c-b76a-441a-920b-32bd88d5e778@m=
urch.one/>
>>          [14]
>>          https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f...@achow101=
.com/ <https://gnusha.org/pi/bitcoindev/ae482890-bce3-468f-866d-c555b80b064=
4@achow101.com/>
>>          [15]
>>          https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof=
_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xo=
jo=3D@protonmail.com/ <https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIB=
VBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4=
gwU1c2jS4xojo=3D@protonmail.com/>
>>          [16]
>>          https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552...@googlegr=
oups.com/ <https://gnusha.org/pi/bitcoindev/ad284018-e99c-4552-88ca-11b9ed3=
40661n@googlegroups.com/>
>>          [17]
>>          https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU=3D=
=3DYJMvd9Qrst+...@mail.gmail.com/ <https://gnusha.org/pi/bitcoindev/CAMHHRO=
w9mZJRnTbUo76PdqwJU=3D=3DYJMvd9Qrst+nmyypaedYZgg@mail.gmail.com/>
>>
>>      --
>>      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 email to bitcoindev+unsubscribe@googlegroups.com
>>      <mailto:bitcoindev+unsubscribe@googlegroups.com>.
>>      To view this discussion on the web visit
>>      https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a44=
1-aebcfc7b0bben%40googlegroups.com <https://groups.google.com/d/msgid/bitco=
indev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com?utm_medium=
=3Demail&utm_source=3Dfooter>.
>>
>>
>>
>> --
>> Sergi.
>>
>> --
>> 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 email to bitcoindev+unsubscribe@googlegroups.com
>> <mailto:bitcoindev+unsubscribe@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXB=
cRyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com <https://groups.google.com/d/=
msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGHGuSCgm%2B-4WxT9w%40=
mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter>.
>=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=
 email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgi=
d/bitcoindev/fb52ccb5-9942-4db8-b880-3c06ebc47cd1%40achow101.com.

--=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/070755a0-10e9-4903-9524-dd8ef98c1c8b%40achow101.com.