From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1ViogB-0002Lq-G2 for bitcoin-development@lists.sourceforge.net; Tue, 19 Nov 2013 17:01:35 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.41 as permitted sender) client-ip=209.85.215.41; envelope-from=gmaxwell@gmail.com; helo=mail-la0-f41.google.com; Received: from mail-la0-f41.google.com ([209.85.215.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Viog9-0001u3-0X for bitcoin-development@lists.sourceforge.net; Tue, 19 Nov 2013 17:01:35 +0000 Received: by mail-la0-f41.google.com with SMTP id eo20so242422lab.14 for ; Tue, 19 Nov 2013 09:01:26 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.130.168 with SMTP id of8mr114085lbb.66.1384880486283; Tue, 19 Nov 2013 09:01:26 -0800 (PST) Received: by 10.112.63.162 with HTTP; Tue, 19 Nov 2013 09:01:26 -0800 (PST) In-Reply-To: References: Date: Tue, 19 Nov 2013 09:01:26 -0800 Message-ID: From: Gregory Maxwell To: Drak Content-Type: text/plain; charset=UTF-8 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -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: zikula.org] -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: 1Viog9-0001u3-0X Cc: Bitcoin Dev 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, 19 Nov 2013 17:01:35 -0000 On Tue, Nov 19, 2013 at 8:53 AM, Drak wrote: > It's quite normal for standards bodies to allocate numbers when in draft > status. If they don't pass, they don't pass - they are clearly labelled > DRAFTs. > > +1 on having things in a github repository. Much better for collaboration, The IETF makes a clear distinction between individual proposals and documents which have been accepted by a working group. The former are named after their authors. Work is not assigned a number until it is complete. I believe it is important to distinguish complete work that people should be implementing from things which are incomplete, and even more important to distinguish the work of single parties. Otherwise you're going to get crap like BIP90: "Increase the supply of Bitcoins to 210 million" being confused as an earnest proposal supported by many that has traction.