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 ) 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 ; 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: References: <20131119170612.GA30105@petertodd.org> Date: Tue, 19 Nov 2013 18:21:50 +0100 Message-ID: From: Wladimir To: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 wrote: > On Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote: > > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik 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
On Tue, Nov 19, 2013 at 6:06 PM, Peter Todd <pete@petert= odd.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/<= /a> 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 cu= rrent
> BIPs from the wiki there (and convert from wiki markup to markdown whe= re
> necessary).

I already did that:

https://git= hub.com/petertodd/bips

Ok cool, I f= orked it into https://github.com/bitcoin/bips
=C2=A0
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--