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
|
Return-Path: <kanzure@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7839010E1
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 00:43:16 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com
[209.85.223.175])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0516E13A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 4 Sep 2015 00:43:15 +0000 (UTC)
Received: by ioiz6 with SMTP id z6so7046972ioi.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 03 Sep 2015 17:43:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=zAy8nwuiUHqCJGGgDSGkH6otidWfX48/0khSZbJB6YM=;
b=zVKSSVgeBySSBolsL5ImhP8+LnSFhmTZVb8fPgpMmwvR2TjpN9HUbfnEQzkfvP9EoC
AgBxKd2dp54TLiZy0OjujejNxAM6j8C6sZ7MSWr0PuJvCIBT64nZRnL4SWmbYVVMdMU1
mjBJ8gjy8XJWyY+WdoyInSaNvV1jAoEUGfc7AvXLEDavS/W8dy++PAfge288xPtnZkMN
+H07TXc1bRCXC6+HOxjc1ab5bKKDYHuRjOFrr80aj5/8q2bP+iU4U7lugtZEYj685Bwn
YbC0Ej0Lnw6k3XFA6gMIa3xqsedOAc4z7nXP/XIrRBUUfUHsT1dJ2mftLa4BSfdDIUm3
D3jg==
MIME-Version: 1.0
X-Received: by 10.107.30.13 with SMTP id e13mr1709940ioe.57.1441327395416;
Thu, 03 Sep 2015 17:43:15 -0700 (PDT)
Received: by 10.36.19.141 with HTTP; Thu, 3 Sep 2015 17:43:15 -0700 (PDT)
In-Reply-To: <64B72DF6-BE37-4624-ADAA-CE28C14A4227@gmail.com>
References: <64B72DF6-BE37-4624-ADAA-CE28C14A4227@gmail.com>
Date: Thu, 3 Sep 2015 19:43:15 -0500
Message-ID: <CABaSBaw7hM2qmuR6Z6USy5=V9NGeCPKmHHuVOH=vexDk7kY8OA@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: Andy Chase <theandychase@gmail.com>, Bryan Bishop <kanzure@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP/Draft] BIP Acceptance Process
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: Fri, 04 Sep 2015 00:43:16 -0000
On Thu, Sep 3, 2015 at 7:30 PM, Andy Chase via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> I wrote the BIP mostly to stir the pot on ideas of governance
Some quick comments:
I have some objects that I am not ready to put into words, but I do
think there are easily some major objections to committee design. If I
vanish and never respond with my objections, perhaps there's an IETF
RFC about this already....
Something that may mitigate my possible objections would be some
mandatory requirement about ecosystem echo-chambers making many
attempts and efforts at steelman representations of alternative
viewpoints. Understanding objections at a fundamental level, enough to
make strong steelman statements, is very important to ensure that the
competing opinions are not censored from consideration. Pathological
integration and internalization of these steelman arguments can be
very useful, even if the process looks unusual.
Your process does not have to replace any particular BIP process
as-is, but rather could be an alternative that proceeds on its own
perhaps indefinitely without replacement. I don't think too many BIP
processes are necessarily incompatible except by namespace collision.
https://gist.github.com/andychase/dddb83c294295879308b#gistcomment-1566432
- Bryan
http://heybryan.org/
1 512 203 0507
|
