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
|
Return-Path: <jlrubin@mit.edu>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 09414C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Apr 2021 03:36:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id D6AC2400D1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Apr 2021 03:36:31 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id MbGDqo4XwBxI
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Apr 2021 03:36:31 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
by smtp2.osuosl.org (Postfix) with ESMTPS id C79FB400BD
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 23 Apr 2021 03:36:30 +0000 (UTC)
Received: from mail-io1-f46.google.com (mail-io1-f46.google.com
[209.85.166.46]) (authenticated bits=0)
(User authenticated as jlrubin@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13N3aSt9019191
(version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
for <bitcoin-dev@lists.linuxfoundation.org>; Thu, 22 Apr 2021 23:36:29 -0400
Received: by mail-io1-f46.google.com with SMTP id b10so47678519iot.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 22 Apr 2021 20:36:29 -0700 (PDT)
X-Gm-Message-State: AOAM531fffQr593doUHQMPO31mcvCylqSMcGXrvp/VJW4sIZ0Ci7u8+Q
WjiFlHc6t4DXBiSysVmjpgUzzYjjtmMeCQ1THmY=
X-Google-Smtp-Source: ABdhPJw9fKL7rwxPZZghH/aW+08e3FkfaZHnOWTTs4srOlQWQAPq9ZSO44hGgpB5105UTsPBChY9uYwK4fp9/Tf3XNg=
X-Received: by 2002:a6b:7b45:: with SMTP id m5mr1771443iop.97.1619148988571;
Thu, 22 Apr 2021 20:36:28 -0700 (PDT)
MIME-Version: 1.0
References: <202104230209.05373.luke@dashjr.org>
In-Reply-To: <202104230209.05373.luke@dashjr.org>
From: Jeremy <jlrubin@mit.edu>
Date: Thu, 22 Apr 2021 20:36:16 -0700
X-Gmail-Original-Message-ID: <CAD5xwhgy1dkKqbWY=n1_p5MfbNwJweCHZotkD6hj7K4kv+wg3Q@mail.gmail.com>
Message-ID: <CAD5xwhgy1dkKqbWY=n1_p5MfbNwJweCHZotkD6hj7K4kv+wg3Q@mail.gmail.com>
To: Luke Dashjr <luke@dashjr.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000004d643f05c09b80c2"
Subject: Re: [bitcoin-dev] Proposed BIP editor: Kalle Alm
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Apr 2021 03:36:32 -0000
--0000000000004d643f05c09b80c2
Content-Type: text/plain; charset="UTF-8"
ACK adding Kalle.
Kalle is a qualified reviewer / editor and well suited for this role.
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
On Thu, Apr 22, 2021 at 7:09 PM Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Unless there are objections, I intend to add Kalle Alm as a BIP editor to
> assist in merging PRs into the bips git repo.
>
> Since there is no explicit process to adding BIP editors, IMO it should be
> fine to use BIP 2's Process BIP progression:
>
> > A process BIP may change status from Draft to Active when it achieves
> > rough consensus on the mailing list. Such a proposal is said to have
> > rough consensus if it has been open to discussion on the development
> > mailing list for at least one month, and no person maintains any
> > unaddressed substantiated objections to it.
>
> A Process BIP could be opened for each new editor, but IMO that is
> unnecessary. If anyone feels there is a need for a new Process BIP, we can
> go
> that route, but there is prior precedent for BIP editors appointing new
> BIP
> editors, so I think this should be fine.
>
> Please speak up soon if you disagree.
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--0000000000004d643f05c09b80c2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:#000000">ACK adding Kalle.</div><d=
iv class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;=
font-size:small;color:#000000"><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">K=
alle is a qualified reviewer / editor and well suited for this role.<br cle=
ar=3D"all"></div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smart=
mail=3D"gmail_signature"><div dir=3D"ltr">--<br><a href=3D"https://twitter.=
com/JeremyRubin" target=3D"_blank">@JeremyRubin</a><a href=3D"https://twitt=
er.com/JeremyRubin" target=3D"_blank"></a></div></div></div><br></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr=
22, 2021 at 7:09 PM Luke Dashjr via bitcoin-dev <<a href=3D"mailto:bitc=
oin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a=
>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Unl=
ess there are objections, I intend to add Kalle Alm as a BIP editor to <br>
assist in merging PRs into the bips git repo.<br>
<br>
Since there is no explicit process to adding BIP editors, IMO it should be =
<br>
fine to use BIP 2's Process BIP progression:<br>
<br>
> A process BIP may change status from Draft to Active when it achieves<=
br>
> rough consensus on the mailing list. Such a proposal is said to have<b=
r>
> rough consensus if it has been open to discussion on the development<b=
r>
> mailing list for at least one month, and no person maintains any<br>
> unaddressed substantiated objections to it.<br>
<br>
A Process BIP could be opened for each new editor, but IMO that is <br>
unnecessary. If anyone feels there is a need for a new Process BIP, we can =
go <br>
that route, but there is prior precedent for BIP editors appointing new BIP=
<br>
editors, so I think this should be fine.<br>
<br>
Please speak up soon if you disagree.<br>
<br>
Luke<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--0000000000004d643f05c09b80c2--
|
