Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of
	nilsschneider.net designates 217.11.48.105 as permitted sender)
	client-ip=217.11.48.105; envelope-from=nils@nilsschneider.net;
	helo=ngcobalt05.manitu.net; 
Message-ID: <4E9DEEFE.9040301@nilsschneider.net>
Date: Tue, 18 Oct 2011 23:26:22 +0200
From: Nils Schneider <nils@nilsschneider.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
In-Reply-To: <CABsx9T0xjz2bO0PKX7VBka_j_MpGky9scHhkyM=b9MbtPAwx=A@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] BIP process
Precedence: list


> =95 I propose that BIPs be wiki pages, with a social convention that th=
e
> Author gets final word if any editing wars break out.

That's a good idea. What about using GitHub's Wiki feature for BIPs?
They support MarkDown which is easy to read in text editors so we could
someday create a repo with all finalized BIPs. That's a lot easier than
importing a mediawiki dump. The last time en.bitcoin.it went down I
tried to setup a static mirror and that was nearly impossible without a
full LAMP stack. Also, BIPs should only contain images when absolutely
necessary.

> =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