Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
* Re: [bitcoindev] RFC: Two years of BIP Editing, time for some new faces?
@ 2026-04-23 11:22 'stickies-v' via Bitcoin Development Mailing List
  0 siblings, 0 replies; 3+ messages in thread
From: 'stickies-v' via Bitcoin Development Mailing List @ 2026-04-23 11:22 UTC (permalink / raw)
  To: bitcoindev

[-- Attachment #1: Type: text/plain, Size: 2958 bytes --]

I'm not involved enough with the BIPs repository to have a good view on the
exact best number of editors, but I agree that it is better to have a smaller
group where everyone is actively engaged. Three sounds reasonable.

Thank you to all the editors, and special mention to Murch, for your excellent
work on revitalizing the BIPs repository in the last 2 years. For the visible and
the invisible work.
stickies-v

On Thu, Apr 23, 2026 at 1:04 AM 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/SoWAToywcwdV53iRUabwyoAc2Zli8up12ofKsvbGFk_zONpq9U8hlmG9PzIsd0Fv4bZQZaVCEQ-EC7SLxMqHYEMmYkAo3evOjIrotmlst80%3D%40protonmail.com.

[-- Attachment #2: Type: text/html, Size: 4399 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread
* [bitcoindev] RFC: Two years of BIP Editing, time for some new faces?
@ 2026-04-22 23:48 Murch
  2026-04-23 12:35 ` Greg Tonoski
  0 siblings, 1 reply; 3+ messages in thread
From: Murch @ 2026-04-22 23:48 UTC (permalink / raw)
  To: bitcoindev

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.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/3cfa2ee0-07ae-43db-8664-a817af477c95%40murch.one.


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-04-23 14:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-04-23 11:22 [bitcoindev] RFC: Two years of BIP Editing, time for some new faces? 'stickies-v' via Bitcoin Development Mailing List
  -- strict thread matches above, loose matches on Subject: below --
2026-04-22 23:48 Murch
2026-04-23 12:35 ` Greg Tonoski

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox