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
|
Return-Path: <mus@musalbas.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 40C99CF8
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 00:45:20 +0000 (UTC)
X-Greylist: delayed 00:08:36 by SQLgrey-1.7.6
Received: from science.musalbas.com (science.musalbas.com [195.154.112.130])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E56B416F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 00:45:18 +0000 (UTC)
Received: from [10.7.0.6] (unknown [10.7.0.6])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client did not present a certificate)
by science.musalbas.com (Postfix) with ESMTPSA id D18376A09BC
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 10 Mar 2016 00:37:46 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=musalbas.com;
s=mail; t=1457570266;
bh=gN+WcNHwW0pGO+sWa1uFuBa1AClZuvBIcf22SuDZqu4=;
h=Subject:To:References:From:Date:In-Reply-To;
b=C1+eO7QT9Y9N7v6Au0dwg8p7quCzC+a1499f/raVzd4CIlxdDMBOSZl696qJzDF77
+FDldwu4rllhNUFdA5NGySci/skO3xSm+jmGn8GPmpcJjnVfw+XoN2Wevgqho649UJ
uz7E33En9+vyAmHtzS+DrPED2VXy24Jt6EXSHnR4=
To: bitcoin-dev@lists.linuxfoundation.org
References: <201602012253.18009.luke@dashjr.org>
<CABsx9T2X+2Vnwd3RJJvRpNKbO2S1kY8JS2YqHEKUmAhYSNpkBg@mail.gmail.com>
From: Mustafa Al-Bassam <mus@musalbas.com>
Message-ID: <56E0C1DA.4090804@musalbas.com>
Date: Thu, 10 Mar 2016 00:37:46 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CABsx9T2X+2Vnwd3RJJvRpNKbO2S1kY8JS2YqHEKUmAhYSNpkBg@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------080008010804050303010408"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RP_MATCHES_RCVD autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 10 Mar 2016 01:44:53 +0000
Subject: Re: [bitcoin-dev] BIP Process: Status, comments,
and copyright licenses
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Thu, 10 Mar 2016 00:45:20 -0000
This is a multi-part message in MIME format.
--------------080008010804050303010408
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
It would be nice to decouple the venue, but even BIP 1 gives that
control to whoever controls the mailing list: "Following a discussion,
the proposal should be sent to the bitcoin-dev list and the BIP editor
with the draft BIP." (BIP 1)
A neater way to do it might be to replace references to the mailing list
with "public discussion medium" where "medium" can be defined as
something like any discussion forum frequented by the wider development
community, like the pull requests section of the BIP repo, conferences, etc.
On 02/02/16 15:58, Gavin Andresen via bitcoin-dev wrote:
> On Mon, Feb 1, 2016 at 5:53 PM, Luke Dashjr via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>
> I've completed an initial draft of a BIP that provides
> clarifications on the
> Status field for BIPs, as well as adding the ability for public
> comments on
> them, and expanding the list of allowable BIP licenses.
>
> https://github.com/luke-jr/bips/blob/bip-biprevised/bip-biprevised.mediawiki
>
> I plan to open discussion of making this BIP an Active status
> (along with BIP
> 123) a month after initial revisions have completed. Please
> provide any
> objections now, so I can try to address them now and enable
> consensus to be
> reached.
>
>
>
> I like the more concrete definitions of the various statuses.
>
> I don't like the definition of "consensus". I think the definition
> described gives too much centralized control to whoever controls the
> mailing list and the wiki.
>
> --
> --
> Gavin Andresen
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--------------080008010804050303010408
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
It would be nice to decouple the venue, but even BIP 1 gives that
control to whoever controls the mailing list: "Following a
discussion, the proposal should be sent to the bitcoin-dev list and
the BIP editor with the draft BIP." (BIP 1)<br>
<br>
A neater way to do it might be to replace references to the mailing
list with "public discussion medium" where "medium" can be defined
as something like any discussion forum frequented by the wider
development community, like the pull requests section of the BIP
repo, conferences, etc.<br>
<br>
<div class="moz-cite-prefix">On 02/02/16 15:58, Gavin Andresen via
bitcoin-dev wrote:<br>
</div>
<blockquote
cite="mid:CABsx9T2X+2Vnwd3RJJvRpNKbO2S1kY8JS2YqHEKUmAhYSNpkBg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Feb 1, 2016 at 5:53 PM, Luke
Dashjr via bitcoin-dev <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:bitcoin-dev@lists.linuxfoundation.org"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I've
completed an initial draft of a BIP that provides
clarifications on the<br>
Status field for BIPs, as well as adding the ability for
public comments on<br>
them, and expanding the list of allowable BIP licenses.<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/luke-jr/bips/blob/bip-biprevised/bip-biprevised.mediawiki"
rel="noreferrer" target="_blank">https://github.com/luke-jr/bips/blob/bip-biprevised/bip-biprevised.mediawiki</a><br>
<br>
I plan to open discussion of making this BIP an Active
status (along with BIP<br>
123) a month after initial revisions have completed.
Please provide any<br>
objections now, so I can try to address them now and
enable consensus to be<br>
reached.<br>
</blockquote>
<div> </div>
</div>
<div class="gmail_extra"><br>
</div>
<div>I like the more concrete definitions of the various
statuses.</div>
<div><br>
</div>
<div>I don't like the definition of "consensus". I think the
definition described gives too much centralized control to
whoever controls the mailing list and the wiki.</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>--<br>
Gavin Andresen<br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------080008010804050303010408--
|
