Message-ID: <52662AA1.5050509@250bpm.com>
Date: Tue, 22 Oct 2013 09:34:57 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Gregory Maxwell <gmaxwell@gmail.com>, 
	Jean-Paul Kogelman <jeanpaulkogelman@me.com>
References: <791a727f-2188-4848-bd77-ea733c8c5c2c@me.com>	<201310211947.59640.luke@dashjr.org>	<52661DB7.7040805@250bpm.com>	<FAE2A544-9295-4087-96DE-D4602D109CBD@me.com>
	<CAAS2fgS2f=gYRSr1n2DzK7CUH3xG3J2JMnDreCKBoCcJcpGLxg@mail.gmail.com>
In-Reply-To: <CAAS2fgS2f=gYRSr1n2DzK7CUH3xG3J2JMnDreCKBoCcJcpGLxg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revisiting the BIPS process, a proposal
Precedence: list

On 22/10/13 09:03, Gregory Maxwell wrote:
> On Mon, Oct 21, 2013 at 11:59 PM, Jean-Paul Kogelman
> <jeanpaulkogelman@me.com> 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