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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ampedal@gmail.com>) id 1RGkls-00014N-DU
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Oct 2011 05:02:24 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.47 as permitted sender)
client-ip=209.85.216.47; envelope-from=ampedal@gmail.com;
helo=mail-qw0-f47.google.com;
Received: from mail-qw0-f47.google.com ([209.85.216.47])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1RGklr-0003ze-GM
for bitcoin-development@lists.sourceforge.net;
Thu, 20 Oct 2011 05:02:24 +0000
Received: by qam2 with SMTP id 2so2508401qam.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 19 Oct 2011 22:02:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.81.197 with SMTP id y5mr2161000qck.266.1319086938016; Wed,
19 Oct 2011 22:02:18 -0700 (PDT)
Received: by 10.229.3.68 with HTTP; Wed, 19 Oct 2011 22:02:17 -0700 (PDT)
In-Reply-To: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
References: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
Date: Thu, 20 Oct 2011 01:02:17 -0400
Message-ID: <CAL0fb61d0zd94qYpKT8hDfE-QiTWN7K510O1e4Gm5o=PjNWFwg@mail.gmail.com>
From: Alex Waters <ampedal@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=0016361640995e4c0a04afb3dcb5
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
(ampedal[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: 1RGklr-0003ze-GM
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 05:02:24 -0000
--0016361640995e4c0a04afb3dcb5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
>
>
> =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
>
=95 If he's willing, I propose that Amir take the role of BIP editor.
>
> 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
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 righ=
t
direction to head in, and a composite list of similar proposals could be
maintained on their own repository (to maintain separation from the core
Bitcoin repo.)
-Alex
--0016361640995e4c0a04afb3dcb5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n: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>ACK=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">=A0</blockquote><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex;">
=95 If he's willing, I propose that Amir take the role of BIP editor.<b=
r>
<br></blockquote><div>ACK</div><div>=A0</div><blockquote class=3D"gmail_quo=
te" 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>ACK</div><div><br></div><div>As for what Nils mentioned =
on using GitHub's Wiki feature, Gavin seems to have started a few propo=
sals at=A0<a href=3D"https://github.com/gavinandresen/bitcoin-git/wiki">htt=
ps://github.com/gavinandresen/bitcoin-git/wiki</a>. I think this is the rig=
ht direction to head in, and a composite list of similar proposals could be=
maintained on their own repository (to maintain separation from the core B=
itcoin repo.)</div>
<div><br></div><div>-Alex</div></div>
--0016361640995e4c0a04afb3dcb5--
|
