summaryrefslogtreecommitdiff
path: root/a3/2b4bac087c70d4a0bc2ee20f83ad7b5c0263b7
blob: f2c0fabbd029fe6d164394e8eb385d77c9c112e3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
Return-Path: <elombrozo@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 05D63A70
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 21:01:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f173.google.com (mail-ig0-f173.google.com
	[209.85.213.173])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id F2972194
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 21:01:35 +0000 (UTC)
Received: by igfj19 with SMTP id j19so65957027igf.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 24 Aug 2015 14:01:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:from:date:message-id:subject:to:content-type;
	bh=P8HD5FwCNiTagbWjWmaQoEVa4nVxXEmZhh61HDfC5qU=;
	b=uOoceQuD9FF85oXmbN52CwTTGirky7DpGxaexbZWNrfeGDcLpCUmgRh7p3kU81lozO
	benPMug//ndWPO0KpH3Ac9dLfDDN6JMgcjktlaFQefSrLhBKcMSPIqKkuZqOZT1jbXxI
	PZ8nx73AeUCOAxh8H2XtdXpB83O2ydDX/K09oh0hPqVUU25mDhCdlZtLiHFPEU0unjTh
	fmXNP6qDdciwJxEy6FZts2Y+5SfrNhwLXdoAb0Z4L2OihETvVpPGB1BpUqX2TqorU8qZ
	pkvJHcpQgrVXyHPt1lh0Sr/NUKZBRJEI0rQacXaSzKbUUn/icmH+RM/CP851EuGYbOlm
	h7sw==
X-Received: by 10.50.110.72 with SMTP id hy8mr15842927igb.36.1440450095433;
	Mon, 24 Aug 2015 14:01:35 -0700 (PDT)
MIME-Version: 1.0
From: Eric Lombrozo <elombrozo@gmail.com>
Date: Mon, 24 Aug 2015 21:01:26 +0000
Message-ID: <CABr1YTcoWesaBJaT--bbUUN-c2phc-=3ieWT7vVDNPGg0iHH2g@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=089e011849d4415061051e14ecd2
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: [bitcoin-dev] Splitting BIPs
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2015 21:01:37 -0000

--089e011849d4415061051e14ecd2
Content-Type: text/plain; charset=UTF-8

Seems like a lot of effort and goodwill is being wasted on contention over
things we don't really need to agree upon. In order to help us better
prioritize, I propose adding an extra attribute to BIPs indicating their
"level" which is split into five as follows:

1. Consensus (hard/soft fork)
2. Peer Services
3. RPC
4. Implementations
5. Applications

I posted an example of what such a table might look like here: http://
blockhawk.net/bitcoin-dev/bipwiki.html

If other folks also think this is a good idea I'll start working on a BIP
draft for this.

--089e011849d4415061051e14ecd2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
Seems like a lot of effort and goodwill is being wasted on contention over =
things we don&#39;t really need to agree upon. In order to help us better p=
rioritize, I propose adding an extra attribute to BIPs indicating their &qu=
ot;level&quot; which is split into five as follows:</p>
<p dir=3D"ltr">1. Consensus (hard/soft fork)<br>
2. Peer Services<br>
3. RPC<br>
4. Implementations<br>
5. Applications</p>
<p dir=3D"ltr">I posted an example of what such a table might look like her=
e: http://<a href=3D"http://blockhawk.net/bitcoin-dev/bipwiki.html">blockha=
wk.net/bitcoin-dev/bipwiki.html</a></p>
<p dir=3D"ltr">If other folks also think this is a good idea I&#39;ll start=
 working on a BIP draft for this.</p>

--089e011849d4415061051e14ecd2--