From: Murch <murch@murch.one>
To: Greg Tonoski <greg.tonoski@gmail.com>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] RFC: Two years of BIP Editing, time for some new faces?
Date: Wed, 29 Apr 2026 13:23:54 -0700 [thread overview]
Message-ID: <76b26e07-d5f4-470e-abb6-66214ad56dc3@murch.one> (raw)
In-Reply-To: <CAMHHROzNUeon9Qj9TEJEU+qe2xHQPQWTwMNeSEnwZqVr7fyMxg@mail.gmail.com>
Hi Greg,
thanks again for your interest. As I wrote to Zed in another branch of
this thread, almost all of the work BIP Editors do on a regular basis
can be contributed to by anyone: please feel free to give some of the
open pull requests a solid review and leave some constructive comments.
I expect that this conversation will probably move similarly slowly as
two years ago. I would surmise that candidates who made pertinent
contributions to the repository would be more likely to garner support
for a BIP Editor role.
Cheers,
Murch
On 2026-04-23 05:35, Greg Tonoski wrote:
> I will help you and join the BIP Editors team so that there are more
> contributors. What information do you need from me to complete
> authorization?
>
> BTW I already offered my contributions two years ago in the mailing list.
>
> Looking forward to a reply.
>
> On Thu, 23 Apr 2026 at 02:04, Murch <murch@murch.one> wrote:
>
> Howdy everyone,
>
> I noticed a couple weeks ago that the two-year anniversary of the
> “new”
> BIP Editors is coming up, and I want to comment on the state of
> the BIPs
> repository and BIP Editorship. In the past two years
> (2024-04-22–2026-04-22), the six BIP Editors left 4108 comments,
> processed 596 pull requests (382 merged), and facilitated the
> publication of 42 BIPs. We got a new BIP Process, touched up existing
> documents, tidied up abandoned submissions, and fixed up the CI
> scripts.
> There is still room for improvement, but I perceive a positive
> impact on
> development discussions and an increase in submissions as the BIPs
> repository became more lively again. I’m proud of what we have
> achieved
> so far.
>
> For most of this time, two BIP Editors contributed most of the work.
> Then for the first quarter this year, I was the only BIP Editor that
> regularly contributed to and did the vast majority of the day-to-day
> work in the repository. I enjoy the work—but we added more BIP
> Editors
> two years ago because it’s more than a one-person job.
>
> I’m grateful for my colleagues’ contributions as well as the splendid
> advice they’ve provided in our many discussions, and thankful that
> they
> volunteered to serve the community!
>
> After two years, I propose that we refresh the BIP Editor team. My
> recommendation would be to aim for three BIP Editors that are all
> keen
> on regularly contributing to the BIP Editor work in the repository.
>
> Looking forward to hearing your thoughts,
> Murch
>
> --
> 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%2Bunsubscribe@googlegroups.com>.
> To view this discussion visit
> https://groups.google.com/d/msgid/bitcoindev/3cfa2ee0-07ae-43db-8664-a817af477c95%40murch.one.
>
--
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 visit https://groups.google.com/d/msgid/bitcoindev/76b26e07-d5f4-470e-abb6-66214ad56dc3%40murch.one.
next prev parent reply other threads:[~2026-04-29 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 23:48 [bitcoindev] RFC: Two years of BIP Editing, time for some new faces? Murch
2026-04-23 12:35 ` Greg Tonoski
2026-04-27 19:51 ` 'Jaroslav Dlouhy' via Bitcoin Development Mailing List
2026-04-29 20:06 ` Murch
2026-04-29 20:23 ` Murch [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-23 11:22 'stickies-v' via Bitcoin Development Mailing List
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76b26e07-d5f4-470e-abb6-66214ad56dc3@murch.one \
--to=murch@murch.one \
--cc=bitcoindev@googlegroups.com \
--cc=greg.tonoski@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox