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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
Return-Path: <milly@bitcoins.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 757E4ABF
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 12:35:03 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.help.org (mail.help.org [70.90.2.18])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 93469F4
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 12:35:02 +0000 (UTC)
Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA
; Fri, 26 Jun 2015 08:34:58 -0400
References: <COL402-EAS127289185B11D0D58E1F5E6CDAE0@phx.gbl>
<558B7352.90708@bitcoins.info>
<CABm2gDrCxLyxC=BkgiQOjRczy26kQOZb2+p9xDXOh4HuDG8nRw@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
From: Milly Bitcoin <milly@bitcoins.info>
Message-ID: <558D46EC.6050300@bitcoins.info>
Date: Fri, 26 Jun 2015 08:34:52 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <CABm2gDrCxLyxC=BkgiQOjRczy26kQOZb2+p9xDXOh4HuDG8nRw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BIP Process and Votes
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, 26 Jun 2015 12:35:03 -0000
Without looking up specific links I am confident people like Mircea
Popescu will oppose just about any change. Maybe they don't post their
objection to Github but the point I am making is that no matter what
change you make someone, somewhere will be against it. Some of the
developers think that Github is the only place that matters and that the
only opinions that matter is a tiny group of insiders. I don't think
that way which is the reasoning behind my statement.
I am saying that after all the concerns are addressed as far as
reasonably possible someone, somewhere has to decide whether or not to
commit the changes to the official release. Right now the only person
who makes that decision if the version manager. I agree it should not
fall onto the shoulders of one person who is also very busy doing other
things. I am saying there should be some process to move forward and
make decisions when needed.
Also, you already saw one of the Core developers calling me a "troll"
and telling others to ignore my messages. I have heard of several
people who just drop out of the github discussions because of stuff like
that. They also delete message from Gihub discussions so that archive
is not 100% credible. I have seen things like a Github discussion
between 3 or 4 people and then Garzik send out a tweet that there is
near universal approval for the proposed change as it nobody is allowed
to question it. After watching the github process for a couple years I
simply don't trust it because the developers in charge have a
dictatorial style and they shut out many stakeholders instead of
soliciting their opinions. I view the Github system as the biggest
centralized choke-point in Bitcoin and probably its biggest threat to
its continued survival. Anyone can come in and hire a couple core
developers and veto any change they don't want.
Russ
On 6/26/2015 7:13 AM, Jorge Timón wrote:
> On Thu, Jun 25, 2015 at 2:42 PM, Milly Bitcoin <milly@bitcoins.info> wrote:
>> "Cultish" means making claims without any supporting facts.
> On Thu, Jun 25, 2015 at 5:19 AM, Milly Bitcoin <milly@bitcoins.info> wrote:
>> As for developers, the consensus on code changes are almost never 100% and
>> someone has to make the decision about what is an a acceptable consensus.
> This statement seems "cultish" by your own definition.
> I'm going to make the opposite statement: the consensus on code
> changes is almost always 100%.
> Mark has already given a couple examples of changes to consensus rules
> (the most risky type of change), here's a few thousand other examples
> of changes to the bitcoin core's code that had no opposition:
>
> https://github.com/bitcoin/bitcoin/commits/master
>
> Can you please point us to a few examples were changes were made with
> opposition to them?
> In those cases (which you assure is what happens almost always), would
> you say that the result of letting a decider decide instead of fixing
> or addressing all the concerns (either by changing the proposed code
> or explaining it) better in restrospective?
>
|
