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; 
MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
Precedence: list

--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">&lt;<a href=
=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt;=
</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&#39=
;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&#39;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--