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
|
Delivery-date: Thu, 14 Mar 2024 05:04:27 -0700
Received: from mail-ot1-f62.google.com ([209.85.210.62])
by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
(Exim 4.94.2)
(envelope-from <bitcoindev+bncBDML5DFJWQEBBQ6PZOXQMGQEVKG47WQ@googlegroups.com>)
id 1rkjow-0002eH-Jx
for bitcoindev@gnusha.org; Thu, 14 Mar 2024 05:04:27 -0700
Received: by mail-ot1-f62.google.com with SMTP id 46e09a7af769-6e514911e25sf677377a34.0
for <bitcoindev@gnusha.org>; Thu, 14 Mar 2024 05:04:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlegroups.com; s=20230601; t=1710417860; x=1711022660; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:sender:from
:to:cc:subject:date:message-id:reply-to;
bh=gUuW59j+Iq6SBlyUP3wxjXbRA7QXNoeAuZKo/3KLJ+M=;
b=STubZcBMCzZW5F1iD5wJneFCKi+UYSle06HkidBYukWZuTft/sefITPHPbdVJzZ6HW
rka8xsiKvt0NTL4cT6jfdArUbWXhlq5BuDWMQqo1oOI8jLqFN8xkC/dMISBfpQcvW5sh
aZx8jxL8ZsSTOOqKS7U0Wq8vqUsWe13sF2DO7O26hXYr/5HKaGKtYRG++77px7zy4+zp
E3zPfD6FbOiEsAlkfIjJb0aLgq4M41r4fADKI7KED8/t5iYKH5k94sOHdIUukDrVmG/o
FpAPin9hbmQ2iJAcXCLehT2sJW2E3PRKsPSPd7bnEZZ4fm+YHV83jYN86XDnrsm3X7dk
4okw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1710417860; x=1711022660; darn=gnusha.org;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:from:to:cc
:subject:date:message-id:reply-to;
bh=gUuW59j+Iq6SBlyUP3wxjXbRA7QXNoeAuZKo/3KLJ+M=;
b=kayB+7HWdEBWdEg5UhQUl2EGYEefmCKsWNwrhcIB+2To+mf6pKUhCsMcTsff6H8vz1
bA42Wgm1szkINRJgzb/Z6eocGmVqyq04HO4tcrCNumc09ElU7cCk4n3rAWSHj0y8UEhQ
MZiCgTIpVxaGc5jtbewwGAVTxruG2vW34V7/Sbe9b9eqtPphAnlK+9ZJJ5NIiKAwjamE
6f52dSKScGxyy2iTjmJybrNwPNNYe8tAQcTMkQzldzLFbfZtyUu+D52EHNuW0YAabq1P
e6fAIt3IKYQwuqqJ0TKXk0B46iQICEpBl6jikDu0qGMwxJ6O1OckiiEfwOUCB+Xv4iVz
MXow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1710417860; x=1711022660;
h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
:list-id:mailing-list:precedence:x-original-sender:mime-version
:subject:references:in-reply-to:message-id:to:from:date:x-beenthere
:x-gm-message-state:sender:from:to:cc:subject:date:message-id
:reply-to;
bh=gUuW59j+Iq6SBlyUP3wxjXbRA7QXNoeAuZKo/3KLJ+M=;
b=K4fiXlr/7d1jgBi8iUirAgRtr6xilsosUIcf2R45fD3UVQtlr9ANgnmohMHmlZtC8E
kjehQI6mUI1QI1/pxUT5V9xv5nZM5dl+p3zhYFLHnwVqBAZ07QM6sryR0qJhyNWEGVu4
wIYP0DeY9SFNNInlqVj1O5SnnNnW+W770dNsxLxDYUScF+RjWBa57g/Xpx32W8CObm7Y
LvyQWdyFZtYcIgr7o8WHWWKThyRcrUJUG+mPYtqARkCC3HZ4ZZa2/E/c+Penl8TuKuo5
WYTI7kMR7IhrPNK51HmEzo5FQIBjQwy8IVKsPxTAImP1u0fx38cDV+4GRRIMTj7NvF4g
1Nww==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCUN5fAFmZ4iDlbA0Y+3tNMwX0vSkY2OCoMr3NKnBbvweq5a8q8tTjL7BVWWpgInfVqqwsam2x3wQed3TvVwjl9qqUc4+1M=
X-Gm-Message-State: AOJu0YyBLNS4uzIFm0R/eaLVtV1B2klGmI4vbLYUcR6q0by/ASrVxoDr
bPHR4+Y2U3Ljra3nExgL59QNjkhoJvP6p3y28UL2Cu9LflYXv945
X-Google-Smtp-Source: AGHT+IE937G35HP3a034jQno3zqbfXHy5KzRvD/BAH1+OCN7K6QBTF8qrENlkVT9WVn6MpS+Zz2y4g==
X-Received: by 2002:a05:6358:2621:b0:17e:68b8:e29c with SMTP id l33-20020a056358262100b0017e68b8e29cmr2174440rwc.11.1710417860230;
Thu, 14 Mar 2024 05:04:20 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a25:b101:0:b0:dcd:a08f:c83e with SMTP id g1-20020a25b101000000b00dcda08fc83els1100358ybj.2.-pod-prod-07-us;
Thu, 14 Mar 2024 05:04:19 -0700 (PDT)
X-Received: by 2002:a05:6902:e04:b0:dc7:68b5:4f3d with SMTP id df4-20020a0569020e0400b00dc768b54f3dmr446642ybb.11.1710417859225;
Thu, 14 Mar 2024 05:04:19 -0700 (PDT)
Received: by 2002:a05:690c:387:b0:60a:5801:5e7b with SMTP id 00721157ae682-60a6aba0a29ms7b3;
Thu, 14 Mar 2024 04:56:23 -0700 (PDT)
X-Received: by 2002:a81:6dc1:0:b0:60c:d049:4332 with SMTP id i184-20020a816dc1000000b0060cd0494332mr164632ywc.2.1710417382630;
Thu, 14 Mar 2024 04:56:22 -0700 (PDT)
Date: Thu, 14 Mar 2024 04:56:22 -0700 (PDT)
From: Chris Stewart <stewart.chris1234@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n@googlegroups.com>
In-Reply-To: <42e6c1d1d39d811e2fe7c4c5ce6e09c705bd3dbb.camel@timruffing.de>
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>
Subject: Re: [bitcoindev] Re: Adding New BIP Editors
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_112550_1534944610.1710417382264"
X-Original-Sender: stewart.chris1234@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 (/)
------=_Part_112550_1534944610.1710417382264
Content-Type: multipart/alternative;
boundary="----=_Part_112551_566608664.1710417382264"
------=_Part_112551_566608664.1710417382264
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I agree with Tim's thoughts here.
I think Jon Atack, Reuben Somsen, Kanzure or Roasbeef would all make great=
=20
candidates.
On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim Ruffing wro=
te:
> On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:
> > The hard part is evaluating=20
> > if the new proposal meets the criteria - which definitely needs dev=20
> > 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.=20
>
> Best,
> Tim
>
>
> [1] BIP2 says:=20
> "For each new BIP that comes in an editor does the following:=20
>
> - 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/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n%40googlegroups.com.
------=_Part_112551_566608664.1710417382264
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div>I agree with Tim's thoughts here.</div><div><br /></div><div>I think J=
on Atack, Reuben Somsen, Kanzure or Roasbeef would all make great candidate=
s.<br /></div><br /><div class=3D"gmail_quote"><div dir=3D"auto" class=3D"g=
mail_attr">On Thursday, February 29, 2024 at 10:55:52=E2=80=AFAM UTC-6 Tim =
Ruffing wrote:<br/></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;=
">On Tue, 2024-02-27 at 17:40 -0500, Luke Dashjr wrote:
<br>> The hard part is evaluating=20
<br>> if the new proposal meets the criteria - which definitely needs de=
v=20
<br>> skills (mainly for technical soundness).
<br>
<br>I'm aware that checking technical soundness is in accordance with B=
IP2
<br>[1], but I believe that this is one of the main problems of the current
<br>process, and I can imagine that this is what eats the time of editors.
<br>
<br>I'd prefer a BIP process in which the editors merely check that the
<br>proposal is related to the Bitcoin ecosystem and meets some minimal
<br>formal criteria that we already enforce now (i.e., is a full self-
<br>contained document, has the required sections, etc...). This relieves
<br>the editors not just from the effort, but also from the responsibility
<br>to do so. Technical soundness should be evaluated by the audience of a
<br>BIP, not by the editor.=20
<br>
<br>Best,
<br>Tim
<br>
<br>
<br>[1] BIP2 says:=C2=A0
<br>"For each new BIP that comes in an editor does the following:=20
<br>
<br>- Read the BIP to check if it is ready: sound and complete. The ideas
<br>must make technical sense, even if they don't seem likely to be
<br>accepted.
<br>[...]"
<br></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List" 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/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/d1e7183c-30e6-4f1a-8fd6-cddc46f129a2n%40googlegroups.com</a>.=
<br />
------=_Part_112551_566608664.1710417382264--
------=_Part_112550_1534944610.1710417382264--
|
