1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
|
Delivery-date: Tue, 12 Aug 2025 02:02:01 -0700
Received: from mail-oa1-f61.google.com ([209.85.160.61])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDBNTKFG4EDRB7UF5TCAMGQE2Z6IF4Y@googlegroups.com>)
id 1ulktN-0007tc-1z
for bitcoindev@gnusha.org; Tue, 12 Aug 2025 02:02:01 -0700
Received: by mail-oa1-f61.google.com with SMTP id 586e51a60fabf-30bcb15eff5sf4190294fac.1
for <bitcoindev@gnusha.org>; Tue, 12 Aug 2025 02:02:00 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1754989314; cv=pass;
d=google.com; s=arc-20240605;
b=a79LTS4xSOdLWQkaq1y8gGcnsnGbArly3TqR13U1XoWml7J5zZ1Y9/ZK3TlbZnOYC2
Bcs8mGMf6/L34mynzMrbKkvuXtXHwyPulNnkWUOsMhxddNi/LfWOfr6Lu77MNxSAC1pl
gcAUVi8Ufs1c1hhsxCJXCgT2xIYVLomTjOT4cT5om+hwfeWxI5MWeN/W7xfC8WXTy3xx
8c17nOXcCuAHUSa+8Op+pubwCVEClcE7HLmL4m+ekRd/mjx85He38wCFUW15qLYz+tuX
yY7C6O7NVH+AD7G1o6WvaVUbqeGbKljGo0ECJDQ2eQfqLCh3oUVVJdKmajEk6deG+tvz
DSkA==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:in-reply-to:content-disposition
:mime-version:message-id:subject:cc:to:from:date:sender
:dkim-signature;
bh=fMxDzal5XHym/oWTvMjTk2npPKfmbsK1ZVFJyt7UWhU=;
fh=qMnkpkYuxMVxcZ7fCVuZ2WeRjjl14epooWi3Ys6Dg3g=;
b=W6IGMpc9P9o/goKFg2fQIxoUJ5HGoFZByqDY1mPpBX35Vr+X2ivsLvjBuY6pValAc7
iFi/O88Ye30/cu3TW4XscdI+OvH1/PQ+JuWxdVNO3DdHv8oB4VTeOUO2sVPfRqSPKI7X
NcGGzedsvI98jyEs8XjiJ1oQ/lddEEzRSj8KSqKP0eSJQxuWVhIakhjiCf6s7KnqhDB0
UKPHoIH/OhvvaO9J6g8/ZqHwYSZYm/SMCiwcDnNh78iiJXiYHypMFP0xNCQdWsmplEsl
maZLsaHsHg8UuXLgVbrzdKW4BLk9nitWVC3J4T8gdLYGPmrAS+CZrSIJu+tWWTaOBf2b
SBqg==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
spf=pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) smtp.mailfrom=aj@erisian.com.au
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1754989314; x=1755594114; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:in-reply-to:content-disposition:mime-version
:message-id:subject:cc:to:from:date:sender:from:to:cc:subject:date
:message-id:reply-to;
bh=fMxDzal5XHym/oWTvMjTk2npPKfmbsK1ZVFJyt7UWhU=;
b=bhekl1KJP/ka8QfaBQyDGUvKMW1XLGaIf9QIhAKuhcCOYneDQzRaw0X6QeerrPxMrz
JUUR4g7z/1ZvgWABFvk3fhzS2EHeVZXEGnTrivfoqRmF+gvUklfx2IWz2ec2uvOGw6Zn
q582f76CsmFaZ+LeDnben3tdzaHy8eVoe4XngiaYx/weCkK3pPNxc59s5ARhXYxZyia5
lWT2fgVoHzr37b2zOtG1w01zCV/tbmp+WAhONnJudFqjANv8RaSf0iW6cy9rJns8FUtL
pwnu/LZaC6cul4Vsrsom9NxU91BHLh4tlVnHb2SlVXTqP8MdPdohpoTshILpicg5chbC
dPKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1754989314; x=1755594114;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:in-reply-to:content-disposition:mime-version
:message-id:subject:cc:to:from:date:x-beenthere:x-gm-message-state
:sender:from:to:cc:subject:date:message-id:reply-to;
bh=fMxDzal5XHym/oWTvMjTk2npPKfmbsK1ZVFJyt7UWhU=;
b=Z83MhoeyZY6YqfKOquHZMJN33dN7HTEaJe10hOkuYd4Y5iXjAB5dTFg4wUvEktomQx
sylPL8RW/xhTXr7C4+GD1sgNoGX7gKbXc7lChEk3PKB9yq9WPUU8kKnQimh4vV9W/Jdy
htGaULRX9H+7GCbkEQA+qkZduNHyYRsO1WNWxw6eRZsRCz0KWO8dn1JFE+bK90soO4JV
ezzAB602E+pkNUOAQENg5CovMfniaXd4Yv5NbtDHUhlTwml1R28MCTm3El+eEm60L0Wk
HgLOiBEpWkzBrYT7EEO3ErO0C987SkHU7q4n+Mn6oYhTf7vFi4z4af0tax9wGyq7ZMHE
EaZQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCVjsW2o/Mm05eW7zs7KrVotgzf59at6+WN8+9ME0wPs4aU8WYQMU3IshUEfCaxDoMvpPks14KF63H5u@gnusha.org
X-Gm-Message-State: AOJu0YxZD+1lbeNYhWqj5cEylAN5Ho3m2FId3O2UVXMAUxPI3Lw5q0ZZ
2eJE2mInyHLKWhOM3JKpAG0+PzUVAlG+Iw7DDz+uLtztVJTz4j/v8/Nu
X-Google-Smtp-Source: AGHT+IEmbOE2q6gEo6h7kU76gYpzAjFcbyue3RbSHV+e7UKUSwaRgfCDw6JL22bd6MemGQvdh4A3Kw==
X-Received: by 2002:a05:6870:c1d3:b0:30b:a9d5:d475 with SMTP id 586e51a60fabf-30c950befb6mr1725235fac.28.1754989314101;
Tue, 12 Aug 2025 02:01:54 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZcACTbsCQdgLqx5OCstlRM+aNnw586AzMsFiNhZMx5ciQ==
Received: by 2002:a05:6870:b6a4:b0:30b:b2fd:9588 with SMTP id
586e51a60fabf-30bfe78956dls2916582fac.2.-pod-prod-03-us; Tue, 12 Aug 2025
02:01:50 -0700 (PDT)
X-Received: by 2002:a05:6808:181e:b0:40a:59fd:1366 with SMTP id 5614622812f47-435c90e54a5mr1573309b6e.13.1754989310577;
Tue, 12 Aug 2025 02:01:50 -0700 (PDT)
Received: by 2002:a05:6808:654d:b0:40d:498:c1f6 with SMTP id 5614622812f47-4359a0b985amsb6e;
Mon, 11 Aug 2025 22:33:15 -0700 (PDT)
X-Received: by 2002:a05:6602:340d:b0:881:81cb:57de with SMTP id ca18e2360f4ac-8841bf117e5mr472839239f.12.1754976795141;
Mon, 11 Aug 2025 22:33:15 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1754976795; cv=none;
d=google.com; s=arc-20240605;
b=TkCLd5IuUwYGa13qCvVkyH0DPFyQYdnMRB3gMhf/JF7FFCyXFSDjGgm6xnujsZ/IN+
3eka3MTi/qcxBhzuYnlKn6FL8a+nkyJkO664QVRQtNAiKOz1RnQTUXjdULyNYBxBLlXs
c/wYRl/2PBIsTC+LxLBwBHNP2Zkh6laJoRu7Z51TKbMymXQTX+wLmnxqBXTepzDfZdXd
HJuSgjkS7MpkrCF0nDaMNHSCakGgn7j6k9qlWg+uXoQJAubte2zqX/0HpGp0UxrDzqnp
Q085Cj45ypJw69HzE0xeWUlGu0M8A2B9fN4LbJM/k5Uy+FYioOukCSg/RXctySgNAeTW
oI2w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
h=in-reply-to:content-disposition:mime-version:message-id:subject:cc
:to:from:date;
bh=x52m92h+QWfT81UxxipavDMOCLaKd1SG6Hm6m7XKnZg=;
fh=Qrb94UvldC6eQpFIUo/ZLYKlUS2Ev1tCkRyZGXt1hgY=;
b=jo1MGNDCfHQxIJ2ViAh7Dau0cj1/vzL9tnSzPsKjhbIBQt58DqDmhQ7mu0B2T7dApR
eXCLumBwPkaCvE+s1FesOrc81J4mOVUUQwfB/PR4xnCFlmKQxFGI+8FST37YDlY0HEcH
2TQl/G8UVM6I5kLqVSm4imwUb111f9Qc6vUvxOxzTil3+IDpBDwcQVY9X6wG4axIwh3j
t4fDauj615VFuf4ZhlUAPPNd2Vtnt7cmB7XfqAQ4ktev39nCGI2JcXIvTw/lcgrEUjH5
2E3nIfUVxCmitjJo8LU/xz4sTwz0r3OVIyJGVyDje+bHNWWGK0AC482aSQznFTxdI73u
F+Vw==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
spf=pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) smtp.mailfrom=aj@erisian.com.au
Received: from cerulean.erisian.com.au (azure.erisian.com.au. [172.104.61.193])
by gmr-mx.google.com with ESMTPS id ca18e2360f4ac-883f1999f30si37619339f.2.2025.08.11.22.33.14
for <bitcoindev@googlegroups.com>
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Mon, 11 Aug 2025 22:33:14 -0700 (PDT)
Received-SPF: pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) client-ip=172.104.61.193;
Received: from aj@azure.erisian.com.au
by cerulean.erisian.com.au with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.96)
(envelope-from <aj@erisian.com.au>)
id 1ulhdD-0000Vs-1R;
Tue, 12 Aug 2025 15:33:09 +1000
Received: by email (sSMTP sendmail emulation); Tue, 12 Aug 2025 15:33:04 +1000
Date: Tue, 12 Aug 2025 15:33:04 +1000
From: Anthony Towns <aj@erisian.com.au>
To: Ava Chow <lists@achow101.com>, Jon Atack <jonnyatack@gmail.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] New BIP Editors: 1 Year Later
Message-ID: <aJrSEOImKAa9NEB9@erisian.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
In-Reply-To: <8285fb0c-119b-42b8-a530-194650b87ebe@achow101.com>
X-Spam_score: -0.0
X-Spam_bar: /
X-Original-Sender: aj@erisian.com.au
X-Original-Authentication-Results: gmr-mx.google.com; spf=pass
(google.com: domain of aj@erisian.com.au designates 172.104.61.193 as
permitted sender) smtp.mailfrom=aj@erisian.com.au
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
<https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)
On Tue, Jul 15, 2025 at 01:01:55AM +0000, 'Ava Chow' via Bitcoin Development Mailing List wrote:
> In the 15 months since adding the new BIP Editors, the BIP Editors have:
> - Left 1272 comments
> - Merged 261 PRs
> - Closed 122 PRs
> - Assigned 22 BIP numbers
>
> This improvement is very much welcome and the BIPs process no longer
> feels stuck.
I had a look at this via commits to the bips repo a while ago, and came up
with these numers:
- 2021: ~111 merges
- 2022: ~58 merges
- 2023: ~49 merges
- 2024(a): ~2 merges (jan-mar, prior to the new editors)
- 2024(b): ~162 merges (apr-dec, after the new editors were added)
- 2025: ~98 commits (to date)
To me, that seems to back up the impression that things were getting
increasingly stuck, and that that's no longer the case.
> That being said, there is significant variance in the activity of the
> Editors, with only a couple Editors accounting for the vast majority of
> the aforementioned activity.
This is also reflected in the commit history. For the 2025 commits,
I see 38 merges by Murch, and 60 by Jon Atack, leaving 0 by the other
editors. (Going by "git log --merges --first-parent")
For 2024(b), I see 83 by Jon Atack, 56 by Murch, 4 by laolu, 1 by Luke Dashjr,
1 by Bryan Bishop and none by Ruben Somsen. Those latter 6 merges were:
- laolu:
* merged https://github.com/bitcoin/bips/pull/1411 [2024-05-08]
* merged https://github.com/bitcoin/bips/pull/733 [2024-04-23]
* merged https://github.com/bitcoin/bips/pull/1530 [2024-04-22]
* merged https://github.com/bitcoin/bips/pull/1564 [2024-04-22]
- luke:
* merged https://github.com/bitcoin/bips/pull/1598 [2024-05-31]
* also had a direct commit (not a PR) to fix the README after BIP
47 was marked final via PR#1068 [2024-04-24]
- bryan:
* merged https://github.com/bitcoin/bips/pull/596 [2024-04-24]
Adding 5 new editors and having essentially a 60% attrition rate a month
or two later doesn't actually seem that bad to me; but I don't think
it's a good idea to stop there and leave people who aren't particularly
active filling the roles indefinitely.
My guess is that it would be closer to ideal to have the load distributed
across perhaps three or four active editors at any one time rather than
just two, and that over the course of twelve months the three or four
most active editors should change as individuals take time for vacation,
or find themselves having to more intensively focus on work/family/etc
for a period.
It can be pretty hard to voluntarily step down from volunteer positions
(and when that's the primary means for changeover, it tends to lead
to the positions being permanently filled by people who'll simply
never voluntarily step down), so it might be worth considering more
objective/automatic ways to move inactive members.
One straightforward approach is to have term limits, eg "we want six
editors; we'll add two editors each year, and have a three year term
limit. if you were an editor as recently as year X, you're not eligible
to be appointed as an editor again until year X+3". To get the transition
started, you could have Luke (as the longest serving editor, at ~9 years)
and Ruben (as the editor with least merges) have their terms end this
year, Laolu and Bryan in 2026, and Murch and Jon in 2027, eg.
In some circumstances, I think it makes sense to retain past/inactive
contributors in an advisory/oversight/backup role -- so that if something
goes badly wrong, there's not very much friction for those people with
past experience to step up and get things back on track. I'm not sure
how much that applies here, and the github org admins also serve in that
role to some extent, but maybe it's a helpful option to have in mind.
Advisors aren't much of a replacement for active co-contributors, however.
Figuring out how to add two editors a year might seem hard. One way to
make that easier is having some sort of "apprenticeship" role -- one that
demonstrates some of the skills required of an editor, but that doesn't
require extra permissions. Perhaps it could work to let people volunteer
to do early triage/review of bips repo PRs during the first few days after
they're opened, so that authors get a quick response, without editors
having to be constantly on-call, and track their contributions on a wiki
or similar. Alternatively inviting the people who've proposed/reviewed
bips heavily (and helpfully) over the past year or two might work okay.
Cheers,
aj
--
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/aJrSEOImKAa9NEB9%40erisian.com.au.
|
