Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <sustrik@250bpm.com>) id 1VY9o2-0000fL-Qp
	for bitcoin-development@lists.sourceforge.net;
	Mon, 21 Oct 2013 07:21:38 +0000
X-ACL-Warn: 
Received: from chrocht.moloch.sk ([62.176.169.44] helo=mail.moloch.sk)
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1VY9o1-0005Ju-7z
	for bitcoin-development@lists.sourceforge.net;
	Mon, 21 Oct 2013 07:21:38 +0000
Received: from [192.168.0.102] (ip66.bbxnet.sk [91.219.133.66])
	by mail.moloch.sk (Postfix) with ESMTPSA id CC13B1801144;
	Mon, 21 Oct 2013 09:03:55 +0200 (CEST)
Message-ID: <5264D1DB.5060107@250bpm.com>
Date: Mon, 21 Oct 2013 09:03:55 +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: Jean-Paul Kogelman <jeanpaulkogelman@me.com>, 
	Peter Todd <pete@petertodd.org>
References: <38895569-E6E1-4576-9E36-B00B53F9D3CC@me.com>	<201310192229.19932.luke@dashjr.org>	<CAAS2fgRu1j0w8RsiYutixEDxs1NYZVxQ7D7VRgDVi1b-wx+vUQ@mail.gmail.com>	<19909B49-0895-4130-99FB-9A116140CFE9@me.com>	<20131019235746.GA29032@savin>	<9EF588BB-14B5-495A-8253-82574DCB1A8A@me.com>	<20131020224316.GA25280@savin>	<CAJHLa0OTHKaCOnpVBqapxc3xBwkgr4F9cCi0=15P4b80oVc51w@mail.gmail.com>	<20131021062555.GA10784@savin>	<80401395-792A-4637-A75C-1D499C547F98@me.com>	<20131021064320.GA17190@savin>
	<AD405CE3-3E5D-4927-9A0E-43238ED3FDFC@me.com>
In-Reply-To: <AD405CE3-3E5D-4927-9A0E-43238ED3FDFC@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1VY9o1-0005Ju-7z
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2013 07:21:39 -0000

On 21/10/13 08:52, Jean-Paul Kogelman wrote:
> How about putting them into sub directories that map onto the status of the BIP?
>
> Reading BIP 1, that would make:
>
> Accepted
> Active
> Draft
> Deferred
> Final
> Rejected
> Replaced
> Withdrawn

Have it been considered to do this via IETF? The process there is 
hardened by 40 years of experience and 7000+ RFCs. Probably better than 
anything you can devise yourself.

Martin