From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VY3Lf-0004t0-5s for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 00:27:55 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.44 as permitted sender) client-ip=74.125.82.44; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f44.google.com; Received: from mail-wg0-f44.google.com ([74.125.82.44]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VY3Le-00050M-6p for bitcoin-development@lists.sourceforge.net; Mon, 21 Oct 2013 00:27:55 +0000 Received: by mail-wg0-f44.google.com with SMTP id n12so5846402wgh.35 for ; Sun, 20 Oct 2013 17:27:48 -0700 (PDT) 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:date :message-id:subject:from:to:cc:content-type; bh=uHmF6Cmym06bgzXX2f8crsbEDq01ZAiEqOIw+Jc5QuA=; b=f56ASxe7LaEG8SadMGGVIctAebKAWzYGXN5HRh13C3PiqXMqx/Z+BgKYhYBaUGM1w1 5ozrJPDJGgY4PMY1Z5p+/iE+hNok2EheRDoJNOJleapE4q6oHc1DfEZitrkt3V/ngJd4 kiB6hSFzWNbtYCIN7G4MGTQwPYaYNZb9cPITA43TDmhWzGK0Yi1qEYFHwSfqPN0ht4Wv oYiWBIwc21YTyzi/dR1HUY1wRVQTGLnFZ8VrMzD4u42AwewibiS3shjR+6BABzmmmRI/ gl/u8EbsO8EV63R9K76BH6dACIeTz+dwIcQMVJHhYHJ0F1+zEDF8oOazwHN41A74y5n/ 9ITw== X-Gm-Message-State: ALoCoQnVp+v8L1xMoFE/hzt5Ay1s3b364N/tGJhNQcTvpVYHV1o1+1VRtZmv40m2AgDnt3L+BxZh MIME-Version: 1.0 X-Received: by 10.180.73.239 with SMTP id o15mr7503477wiv.36.1382315267993; Sun, 20 Oct 2013 17:27:47 -0700 (PDT) Received: by 10.194.164.164 with HTTP; Sun, 20 Oct 2013 17:27:47 -0700 (PDT) In-Reply-To: <20131020224316.GA25280@savin> References: <38895569-E6E1-4576-9E36-B00B53F9D3CC@me.com> <201310192229.19932.luke@dashjr.org> <19909B49-0895-4130-99FB-9A116140CFE9@me.com> <20131019235746.GA29032@savin> <9EF588BB-14B5-495A-8253-82574DCB1A8A@me.com> <20131020224316.GA25280@savin> Date: Sun, 20 Oct 2013 20:27:47 -0400 Message-ID: From: Jeff Garzik To: Peter Todd Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 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: bitpay.com] -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: 1VY3Le-00050M-6p Cc: Bitcoin Development Subject: Re: [Bitcoin-development] A critique of bitcoin open source community 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: Mon, 21 Oct 2013 00:27:55 -0000 On Sun, Oct 20, 2013 at 6:43 PM, Peter Todd 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. -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/