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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1Viozu-0000AM-CK
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 17:21:58 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.41 as permitted sender)
client-ip=209.85.214.41; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f41.google.com;
Received: from mail-bk0-f41.google.com ([209.85.214.41])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Viozt-0002oU-Ei
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 17:21:58 +0000
Received: by mail-bk0-f41.google.com with SMTP id v15so3260161bkz.28
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Nov 2013 09:21:51 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.205.14.69 with SMTP id pp5mr17002107bkb.14.1384881710970;
Tue, 19 Nov 2013 09:21:50 -0800 (PST)
Received: by 10.204.71.206 with HTTP; Tue, 19 Nov 2013 09:21:50 -0800 (PST)
In-Reply-To: <CA+s+GJA=p+yvoJqUAMQQRcfYK1B8eMVSJDWaXW8o+X5dzCXkdA@mail.gmail.com>
References: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
<CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>
<20131119170612.GA30105@petertodd.org>
<CA+s+GJA=p+yvoJqUAMQQRcfYK1B8eMVSJDWaXW8o+X5dzCXkdA@mail.gmail.com>
Date: Tue, 19 Nov 2013 18:21:50 +0100
Message-ID: <CA+s+GJDV0R=GjbDwyWMjB85E8CT28os0E33rr_u5E1Yw7=v4qg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf30223a83706ba804eb8ae650
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-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
(laanwj[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: 1Viozt-0002oU-Ei
Subject: [Bitcoin-development] Fwd: Revisiting the BIPS process, a proposal
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: Tue, 19 Nov 2013 17:21:58 -0000
--20cf30223a83706ba804eb8ae650
Content-Type: text/plain; charset=UTF-8
On Tue, Nov 19, 2013 at 6:06 PM, Peter Todd <pete@petertodd.org> wrote:
> On Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote:
> > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> >
> > > BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and
> > > are not automatically assigned a BIPS number.
> > >
> >
> > Are we going to move ahead with this?
> >
> > If so, I'm volunteering to create the repository and import the current
> > BIPs from the wiki there (and convert from wiki markup to markdown where
> > necessary).
>
> I already did that:
>
> https://github.com/petertodd/bips
>
Ok cool, I forked it into https://github.com/bitcoin/bips
> GitHub can render MediaWiki just fine, so I think leaving the BIPs as
> MediaWiki is the way to go. New BIPs may want to use either markdown or
> MediaWiki - the latter has advantages in terms of formatting
> capabilities over the former, particularly when math needs to be
> displayed.
>
Agreed, I had no idea github could do that too.
Wladimir
--20cf30223a83706ba804eb8ae650
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Tue, Nov 19, 2013 at 6:06 PM, Peter Todd <span dir=3D"l=
tr"><<a href=3D"mailto:pete@petertodd.org" target=3D"_blank">pete@petert=
odd.org</a>></span> wrote:<br>
<div class=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On=
Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote:<br>
> On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik <<a href=3D"mailto:jga=
rzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>> wrote:<br>
><br>
> > BIP drafts are stored in git://<a href=3D"http://github.com/bitco=
in/bips.git/drafts/" target=3D"_blank">github.com/bitcoin/bips.git/drafts/<=
/a> and<br>
> > are not automatically assigned a BIPS number.<br>
> ><br>
><br>
> Are we going to move ahead with this?<br>
><br>
> If so, I'm volunteering to create the repository and import the cu=
rrent<br>
> BIPs from the wiki there (and convert from wiki markup to markdown whe=
re<br>
> necessary).<br>
<br>
I already did that:<br>
<br>
<a href=3D"https://github.com/petertodd/bips" target=3D"_blank">https://git=
hub.com/petertodd/bips</a><br></blockquote><div><br></div><div>Ok cool, I f=
orked it into <a href=3D"https://github.com/bitcoin/bips" target=3D"_blank"=
>https://github.com/bitcoin/bips</a><br>
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
GitHub can render MediaWiki just fine, so I think leaving the BIPs as<br>
MediaWiki is the way to go. New BIPs may want to use either markdown or<br>
MediaWiki - the latter has advantages in terms of formatting<br>
capabilities over the former, particularly when math needs to be<br>
displayed.<br></blockquote><div><br></div><div>Agreed, I had no idea github=
could do that too.<span class=3D"HOEnZb"><font color=3D"#888888"><br></fon=
t></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></di=
v><div>
Wladimir<br></div></font></span></div></div></div>
</div><br></div>
--20cf30223a83706ba804eb8ae650--
|
