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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <decker.christian@gmail.com>) id 1RGqmy-0007ff-Q2
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Oct 2011 11:27:56 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=decker.christian@gmail.com;
helo=mail-ww0-f53.google.com;
Received: from mail-ww0-f53.google.com ([74.125.82.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RGqmx-0003Ui-LH
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Oct 2011 11:27:56 +0000
Received: by wwi36 with SMTP id 36so3644566wwi.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 20 Oct 2011 04:27:49 -0700 (PDT)
Received: by 10.227.201.133 with SMTP id fa5mr181369wbb.91.1319110069322; Thu,
20 Oct 2011 04:27:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.128.13 with HTTP; Thu, 20 Oct 2011 04:27:08 -0700 (PDT)
In-Reply-To: <CAL0fb61d0zd94qYpKT8hDfE-QiTWN7K510O1e4Gm5o=PjNWFwg@mail.gmail.com>
References: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
<CAL0fb61d0zd94qYpKT8hDfE-QiTWN7K510O1e4Gm5o=PjNWFwg@mail.gmail.com>
From: Christian Decker <decker.christian@gmail.com>
Date: Thu, 20 Oct 2011 13:27:08 +0200
Message-ID: <CALxbBHWi88HkrmR3nBA1zoMzMd3PaFTTBwu_VM2etc4S3HYvDA@mail.gmail.com>
To: Alex Waters <ampedal@gmail.com>
Content-Type: multipart/alternative; boundary=0015174c40aa1a05b104afb93fda
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(decker.christian[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1RGqmx-0003Ui-LH
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP process
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2011 11:27:56 -0000
--0015174c40aa1a05b104afb93fda
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
On Thu, Oct 20, 2011 at 7:02 AM, Alex Waters <ampedal@gmail.com> wrote:
>
>> =95 I propose that BIPs be wiki pages, with a social convention that the
>> Author gets final word if any editing wars break out.
>
>
> ACK
>
Does it have to be wiki pages if we're going through an editorial process
anyway, and there will be few who can actually edit the pages directly? I'd
go for simple HTML documents in a repository.
>
>
> =95 If he's willing, I propose that Amir take the role of BIP editor.
>>
>> ACK
>
ACK
>
>
>> =95 I think bitcoin is still too small to have a specialized
>> "bitcoin-ideas" mailing list; I propose that new potential BIPs be
>> discussed either here or on the bitcoin-dev mailing list.
>>
>
> ACK
>
Definitely. I don't think too many requests will come right away, and by
posting them here we make sure that the most knowledgeable people are there
to check and improve what might eventually end up in the clients.
>
> As for what Nils mentioned on using GitHub's Wiki feature, Gavin seems to
> have started a few proposals at
> https://github.com/gavinandresen/bitcoin-git/wiki. I think this is the
> right direction to head in, and a composite list of similar proposals cou=
ld
> be maintained on their own repository (to maintain separation from the co=
re
> Bitcoin repo.)
>
> -Alex
>
>
> -------------------------------------------------------------------------=
-----
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Ciosco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--0015174c40aa1a05b104afb93fda
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_quote">On Thu, Oct 20, 2011 at 7:02 AM, Alex Waters=
<span dir=3D"ltr"><<a href=3D"mailto:ampedal@gmail.com">ampedal@gmail.c=
om</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><br>
=95 I propose that BIPs be wiki pages, with a social convention that the<br=
>
Author gets final word if any editing wars break out.</blockquote><div><br>=
</div></div><div>ACK</div></div></blockquote><div>Does it have to be wiki p=
ages if we're going through an editorial process anyway, and there will=
be few who can actually edit the pages directly? I'd go for simple HTM=
L documents in a repository. <br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=
=3D"gmail_quote"><div class=3D"im"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
=95 If he's willing, I propose that Amir take the role of BIP editor.<b=
r>
<br></blockquote></div><div>ACK</div></div></blockquote><div>ACK <br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"gma=
il_quote">
<div class=3D"im"><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=95 I think bitcoin is still too small to have a specialized<br>
"bitcoin-ideas" mailing list; I propose that new potential BIPs b=
e<br>
discussed either here or on the bitcoin-dev mailing list.<br></blockquote><=
div><br></div></div><div>ACK</div></div></blockquote><div>Definitely. I don=
't think too many requests will come right away, and by posting them he=
re we make sure that the most knowledgeable people are there to check and i=
mprove what might eventually end up in the clients.<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=
=3D"gmail_quote"><div><br></div><div>As for what Nils mentioned on using Gi=
tHub's Wiki feature, Gavin seems to have started a few proposals at=A0<=
a href=3D"https://github.com/gavinandresen/bitcoin-git/wiki" target=3D"_bla=
nk">https://github.com/gavinandresen/bitcoin-git/wiki</a>. I think this is =
the right direction to head in, and a composite list of similar proposals c=
ould be maintained on their own repository (to maintain separation from the=
core Bitcoin repo.)</div>
<div><br></div><font color=3D"#888888"><div>-Alex</div></font></div>
<br>-----------------------------------------------------------------------=
-------<br>
The demand for IT networking professionals continues to grow, and the<br>
demand for specialized networking skills is growing even more rapidly.<br>
Take a complimentary Learning@Ciosco Self-Assessment and learn<br>
about Cisco certifications, training, and career opportunities.<br>
<a href=3D"http://p.sf.net/sfu/cisco-dev2dev" target=3D"_blank">http://p.sf=
.net/sfu/cisco-dev2dev</a><br>_____________________________________________=
__<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br>
--0015174c40aa1a05b104afb93fda--
|
