From: Peter Todd <pete@petertodd•org>
To: Jeff Garzik <jgarzik@bitpay•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] A critique of bitcoin open source community
Date: Mon, 21 Oct 2013 02:25:55 -0400 [thread overview]
Message-ID: <20131021062555.GA10784@savin> (raw)
In-Reply-To: <CAJHLa0OTHKaCOnpVBqapxc3xBwkgr4F9cCi0=15P4b80oVc51w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
On Sun, Oct 20, 2013 at 08:27:47PM -0400, Jeff Garzik wrote:
> On Sun, Oct 20, 2013 at 6:43 PM, Peter Todd <pete@petertodd•org> wrote:
> > FWIW I think that BIP's should have been done as a github repository,
> > allowing for dealing with this stuff transparently as a pull-request.
> > It'd also be useful to handle BIP's that way to make it easy to archive
> > them, update them, and keep a log of what and why they were updated.
> > Just put them in markdown format, which is pretty much feature
> > equivalent to the wiki now that markdown supports images.
>
> Agreed -- let's do it. I nominate you to do the conversion, and we'll
> put it up at github.com/bitcoin/bips.git.
Done: https://github.com/petertodd/bips/
GitHub supports MediaWiki these days, so just directly copying from
'View Source' in the bitcoin.it wiki worked pretty well; I archived the
exact text of BIP. Tables, images and math is all supported by github
and look fine, although github doesn't seem to support coloration in
tables. Users wishing to edit their pull-req's or create new ones can do
so easily by forking the repository - they can see their changes as they
go in GitHub.
I've probably missed some stuff re: formatting, and I haven't changed
any of the submission guideline text in bip 1 yet, but that's probably
90% of the work done.
--
'peter'[:-1]@petertodd.org
000000000000000245a735ccc14b98552e152f773c07efa2e89dd7f0463f61cf
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 685 bytes --]
next prev parent reply other threads:[~2013-10-21 6:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 16:38 Mitar
2013-10-19 16:50 ` Melvin Carvalho
2013-10-19 20:40 ` Gregory Maxwell
2013-10-19 21:09 ` Mitar
2013-10-19 21:16 ` Jean-Paul Kogelman
2013-10-19 22:29 ` Luke-Jr
2013-10-19 23:20 ` Gregory Maxwell
2013-10-19 23:35 ` Jean-Paul Kogelman
2013-10-19 23:57 ` Peter Todd
2013-10-20 0:52 ` Jean-Paul Kogelman
2013-10-20 22:43 ` Peter Todd
2013-10-20 23:11 ` Peter Todd
2013-10-21 0:27 ` Jeff Garzik
2013-10-21 6:25 ` Peter Todd [this message]
2013-10-21 6:40 ` Jean-Paul Kogelman
2013-10-21 6:43 ` Peter Todd
2013-10-21 6:52 ` Jean-Paul Kogelman
2013-10-21 7:03 ` Martin Sustrik
2013-10-21 7:07 ` Jean-Paul Kogelman
2013-10-21 7:28 ` Martin Sustrik
2013-10-21 9:36 ` Melvin Carvalho
2013-10-21 9:44 ` Arto Bendiken
2013-10-21 9:49 ` Jean-Paul Kogelman
2013-10-21 10:21 ` Jorge Timón
2013-10-20 10:00 ` Wladimir
2013-10-19 23:21 ` Jean-Paul Kogelman
2013-10-19 23:22 ` Jean-Paul Kogelman
2013-10-19 22:33 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131021062555.GA10784@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@bitpay$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox