Subject: Re: [bitcoindev] Re: Adding New BIP Editors

From: Matt Corallo <[email-masked]>
Date: Mon, 15 Apr 2024 13:50:55 -0400

Strongly agree with Sergi here,

I'd suggest 2-3 BIP editors who are actually responsible for things is more useful than 5 BIP 
editors where no one is responsible for anything.

Again, I'm not convinced dumping this on more people is useful, folks like Roasbeef are great but 
clearly don't have time to keep up with yet more things, and not sure why folks are on the list here 
who haven't been active on the Bitcoin-dev ML and in BIPs for many years (eg no idea who Seccour is).

Matt

On 4/11/24 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 PM nvk <[email-masked] <mailto:[email-masked]>> 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 PM UTC-4 David A. Harding 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 appears to be
>         the candidate list along with the current support. Asterisks denote
>         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], Keagan
>         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 above
>         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 with
>         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 Corallo
>         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 the
>         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 already doing,
>         so I think there's an excellent fit of person to role.
> 
>         -Dave
> 
>         [1]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [2]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [3]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [4]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [5]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [6]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [7]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [8]
>         https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/CALeFGL1-LKPWd7YRS110ut8tX=[email-masked]/>
>         [9] https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [10]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [11] https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/
>         <https://gnusha.org/pi/bitcoindev/ZgWRu32FXzqqg69V@console/>
>         [12]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [13]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [14]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [15]
>         https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=@protonmail.com/ <https://gnusha.org/pi/bitcoindev/ppBS1tfMU3SFX85kmIBVBd0WpT5Wof_oSBXsuizh7692AUDw2TojfvCqvcvlmsy9E69qfWMxK-UZWawf8IDApPqF7bXOH4gwU1c2jS4xojo=@protonmail.com/>
>         [16]
>         https://gnusha.org/pi/bitcoindev/[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/[email-masked]/>
>         [17]
>         https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU==[email-masked]/
>         <https://gnusha.org/pi/bitcoindev/CAMHHROw9mZJRnTbUo76PdqwJU==[email-masked]/>
> 
>     -- 
>     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
>     [email-masked] <mailto:[email-masked]>.
>     To view this discussion on the web visit
>     https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com <https://groups.google.com/d/msgid/bitcoindev/7b4e2223-0b96-4ca0-a441-aebcfc7b0bben%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> 
> 
> -- 
> 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 
> [email-masked] <mailto:[email-masked]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com <https://groups.google.com/d/msgid/bitcoindev/CAEYHFxV_8_Jw61tysL_cV_xiXBcRyA3e%3DCGHGuSCgm%2B-4WxT9w%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
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 [email-masked].
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/64ca2432-c2fc-436f-9ea0-4dd961d4d927%40mattcorallo.com.