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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <drak@zikula.org>) id 1VioYv-0004eE-UM
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 16:54:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
designates 74.125.82.54 as permitted sender)
client-ip=74.125.82.54; envelope-from=drak@zikula.org;
helo=mail-wg0-f54.google.com;
Received: from mail-wg0-f54.google.com ([74.125.82.54])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VioYv-0006yr-23
for bitcoin-development@lists.sourceforge.net;
Tue, 19 Nov 2013 16:54:05 +0000
Received: by mail-wg0-f54.google.com with SMTP id y10so7947531wgg.33
for <bitcoin-development@lists.sourceforge.net>;
Tue, 19 Nov 2013 08:53:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=uBbe1GROWUVnPBBxlQ8mVPKvKpi5d1uA+11HfhzdfBI=;
b=Qg9PfR1SKrPPGqqR2kYN4NmyMPXD9lv/RRD1wYxTgdx5ENZMZ0uPYhCORb5IL3HW2q
6Y1X59ItWBoR0fkS6G66tKdX7Ti3zAG6KNVEnPUWKlVllg276LQMQ/fPJjDW2sY44SjE
QmviQCfE7m5ADXJwPNlCZTyJprTe+Z91YM5+2j/96OuzqV1rZFeKDXjdoVc0uTwIdbJ+
mm040TiYRCdGysxM323zORQiwGn0kOHfcW9LCkIDMNlaCNqI43hywjwekNR7ZzhiVArJ
WEezW1kNmICuB67NZjnJHXAtvLiIgZlUbq1BSrzRD1ACowA11rApL0EStlB18hbM82H9
OUgQ==
X-Gm-Message-State: ALoCoQkzJd7kPxL7xE+/8dOTLXjvga3VG5V0V8sFw+78QIwCh1n3Z0Rx2MckOCW9oa1sHzbbvfqE
X-Received: by 10.180.89.1 with SMTP id bk1mr19014944wib.17.1384880038736;
Tue, 19 Nov 2013 08:53:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.93.105 with HTTP; Tue, 19 Nov 2013 08:53:38 -0800 (PST)
In-Reply-To: <CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>
References: <CAJHLa0MCJzFapBYu+cGcJobeVkuS3yibpgaEJOmEj5-1wWEDYA@mail.gmail.com>
<CA+s+GJDnCx4ZT5woovB-MsKfHOqNoC9WefKQ-VMpWHCZrat5Kw@mail.gmail.com>
From: Drak <drak@zikula.org>
Date: Tue, 19 Nov 2013 16:53:38 +0000
Message-ID: <CANAnSg1eH8+sY6n4-cptdzS5Qj0aXdN_d8h8B9joyk73HGL6ZA@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04447f85c40f9204eb8a8236
X-Spam-Score: -0.5 (/)
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VioYv-0006yr-23
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:54:06 -0000
--f46d04447f85c40f9204eb8a8236
Content-Type: text/plain; charset=UTF-8
On 19 November 2013 16:32, Wladimir <laanwj@gmail.com> 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).
>
> 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.
>
It's quite normal for standards bodies to allocate numbers when in draft
status. If they don't pass, they don't pass - they are clearly labelled
DRAFTs.
+1 on having things in a github repository. Much better for collaboration,
Drak
--f46d04447f85c40f9204eb8a8236
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
9 November 2013 16:32, Wladimir <span dir=3D"ltr"><<a href=3D"mailto:laa=
nwj@gmail.com" target=3D"_blank">laanwj@gmail.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">
<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.</div></div></div></div></blockquote><div><br></div><div=
>It's quite normal for standards bodies to allocate numbers when in dra=
ft status. If they don't pass, they don't pass - they are clearly l=
abelled DRAFTs.</div>
<div><br></div><div>+1 on having things in a github repository. Much better=
for collaboration,</div><div><br></div><div>Drak</div>
</div></div></div>
--f46d04447f85c40f9204eb8a8236--
|
