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
|
Delivery-date: Wed, 27 Mar 2024 14:57:04 -0700
Received: from mail-qt1-f183.google.com ([209.85.160.183])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBAABBKNMSKYAMGQEEMJ2E2Q@googlegroups.com>)
id 1rpbGa-0003SL-70
for bitcoindev@gnusha.org; Wed, 27 Mar 2024 14:57:04 -0700
Received: by mail-qt1-f183.google.com with SMTP id d75a77b69052e-42f521e0680sf2333071cf.1
for <bitcoindev@gnusha.org>; Wed, 27 Mar 2024 14:57:03 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1711576618; cv=pass;
d=google.com; s=arc-20160816;
b=VzJR3Z5RAfAt5VV8AcIkJ7oTm/vl25o5OLWAg2BUw/41P1eksipV8Vr/0P4b5XumWc
2HuO4YctSvLx/wAsXUWJnLZRzz4TLok9RMCkuoITmPczIJjMHjywFBtg4cBWQ/SFg+3f
BV5hbuQKK3lHcl22E47E4H1pYSWN/+Muu++i5MnNAQzIWG9FG3nS9hI6RuGCNRJWgZ7U
E8sV1JNaIkaY6R28kx6iCxv3ZXXRXDOChs7yvmDl4P3R1DzaZBN97Dk9hhMQ3nrIPwd2
PXWYwXDOG7PRZRlqsZal6o3rl6Fu/3aEtl0ZiisQ0UPQ+17mIo4B4HhU26KxA8vEzlVD
BP+g==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:content-transfer-encoding
:in-reply-to:from:references:to:content-language:subject:user-agent
:mime-version:date:message-id:sender:dkim-signature;
bh=zIN90mDJUWIAvjUbJFqb/o2vzv9kwiqagBXxYA6RArE=;
fh=fZG0NuSKlU5UWHYNSXvbOcjbZQfKiqrGJqkPZnFjY14=;
b=MMeUYZBQbfDLNxcCHzvxOMj6Jz/KjOM3nLzTkopAKI+/KAUXXpxhwhK/Y1vElRVtaw
h52CXvXDv3h82/ZBJczsD7Jz3Rzx9gJ2mEGWLSDFoylBPXaewiySUjuz7au/CxQU0tla
IZuEdTxYNRu6j/g5a1c3T4nC70x3NHcuXpDSJxP1vtYqLAwvwORk7EQBjG5EmVeLZMp0
a79GDaZiAh0m5qTtdFDH27yUKFkadcjJdLH11VhNQsbFnk7Ybeosrow8Txcd2cMmzPdP
MATzDEOUskTCm6t7YMtFm1zW5RV+qayKJMtZXq0rnyPqwSBwq/DDatUbD6Sdr/XqMwEn
8DTA==;
darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
dkim=pass header.i=@murch.one header.s=uberspace header.b=c1BOxNBh;
spf=pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) smtp.mailfrom=murch@murch.one
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1711576618; x=1712181418; 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:content-transfer-encoding:in-reply-to:from
:references:to:content-language:subject:user-agent:mime-version:date
:message-id:sender:from:to:cc:subject:date:message-id:reply-to;
bh=zIN90mDJUWIAvjUbJFqb/o2vzv9kwiqagBXxYA6RArE=;
b=EDNP9rKmAy0EdAZ9doKWk1MNvLppcO4LVIkPJYabCw4iWvZsCIvRSlGV5FBEOVcHKO
bgiSujPvWHvt9X7Xh/TFr2GjcnWQEIQHSeB6Mc8Ff61UedquX/81wW4/Gr/c5EFcgoQY
qWDfM8N3XRuCFIVSniJ416mvvoYjL/Q/XHIng0nI6K4DnPX09XqC4e+5dAgu8Xy5dFqV
5uuRoF4LMjZyu+bf7cM0eQP7ymtf3nVhpUzFvPhofWDqXNEXcYcuX+19/pvIdE+GZ3Z+
iy58wXR00gWVDF7oFYxH+Lz5KTilIDC+soR/Tr09U+DeX8C6ormwvHz0uWofQNnKelJx
nH/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1711576618; x=1712181418;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-authentication-results
:x-original-sender:content-transfer-encoding:in-reply-to:from
:references:to:content-language:subject:user-agent:mime-version:date
:message-id:x-beenthere:x-gm-message-state:sender:from:to:cc:subject
:date:message-id:reply-to;
bh=zIN90mDJUWIAvjUbJFqb/o2vzv9kwiqagBXxYA6RArE=;
b=M0FjgdSLxUQ9UewF4zuO34xndiXHc+mARJiGfVvVDgOySj1gtw7WO6E9spx3p7fzPU
OLwIlVGnXIeR5NlaPtJgPeOzvrqb0XOvnptKlvNr/xFNGaxf7Zu1PR0/VRe7R4+5lRrI
Oem6Pa276Zbwdc6sHrnoM7Zuq184aIj41HfzgGPtfjQDzljMFIVEucJLawyATT7tw0UB
Ckw96Mwy0yZR0jXPObsfn+2B/9BD38igvQclP2EyWJuoIB4ZQYuL9ag0zltyaTfPj25+
ilAfkV92kxtlvQeD/jyrYBf+F1SWiKvgVZE08/8rqFjrYW+CP73Jixzx9OuYR/bnsCc6
C8OQ==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCXUrlV6gk0Uxlk5c1U1rjj7w/4mkdripffTBKHgAgrEiyS8BWRbhl7+tGFgs6nXtxleRVTFS4SPPVxzyHrpACNyUo7jUrQ=
X-Gm-Message-State: AOJu0YwDF90BIwbA1J/hrA3RQxigL17LZcwLsBAiz+lQ0EaIyqdridwt
QE5VI9NHRD0oHT8elMFJkaRasEJvhGBtqCNrFXe2PC+FOnMZLiRW
X-Google-Smtp-Source: AGHT+IFrl0HGov0IknLtVM8YWAIBRSACKdC3uzCKhqviLAVIy/Px1ojQtZQLBUkwXs6TjDyN5Q7dPA==
X-Received: by 2002:ac8:5dd4:0:b0:431:7c1e:a76d with SMTP id e20-20020ac85dd4000000b004317c1ea76dmr905302qtx.57.1711576618068;
Wed, 27 Mar 2024 14:56:58 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:622a:1886:b0:431:7333:7aea with SMTP id
v6-20020a05622a188600b0043173337aeals391599qtc.1.-pod-prod-06-us; Wed, 27 Mar
2024 14:56:57 -0700 (PDT)
X-Received: by 2002:a05:622a:9:b0:431:1ee0:26d6 with SMTP id x9-20020a05622a000900b004311ee026d6mr42564qtw.2.1711576616865;
Wed, 27 Mar 2024 14:56:56 -0700 (PDT)
Received: by 2002:a05:620a:4620:b0:78a:4068:6a01 with SMTP id af79cd13be357-78b7b6da341ms85a;
Wed, 27 Mar 2024 14:25:56 -0700 (PDT)
X-Received: by 2002:adf:e291:0:b0:341:7864:a6e3 with SMTP id v17-20020adfe291000000b003417864a6e3mr895843wri.2.1711574754721;
Wed, 27 Mar 2024 14:25:54 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1711574754; cv=none;
d=google.com; s=arc-20160816;
b=Yw3vpaOjgnpnKog1qYFPjJL9Yf4gCKtEqbXNVv/fhY3NG8jUr2M8ebQLCQjy0g20f1
YpA4J950REq274i1bDmGZV/gHFVTEuh+0+WrDS4POShK2urDMdlywPUDnKeSAfQCILIx
LN4JmAj0L/5Y4PLep5Da3t9YnPXPgmb6YweMvxH0uBB4XvCHZX1HAW82eWHxf/boBp7N
AKOdx/JKnHKuAiQ3nOjQHH+tO/4ov9cC4mm2qzJu9w21yd0bE8uh5Hr81C9ZEvBv7niI
fPQDLx2vNaxPqxughfFfhIJ9/ymKfeYzAdNO3c8HeikS4WE+IjNZ/xnY1hx4XECmBWpJ
xzfQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=dkim-signature:content-transfer-encoding:in-reply-to:from
:references:to:content-language:subject:user-agent:mime-version:date
:message-id;
bh=egXxwj/bcdvz7XBGHM+et9mCmaAlHKW/e/9bRwEsKSc=;
fh=VcGcg+Zjs9gw1uDcHbxsAILhBAcecnbJzZRdxgKVDIc=;
b=ff6XLUU92hZRxjoHBvUg0P08IghL3geXi2SPxzrU916Nt9gCApFyOlMiktoln15rO1
zSqFM6ITxgrmXLOL32/s0sS69aJ10PustlaifQLmOgaXJDiEnYHFyvic5c/KOqK/O/6G
1RLtuId1ZddyJpSEAfjISF6b9fRYqSL6MEACn6IkNUn6MT0+oTPGCA1n4EgX0g7N+Alb
r+ipj92KtX8qtrO8Kv5rAr4pH7h1FaT8jehhB5C4/7bH04ir04gmHOtG+JlxvQxelmOZ
4d347M9DgSGDZUqml6020onG5tM6YEPR2WaicpvpaPA9AllWFG6xe4Lyc0kGPCt1UjCs
vgNw==;
dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
dkim=pass header.i=@murch.one header.s=uberspace header.b=c1BOxNBh;
spf=pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) smtp.mailfrom=murch@murch.one
Received: from farbauti.uberspace.de (farbauti.uberspace.de. [185.26.156.235])
by gmr-mx.google.com with ESMTPS id k8-20020a5d6d48000000b0033cddf15870si505wri.6.2024.03.27.14.25.54
for <bitcoindev@googlegroups.com>
(version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
Wed, 27 Mar 2024 14:25:54 -0700 (PDT)
Received-SPF: pass (google.com: domain of murch@murch.one designates 185.26.156.235 as permitted sender) client-ip=185.26.156.235;
Received: (qmail 7373 invoked by uid 989); 27 Mar 2024 21:25:54 -0000
Received: from unknown (HELO unkown) (::1)
by farbauti.uberspace.de (Haraka/3.0.1) with ESMTPSA; Wed, 27 Mar 2024 22:25:54 +0100
Message-ID: <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
Date: Wed, 27 Mar 2024 17:25:44 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
Content-Language: en-US
To: bitcoindev@googlegroups.com
References: <2092f7ff-4860-47f8-ba1a-c9d97927551e@achow101.com>
<e4048607-64b7-4772-b74e-4566a4b50bc0n@googlegroups.com>
<9288df7b-f2e9-4106-b843-c1ff8f8a62a3@dashjr.org>
<42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
<d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com>
From: Murch <murch@murch.one>
In-Reply-To: <d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Rspamd-Bar: --
X-Rspamd-Report: BAYES_HAM(-2.804108) XM_UA_NO_VERSION(0.01) MIME_GOOD(-0.1) MIME_BASE64_TEXT(0.1)
X-Rspamd-Score: -2.794108
X-Original-Sender: murch@murch.one
X-Original-Authentication-Results: gmr-mx.google.com; dkim=pass
header.i=@murch.one header.s=uberspace header.b=c1BOxNBh; spf=pass
(google.com: domain of murch@murch.one designates 185.26.156.235 as permitted
sender) smtp.mailfrom=murch@murch.one
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 (/)
Hey everyone,
I wanted to check in on the topic adding BIP Editors. There seem to be a=20
number of candidates that are willing and able, and there seems to be=20
broad agreement among the current editor, the readers of the repository,=20
and the contributors to the repository that additional help is desirable.
I have seen some support and reservations raised for pretty much every=20
candidate. A few weeks have passed since this topic was last active. So=20
far, there seems no clear path forward.
If we are all just in a holding pattern, perhaps we could timebox this=20
decision process: how about we invite arguments for and against any=20
candidates in this thread until next Friday EOD (April 5th). If any=20
candidates find broad support, those candidates could be added as new=20
editors to the repository on the following Monday (April 8th). If none=20
get broad support, at least we=E2=80=99d be able to move on and try somethi=
ng else.
I propose that all editors share the same privileges, especially that=20
any editor may assign numbers to BIPs. If there is guidance to be=20
provided on the process of assigning numbers and number ranges for=20
specific topics, it should be provided by then. If the editors decide on=20
a single number authority among themselves, that would also be fine as=20
long as it doesn=E2=80=99t become a bottleneck.
As Tim and Chris have suggested, it seems reasonable to me that=20
assessment of the technical soundness can be left to the audience. BIPs=20
have been published in the repository and set to the "rejected" status=20
before, so it=E2=80=99s not as if adding a BIP to the repository is treated=
as=20
an unequivocal endorsement or implementation recommendation.
Cheers,
Murch
On 3/14/24 07:56, Chris Stewart wrote:
> I agree with Tim's thoughts here.
>=20
> I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make grea=
t
> candidates.
>=20
> On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffing w=
rote:
>=20
>> On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:
>>> The hard part is evaluating
>>> if the new proposal meets the criteria - which definitely needs dev
>>> skills (mainly for technical soundness).
>>
>> I'm aware that checking technical soundness is in accordance with BIP2
>> [1], but I believe that this is one of the main problems of the current
>> process, and I can imagine that this is what eats the time of editors.
>>
>> I'd prefer a BIP process in which the editors merely check that the
>> proposal is related to the Bitcoin ecosystem and meets some minimal
>> formal criteria that we already enforce now (i.e., is a full self-
>> contained document, has the required sections, etc...). This relieves
>> the editors not just from the effort, but also from the responsibility
>> to do so. Technical soundness should be evaluated by the audience of a
>> BIP, not by the editor.
>>
>> Best,
>> Tim
>>
>>
>> [1] BIP2 says:
>> "For each new BIP that comes in an editor does the following:
>>
>> - Read the BIP to check if it is ready: sound and complete. The ideas
>> must make technical sense, even if they don't seem likely to be
>> accepted.
>> [...]"
--=20
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 e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/52a0d792-d99f-4360-ba34-0b12de183fef%40murch.one.
|
