summaryrefslogtreecommitdiff
path: root/72/1045569e02d1bcee95da6e1d4e02c0bd8b4b1f
blob: bb2897bf8dfca49039561b5b5604f16d1b4bebf4 (plain)
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
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
Delivery-date: Wed, 27 Mar 2024 16:48:14 -0700
Received: from mail-oo1-f63.google.com ([209.85.161.63])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBDV6R2XBYEMBBN7ASKYAMGQE7HE5E2A@googlegroups.com>)
	id 1rpd0A-0005b0-2e
	for bitcoindev@gnusha.org; Wed, 27 Mar 2024 16:48:14 -0700
Received: by mail-oo1-f63.google.com with SMTP id 006d021491bc7-5a061ace71fsf295134eaf.1
        for <bitcoindev@gnusha.org>; Wed, 27 Mar 2024 16:48:13 -0700 (PDT)
ARC-Seal: i=2; a=rsa-sha256; t=1711583287; cv=pass;
        d=google.com; s=arc-20160816;
        b=kvrpYcwuqWu2L3tFUXa2XZ9xjQmN1TEf4m9YOrM0B4mkADtRiAzbZHe2AvlJtRDS1u
         9XHKjFcmFXu5sTtiv03QeL/DndXgS48pI7UpR5+QmCwE0KczvRiSV/P6eO2ms3jemPp8
         tveQmVaJaebp8PEbZlE8nZ2QFZNgKd4CxifQczgoxoZAkm47IMRNCJXbLXexGDAM6eJD
         YHKXoPTK387zwxLyYXL0kDspVh7T/9T5zQ+E+w7jFBUi2vQ/IaxmNmYpxf/0TNcG8WjU
         4qrTvotncfWHGMXlUVLHUHY5CNjIBPswCpjE8L+1QqKYRFRYTLEkRjIGZ2KS7KgskszO
         t13A==
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:cc:to:subject:message-id:date:from
         :in-reply-to:references:mime-version:sender:dkim-signature
         :dkim-signature;
        bh=wcBndXUxYkghnZtlfHWg/YbPqScVOUHybnP97tZ92fY=;
        fh=Uvq6GHZKrLjjvMEqDC2eFwAhehp4wFfje2Y++PZnBiw=;
        b=F4YYaLnY7ZLdjD8MB3AKpLN6QHT5tG948vxJ2jyaHdcA7dcRvNbFdnojNUbazYzPTd
         maUAKh2ej4kH+Ft50nYHPITiuN4AkkSK3cSGJ+so2SLEn3u5FDalxirFx9XawoaNHOa6
         v6QOs0EY4iFRU33qOXA6YOgTHjxb13n8fu+0S4kYNIZ2Lieieci2OnM4wr+b7KMzx73C
         AGWUko8hQgjJry9x+cb0T2v5hNa6KiPWsEF0iLHeZxPS5YUAcaZh2jVlEO+JAqTozI6c
         Gb4OI8/GVbm86bR1vgtWKJulkYVnY0x8KRrIGvuwH5cXpqDX3fRbO7FP96wenSS9PRYm
         nX7Q==;
        darn=gnusha.org
ARC-Authentication-Results: i=2; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b=cDungKrs;
       spf=pass (google.com: domain of keagan.mcclelland@gmail.com designates 2607:f8b0:4864:20::a32 as permitted sender) smtp.mailfrom=keagan.mcclelland@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1711583287; x=1712188087; 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:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:sender:from:to:cc:subject:date:message-id
         :reply-to;
        bh=wcBndXUxYkghnZtlfHWg/YbPqScVOUHybnP97tZ92fY=;
        b=w7OOEq2YoOtcV4Fzl2DyWBg82+JbwJyIuWGmulO6S8L9ZnrZrb9ZEWTTYqV4Fcv3dB
         ll9EQAw/ppLqwc8tFdF/H6d5dVwr/nrIWw1wk4MjFs3I59qb7TzID00M35R6syCXnLWQ
         xYdD7L6RkZP7MGs8QOY7G3CngnH9Vknr6kNzVJODvWm6S8xr8ukA2OeGR1h7Bgwr/jiL
         I9OjIPn05SRlf29ThHIB67crH/lt9W6xYUEMTe4o4cpnZrKCz9zLkTuhCPVCUQN486q6
         cTkuhhkbUmM51r33gu1rZKbp08It1jNBMUSV/MtYVcSum1AHXaTsZT04qOhDz9K8dLui
         kaTQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1711583287; x=1712188087; 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:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:from:to:cc:subject:date:message-id:reply-to;
        bh=wcBndXUxYkghnZtlfHWg/YbPqScVOUHybnP97tZ92fY=;
        b=RpmtbLb6NbxtV8rxLiCY/a0hXBbt+aI3nWAwQg4S0kFCjKbqeujKucKq1/UG4kuzkj
         +xSjltYIfTvOKkpdIB5984K18PYmEJidPbWDd1Sn41RXlfCuz2d18xcsRiNF64PBcO9a
         iV3JUzDVgs4CIk0bjeGbA2yA5m8ATzPLKIAE6WboY91AyK2LJUFr2cDaVN/1lzOMTzBt
         Ix5NB8KGZEHS0vlDIVbdj4YfnSzONlqvsL840z7TdLDqJeQO8N0rbDBwfYYLmarbTMID
         nM6Wigh6VSIiY1TcNiX1bALj4gMxOdKU+gShRweeIul6E6hT/BjcwO8w8C4fB/qBNdD1
         cWTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1711583287; x=1712188087;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-authentication-results
         :x-original-sender:cc:to:subject:message-id:date:from:in-reply-to
         :references:mime-version:x-beenthere:x-gm-message-state:sender:from
         :to:cc:subject:date:message-id:reply-to;
        bh=wcBndXUxYkghnZtlfHWg/YbPqScVOUHybnP97tZ92fY=;
        b=w229DOrd/k5ADVjUEl0Ww4+NmDnIxHIpbHDPJSFtvIn0RXTwSC/rZQzBppr46APZdK
         emsWmQo18S82Z7KXhjRc7juRjpgb6Iwj8tDclPwGp/97JsqQ3Wg8hSOdAQuoc1zPZ8n2
         e2XBbhSArFZ0Aol5wm7LAzCPAN9GTszJtJNIFeyEMUlIXetfrUOXjZbFsWt9rmtjfso4
         aT8bcneWLjOWl+gDr4CSWvK8gEDK0peHz0Y3XdmrZY2drcPyZgzUqfDMCn3E0zyDcpCS
         whZK9pVpkM/4pObCshQkqHlS5bSZKao0rfJUIwPAvl2viI/coeHxYYf/7eC6MG64x13t
         pQFw==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=2; AJvYcCVoDKzHfDG87ABQlhXMjABLJc7B85ApHLcCe6ijm30H5d2H5CjjPjHqk/h9zjiRFEwtN1eNmiZIi5gQVsRSa9kvsXGpwms=
X-Gm-Message-State: AOJu0YxhXKPbc8kyBOPNZxEl3A+NVn+mnB+sMRAfdaIIJAzCrFtfE5OC
	+rwqbb7IXxqpLoI9QF4MLV9QGiSNmEpTFd04DqTUlobMYOPLH2Dm
X-Google-Smtp-Source: AGHT+IHBVaazHZgzABn53/54CyHXU8/8BJAs+st1TFccHCMJKg3xb473nntiObFFuyD4gJZ3mYDzDg==
X-Received: by 2002:a05:6871:280d:b0:22a:a40c:4bf2 with SMTP id bp13-20020a056871280d00b0022aa40c4bf2mr186189oac.14.1711583287558;
        Wed, 27 Mar 2024 16:48:07 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:6870:200f:b0:22a:a2ad:908 with SMTP id
 o15-20020a056870200f00b0022aa2ad0908ls185483oab.0.-pod-prod-05-us; Wed, 27
 Mar 2024 16:48:06 -0700 (PDT)
X-Received: by 2002:a05:6870:d286:b0:21e:43c5:641f with SMTP id d6-20020a056870d28600b0021e43c5641fmr84875oae.4.1711583286867;
        Wed, 27 Mar 2024 16:48:06 -0700 (PDT)
Received: by 2002:a05:6808:19a3:b0:3c3:cc75:72a7 with SMTP id 5614622812f47-3c3de8ca926msb6e;
        Wed, 27 Mar 2024 16:37:00 -0700 (PDT)
X-Received: by 2002:a9d:6d11:0:b0:6e6:c69c:9ff9 with SMTP id o17-20020a9d6d11000000b006e6c69c9ff9mr1629974otp.3.1711582619992;
        Wed, 27 Mar 2024 16:36:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1711582619; cv=none;
        d=google.com; s=arc-20160816;
        b=K/Ho3tAes4Zgx/M9XJ/fFk9JUi7QF3GjWSG/27M5qOdOiy/ONLkk/SIqz3/XscAAWd
         b/N+7xscwRhxiAqzT3b9JEdflkBcc3ZGWVOcKHkoonx7Ue4I/wOOl0mIXkrj68NPe6Be
         FTYTtMgHpv2+BbLMZt6tpKFzEvdFkC9QTzmm35sXzyHd5UJSya1EZBRLumla9sxUM7yp
         TLdquEVZAwSa47Zt6zJkNCB6lygy9/vonQBT2igMZPkQOOS96SomqL6CgiYjmr6UQJ0D
         Z55LGdevD6+mnISXWVosnoEuRlkoYOmcdM+lJCOLFNc7HgyyJ+fmZ4eOh7iDVa244y5p
         e/Tg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=cc:to:subject:message-id:date:from:in-reply-to:references
         :mime-version:dkim-signature;
        bh=B3B0tgCmkVjujs7/A/J2jCDcz/237NDPM/1sT4y8+0g=;
        fh=foaZ9w3C3c5ltuXRyLrsJcSZd5F+/L4e8AHpKYxjE8o=;
        b=dqpH0kywnNF2MRDpY4/mXZWb6C8xKTIPC1wToj6KKZvThceFH8pKSJ2GvGHWe5g87w
         Se/Ai72PxwpIZ+VG5rObFXHv0jD+7I/J8/6J2vmM0T41jI/BT5aakmcTnQT989FOKDCK
         KUxCT3bc2egVba+XOjOcpWV8o86hl0bLwwqlrZS4PtH64tdiWfchfIiMmxnKt+wTO9uh
         jjh/+b7r58SYo2vOKltT8kE13S2+cp9uCRtUUKB1HDaAzXO6PijznslZydBpI79jqbTI
         hzRNsmXHVB6uBXfW+289KxGyGHohnUG5LoKpKjxinuOimWmAkqC+wzQId0jzST/Fjj4R
         e5rQ==;
        dara=google.com
ARC-Authentication-Results: i=1; gmr-mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20230601 header.b=cDungKrs;
       spf=pass (google.com: domain of keagan.mcclelland@gmail.com designates 2607:f8b0:4864:20::a32 as permitted sender) smtp.mailfrom=keagan.mcclelland@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com. [2607:f8b0:4864:20::a32])
        by gmr-mx.google.com with ESMTPS id t15-20020a05683014cf00b006e6c068a73fsi19519otq.4.2024.03.27.16.36.59
        for <bitcoindev@googlegroups.com>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Wed, 27 Mar 2024 16:36:59 -0700 (PDT)
Received-SPF: pass (google.com: domain of keagan.mcclelland@gmail.com designates 2607:f8b0:4864:20::a32 as permitted sender) client-ip=2607:f8b0:4864:20::a32;
Received: by mail-vk1-xa32.google.com with SMTP id 71dfb90a1353d-4d42d18bd63so131392e0c.2
        for <bitcoindev@googlegroups.com>; Wed, 27 Mar 2024 16:36:59 -0700 (PDT)
X-Received: by 2002:a05:6122:d9f:b0:4d4:19e9:db0 with SMTP id
 bc31-20020a0561220d9f00b004d419e90db0mr1864381vkb.0.1711582619266; Wed, 27
 Mar 2024 16:36:59 -0700 (PDT)
MIME-Version: 1.0
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> <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
In-Reply-To: <52a0d792-d99f-4360-ba34-0b12de183fef@murch.one>
From: Keagan McClelland <keagan.mcclelland@gmail.com>
Date: Wed, 27 Mar 2024 16:36:48 -0700
Message-ID: <CALeFGL2SJdKFaY6MeyXjQ5RJM4Va2Hh=NeRB8wthARbDSBZsvw@mail.gmail.com>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
To: Murch <murch@murch.one>
Cc: bitcoindev@googlegroups.com
Content-Type: multipart/alternative; boundary="000000000000067ab10614ace2b1"
X-Original-Sender: keagan.mcclelland@gmail.com
X-Original-Authentication-Results: gmr-mx.google.com;       dkim=pass
 header.i=@gmail.com header.s=20230601 header.b=cDungKrs;       spf=pass
 (google.com: domain of keagan.mcclelland@gmail.com designates
 2607:f8b0:4864:20::a32 as permitted sender) smtp.mailfrom=keagan.mcclelland@gmail.com;
       dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com
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.5 (/)

--000000000000067ab10614ace2b1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I support this as a go forward plan.

On Wed, Mar 27, 2024 at 2:56=E2=80=AFPM Murch <murch@murch.one> wrote:

> Hey everyone,
>
> I wanted to check in on the topic adding BIP Editors. There seem to be a
> number of candidates that are willing and able, and there seems to be
> broad agreement among the current editor, the readers of the repository,
> and the contributors to the repository that additional help is desirable.
>
> I have seen some support and reservations raised for pretty much every
> candidate. A few weeks have passed since this topic was last active. So
> far, there seems no clear path forward.
>
> If we are all just in a holding pattern, perhaps we could timebox this
> decision process: how about we invite arguments for and against any
> candidates in this thread until next Friday EOD (April 5th). If any
> candidates find broad support, those candidates could be added as new
> editors to the repository on the following Monday (April 8th). If none
> get broad support, at least we=E2=80=99d be able to move on and try somet=
hing else.
>
> I propose that all editors share the same privileges, especially that
> any editor may assign numbers to BIPs. If there is guidance to be
> provided on the process of assigning numbers and number ranges for
> specific topics, it should be provided by then. If the editors decide on
> a single number authority among themselves, that would also be fine as
> long as it doesn=E2=80=99t become a bottleneck.
>
> As Tim and Chris have suggested, it seems reasonable to me that
> assessment of the technical soundness can be left to the audience. BIPs
> have been published in the repository and set to the "rejected" status
> before, so it=E2=80=99s not as if adding a BIP to the repository is treat=
ed as
> an unequivocal endorsement or implementation recommendation.
>
> Cheers,
> Murch
>
>
> On 3/14/24 07:56, Chris Stewart wrote:
> > I agree with Tim's thoughts here.
> >
> > I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make
> great
> > candidates.
> >
> > On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffing=
 wrote:
> >
> >> 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 curren=
t
> >> 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.
> >> [...]"
>
> --
> 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 on the web visit
> https://groups.google.com/d/msgid/bitcoindev/52a0d792-d99f-4360-ba34-0b12=
de183fef%40murch.one
> .
>

--=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/CALeFGL2SJdKFaY6MeyXjQ5RJM4Va2Hh%3DNeRB8wthARbDSBZsvw%40mail.gma=
il.com.

--000000000000067ab10614ace2b1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I support this as a go forward plan.<br></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Mar 27, 20=
24 at 2:56=E2=80=AFPM Murch &lt;murch@murch.one&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">Hey everyone,<br>
<br>
I wanted to check in on the topic adding BIP Editors. There seem to be a <b=
r>
number of candidates that are willing and able, and there seems to be <br>
broad agreement among the current editor, the readers of the repository, <b=
r>
and the contributors to the repository that additional help is desirable.<b=
r>
<br>
I have seen some support and reservations raised for pretty much every <br>
candidate. A few weeks have passed since this topic was last active. So <br=
>
far, there seems no clear path forward.<br>
<br>
If we are all just in a holding pattern, perhaps we could timebox this <br>
decision process: how about we invite arguments for and against any <br>
candidates in this thread until next Friday EOD (April 5th). If any <br>
candidates find broad support, those candidates could be added as new <br>
editors to the repository on the following Monday (April 8th). If none <br>
get broad support, at least we=E2=80=99d be able to move on and try somethi=
ng else.<br>
<br>
I propose that all editors share the same privileges, especially that <br>
any editor may assign numbers to BIPs. If there is guidance to be <br>
provided on the process of assigning numbers and number ranges for <br>
specific topics, it should be provided by then. If the editors decide on <b=
r>
a single number authority among themselves, that would also be fine as <br>
long as it doesn=E2=80=99t become a bottleneck.<br>
<br>
As Tim and Chris have suggested, it seems reasonable to me that <br>
assessment of the technical soundness can be left to the audience. BIPs <br=
>
have been published in the repository and set to the &quot;rejected&quot; s=
tatus <br>
before, so it=E2=80=99s not as if adding a BIP to the repository is treated=
 as <br>
an unequivocal endorsement or implementation recommendation.<br>
<br>
Cheers,<br>
Murch<br>
<br>
<br>
On 3/14/24 07:56, Chris Stewart wrote:<br>
&gt; I agree with Tim&#39;s thoughts here.<br>
&gt; <br>
&gt; I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make g=
reat<br>
&gt; candidates.<br>
&gt; <br>
&gt; On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffin=
g wrote:<br>
&gt; <br>
&gt;&gt; On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:<br>
&gt;&gt;&gt; The hard part is evaluating<br>
&gt;&gt;&gt; if the new proposal meets the criteria - which definitely need=
s dev<br>
&gt;&gt;&gt; skills (mainly for technical soundness).<br>
&gt;&gt;<br>
&gt;&gt; I&#39;m aware that checking technical soundness is in accordance w=
ith BIP2<br>
&gt;&gt; [1], but I believe that this is one of the main problems of the cu=
rrent<br>
&gt;&gt; process, and I can imagine that this is what eats the time of edit=
ors.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;d prefer a BIP process in which the editors merely check tha=
t the<br>
&gt;&gt; proposal is related to the Bitcoin ecosystem and meets some minima=
l<br>
&gt;&gt; formal criteria that we already enforce now (i.e., is a full self-=
<br>
&gt;&gt; contained document, has the required sections, etc...). This relie=
ves<br>
&gt;&gt; the editors not just from the effort, but also from the responsibi=
lity<br>
&gt;&gt; to do so. Technical soundness should be evaluated by the audience =
of a<br>
&gt;&gt; BIP, not by the editor.<br>
&gt;&gt;<br>
&gt;&gt; Best,<br>
&gt;&gt; Tim<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; [1] BIP2 says:<br>
&gt;&gt; &quot;For each new BIP that comes in an editor does the following:=
<br>
&gt;&gt;<br>
&gt;&gt; - Read the BIP to check if it is ready: sound and complete. The id=
eas<br>
&gt;&gt; must make technical sense, even if they don&#39;t seem likely to b=
e<br>
&gt;&gt; accepted.<br>
&gt;&gt; [...]&quot;<br>
<br>
-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev%2Bunsubscribe@googlegroups.com" target=
=3D"_blank">bitcoindev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/52a0d792-d99f-4360-ba34-0b12de183fef%40murch.one" rel=
=3D"noreferrer" target=3D"_blank">https://groups.google.com/d/msgid/bitcoin=
dev/52a0d792-d99f-4360-ba34-0b12de183fef%40murch.one</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/CALeFGL2SJdKFaY6MeyXjQ5RJM4Va2Hh%3DNeRB8wthARbDSBZsvw=
%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.go=
ogle.com/d/msgid/bitcoindev/CALeFGL2SJdKFaY6MeyXjQ5RJM4Va2Hh%3DNeRB8wthARbD=
SBZsvw%40mail.gmail.com</a>.<br />

--000000000000067ab10614ace2b1--