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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1VioEZ-0005Vi-8H
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 16:33:03 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.43 as permitted sender)
client-ip=209.85.214.43; envelope-from=laanwj@gmail.com;
helo=mail-bk0-f43.google.com;
Received: from mail-bk0-f43.google.com ([209.85.214.43])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VioEY-0007gm-1K
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 16:33:03 +0000
Received: by mail-bk0-f43.google.com with SMTP id mz12so940337bkb.16
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Nov 2013 08:32:55 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.204.111.200 with SMTP id t8mr53390bkp.43.1384878775581; Tue,
19 Nov 2013 08:32:55 -0800 (PST)
Received: by 10.204.71.206 with HTTP; Tue, 19 Nov 2013 08:32:55 -0800 (PST)
In-Reply-To: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
References: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
Date: Tue, 19 Nov 2013 17:32:55 +0100
Message-ID: <CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a113359ba79f08704eb8a37bc
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: 1VioEY-0007gm-1K
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 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 16:33:03 -0000
--001a113359ba79f08704eb8a37bc
Content-Type: text/plain; charset=UTF-8
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).
2) Time passes. Software for BIP drafts is developed, tested,
> published, and publicly discussed in a typical open source manner.
>
Personally I think it is useful to have a number as soon as a BIP can be
implemented, even if still in draft status; it gives something to refer to
when mentioning a certain improvement proposal (in commit messages and such
it could be called BIP xxx Draft).
I don't think we are at risk of running out of numbers to assign any time
soon.
Wladimir
--001a113359ba79f08704eb8a37bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik <span dir=3D"ltr"><<a href=
=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>>=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">BIP drafts are stored in git://<a href=3D"ht=
tp://github.com/bitcoin/bips.git/drafts/" target=3D"_blank">github.com/bitc=
oin/bips.git/drafts/</a> and<br>
are not automatically assigned a BIPS number.<br></blockquote><div><br></di=
v><div>Are we going to move ahead with this?<br><br></div><div>If so, I'=
;m volunteering to create the repository and import the current BIPs from t=
he wiki there (and convert from wiki markup to markdown where necessary).<b=
r>
</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) Time passes. =C2=A0Software for BIP drafts is developed, tested,<br>
published, and publicly discussed in a typical open source manner.<br></blo=
ckquote><div><br></div><div>Personally I think it is useful to have a numbe=
r as soon as a BIP can be implemented, even if still in draft status; it gi=
ves something to refer to when mentioning a certain improvement proposal (i=
n commit messages and such it could be called BIP xxx Draft).<br>
</div><div>I don't think we are at risk of running out of numbers to as=
sign any time soon.<br></div><div><br></div><div>Wladimir<br></div></div></=
div></div>
--001a113359ba79f08704eb8a37bc--
|
