From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VYcd3-00012R-Db for bitcoin-development@lists.sourceforge.net; Tue, 22 Oct 2013 14:08:13 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.176 as permitted sender) client-ip=209.85.212.176; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f176.google.com; Received: from mail-wi0-f176.google.com ([209.85.212.176]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VYcd2-0007vy-Bz for bitcoin-development@lists.sourceforge.net; Tue, 22 Oct 2013 14:08:13 +0000 Received: by mail-wi0-f176.google.com with SMTP id l12so5741303wiv.9 for ; Tue, 22 Oct 2013 07:08:06 -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=xi+sS2Wkt6o2ywUqgi2sWe2nlgRTzFA8UO0PGxHzUIY=; b=W4GDI39/9xyPZMjjzqrpmsFH9NiklDj25cUHzsKmsunvbnbc9Qf4H62AecYo6uIZgX xTkfKW82nc/A+1+x3uPhkdrmS//FI/ny+viLiM7OFh7JpaInNtR/csRJgmZrItXHeC2T gr3id7nxwAvCyJoUbzJkB9gOYU3ftbup/bF5jQ9tRmo/bBRk9Ex5MKRip5Q7Qa25cCk6 nTs/vNJzpDWuGyix3Ey3pDShy3Q41NDlrZKp5kH7rFaBe/9Ov52TUOaJVmAS5de+cKLw uZu/FGGwxm9PX7QjUevxHy0lC0lbI27vtCzjBxY5g6tMDohmQ0TV91cwusog7tAx3QXb YYNQ== X-Gm-Message-State: ALoCoQkBlyPqO46YjtyQEhpabqpLn3pUdsUyOi6iqwA91r3whcfX1Pr+UhyyCB4lNdnGOCeF+Vpz MIME-Version: 1.0 X-Received: by 10.180.78.167 with SMTP id c7mr14642090wix.25.1382450886180; Tue, 22 Oct 2013 07:08:06 -0700 (PDT) Received: by 10.194.164.164 with HTTP; Tue, 22 Oct 2013 07:08:06 -0700 (PDT) In-Reply-To: <52662AA1.5050509@250bpm.com> References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com> <201310211947.59640.luke@dashjr.org> <52661DB7.7040805@250bpm.com> <52662AA1.5050509@250bpm.com> Date: Tue, 22 Oct 2013 10:08:06 -0400 Message-ID: From: Jeff Garzik To: Martin Sustrik 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. 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: doubleclick.net] -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.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: 1VYcd2-0007vy-Bz Cc: Bitcoin Development Subject: Re: [Bitcoin-development] 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, 22 Oct 2013 14:08:13 -0000 All that is good practice, but we should avoid adding burdensome process that might discourage BIP writing. Consider a distributed approach: if you feel a draft needs more sections or better language, submit a pull request yourself and help community-edit the document. On Tue, Oct 22, 2013 at 3:34 AM, Martin Sustrik wrote: > On 22/10/13 09:03, Gregory Maxwell wrote: >> On Mon, Oct 21, 2013 at 11:59 PM, Jean-Paul Kogelman >> wrote: >>> Have you seen: https://en.bitcoin.it/wiki/Protocol_specification ? >> >> Take care, the information in the wiki is woefully incomplete. > > Imagine myself, with no prior knowledge of Bitcoin looking at the > document. It starts with "Hashes". What hashes? No idea what's going on. > Etc. > > Now compare that to a well written RFC. It starts with introduction, > description of the problem, explains the conceptual model of the > solution, then dives into the details. There's also Security > Considerations part in every RFC that is pretty relevant for Bitcoin. > > As I said, I am willing to help with writing such document, it would be > a nice way of learning the stuff, however, help from core devs, such as > answering question that may arise in the process, or reviewing the > document would be needed. > > Martin > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/