From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] RFC: Two years of BIP Editing, time for some new faces?
Date: Wed, 18 Nov 2026 13:18:51 -0800 [thread overview]
Message-ID: <62bb6c9b-d3a4-4b5e-97e7-60a2c8c91a2a@murch.one> (raw)
In-Reply-To: <00eb7789-999b-4087-a0fa-5623fcf9fd5b@murch.one>
Hey everyone,
I would like to resurface the discussion whether we should make
additions to the BIP Editor team. I’m afraid that in the past few
months, we haven’t always been able to keep up with the submissions as I
described in April:
On 2026-04-29 13:06, Murch wrote:
> […] For new BIPs, the editors should be able to give each a timely
> solid read, comment on the technical feasibility, and provide some
> actionable constructive feedback. […]
Currently, there are a few high-quality submissions that were opened in
the summer that still haven’t gotten a solid read by a BIP Editor.
We did have more non-editors help with review of new BIPs (thanks for
that, Daniela, Edil, and others!), but we are still continuously falling
behind on the open work even though I find myself spending more time on
the BIPs repository than I can sustain. Especially, when someone needs
to travel or takes time off, work piles up.
I see a couple options:
- Increase the number of active BIP Editors
- Lower standards, e.g., by dropping the expectation of BIP Editors
doing a full read of new submissions, and instead focus just on format
My strong preference would be to refresh the team to be composed of
three active BIP Editors that all contribute regularly to the day-to-day
work. If anyone is interested but worried about making an open-ended
commitment, it seems reasonable that they’d volunteer for a limited term
in advance; e.g., only offer filling the role 12–24 months.
Cheers,
Murch
On 2026-04-29 13:06, Murch wrote:
> I’d say we are looking for people that have
> • some experience contributing to a Bitcoin project or Bitcoin
> protocol design
> • solid command of English
> • and enjoy detail-oriented work.
>
> A BIP Editor should expect to invest at least 5–10 hours per week in
> the repository with an open ended upper bound. Part of the work is
> fairly clerical: keeping abreast of the open pull requests, nudging
> BIP owners for review or PR authors for updates, and merging PRs when
> they are ready for that. For modifications of existing BIPs, most of
> the review should optimally come from the owners of the affected BIP.
> For new BIPs, the editors should be able to give each a timely solid
> read, comment on the technical feasibility, and provide some
> actionable constructive feedback.
>
> Except for labeling PRs and merging them, essentially all of the work
> of BIP Editors could be done by any community member, so please feel
> free to try it out yourself: take a look at one of the open pull
> requests¹, give it a read, and leave some useful comments.
>
> ¹
> https://github.com/bitcoin/bips/pulls?q=is%3Aopen+is%3Apr+-label%3A%22Metadata+Update%22+-label%3ATypo-to-be-collected+-label%3ACI
--
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/62bb6c9b-d3a4-4b5e-97e7-60a2c8c91a2a%40murch.one.
next prev parent reply other threads:[~2026-11-18 21:43 UTC|newest]
Thread overview: 7+ 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-11-18 21:18 ` Murch [this message]
2026-04-29 20:23 ` Murch
-- 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=62bb6c9b-d3a4-4b5e-97e7-60a2c8c91a2a@murch.one \
--to=murch@murch.one \
--cc=bitcoindev@googlegroups.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