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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Z5bCR-0001nn-QL
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 14:53:51 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.218.49 as permitted sender)
client-ip=209.85.218.49; envelope-from=jgarzik@bitpay.com;
helo=mail-oi0-f49.google.com;
Received: from mail-oi0-f49.google.com ([209.85.218.49])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5bCQ-0007mQ-Qi
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 14:53:51 +0000
Received: by oigb199 with SMTP id b199so17593486oig.3
for <bitcoin-development@lists.sourceforge.net>;
Thu, 18 Jun 2015 07:53:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=5EddLIXYz2WFbCyy4BeGvjMoihNtmjYYnVI6aLawoLY=;
b=lwA+9V0lGopl1OoGorcVgpvffqkBJhz7kdhPe0OOzQJ4jKxqiz2sKWVyfMa3oF1aXp
UbeEcHgeT49+szDRv9s/kyyvEBVTdE9fMmdEH2DBtSc0fHN0Dh6dSnH38srgNTkGjzbZ
ELlXDRfBhIIc3eGdghJFc6EC8z0eJgN4zFRtfnIWH5A4fEZq7C045HnKf4he6cWSQ6Tr
N5enb8vM1x8pdBqPJ18lminb67PN0ZxQYx2FcDSKPPu2grs+7Rye7VT37cCZIvgWq2dR
CGFQuc4bXEIwK4SKhF8rrnP9+Q4MdYYMba1hqFnaoUv6+8buYJWjFoJAdv0ZgzAK9+JF
GHsg==
X-Gm-Message-State: ALoCoQm5b2FhoG9yRiT+bjolHQlwRNGkUNG6yZYci76MG6lNkQ/KcHsk31hnLji2gPi9LKr3mhO3
X-Received: by 10.202.55.7 with SMTP id e7mr8873266oia.56.1434639225383; Thu,
18 Jun 2015 07:53:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.108.149 with HTTP; Thu, 18 Jun 2015 07:53:24 -0700 (PDT)
In-Reply-To: <CAPg+sBj_go==m6-++sA53imYdz4OLH4bkyiuAyEM8YR8CaTd=w@mail.gmail.com>
References: <55828737.6000007@riseup.net>
<CANEZrP3M7+BsZKLFZV-0A_fC7NmMGbTDxsx3ywru3dSW78ZskQ@mail.gmail.com>
<20150618111407.GA6690@amethyst.visucore.com>
<CAPg+sBj_go==m6-++sA53imYdz4OLH4bkyiuAyEM8YR8CaTd=w@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Thu, 18 Jun 2015 10:53:24 -0400
Message-ID: <CAJHLa0OKXaUD6MnN4N6RGbNwrXx43jBm9MiELQK6BRw1OL3HNA@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=001a113cea266910820518cbf9a9
X-Spam-Score: 1.1 (+)
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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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
1.7 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1Z5bCQ-0007mQ-Qi
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
to Remove Commit Access from Other Developers
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: Thu, 18 Jun 2015 14:53:51 -0000
--001a113cea266910820518cbf9a9
Content-Type: text/plain; charset=UTF-8
On Thu, Jun 18, 2015 at 8:29 AM, Pieter Wuille <pieter.wuille@gmail.com>
wrote:
> On Thu, Jun 18, 2015 at 1:14 PM, Wladimir J. van der Laan <
> laanwj@gmail.com> wrote:
>
>> Like in any open source project there is lots of decision making ability
>> for code changes. I'd say look at the changelog for e.g. 0.11
>> https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log,
>> or follow pull requests for a while, to see how many decisions about
>> changes are made from day to day. No, I'm not sitting on my hands, and so
>> is none of the other contributors that you'd like to get rid of.
>>
>
> The analogy goes further even. Even though I disagree with some of the
> changes you're making, I respect Mike's (and anyone's) right to make a fork
> of Bitcoin Core. That's how open source works: if people disagree with
> changes made or not made, they can maintain their own version. However:
>
>
>> Consensus changes are *much* more difficult, on the other hand. Even
>> relatively straightforward softforks come with a long discussion process
>> (see BIP62, BIP66). A hardfork is hard to do at the best of times (everyone
>> needs to upgrade their software!), and simply not possible if almost the
>> entire technical community disagrees with you.
>>
>
> Consensus changes - in particular hardforks - are not about making a
> change to the software. You are effectively asking users of the system to
> migrate to a new system. Perhaps one which is a philosophical successor to
> the old one, but a different system, with new rules that are incompatible
> with the old one.
>
Indeed. I think Mike is glossing over this major facet.
Consensus changes - worded another way - change Bitcoin's Constitution -
The Rules that everyone in the system is -forced- to follow, or be ignored
by the system.
Changing bitcoin's rules IS IN NO WAY like Wikipedia or other open source
software.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--001a113cea266910820518cbf9a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jun 18, 2015 at 8:29 AM, Pieter Wuille <span dir=3D"ltr"><<a=
href=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gm=
ail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"ltr"><span class=3D"">On Thu, Jun 18, 2015 at 1:14 PM, Wladimir J. van der=
Laan <span dir=3D"ltr"><<a href=3D"mailto:laanwj@gmail.com" target=3D"_=
blank">laanwj@gmail.com</a>></span> wrote:<br></span><div class=3D"gmail=
_extra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">Like in any open source project there is lots of decision making ab=
ility for code changes. I'd say look at the changelog for e.g. 0.11 <a =
href=3D"https://github.com/bitcoin/bitcoin/blob/0.11/doc/release-notes.md#0=
110-change-log" rel=3D"noreferrer" target=3D"_blank">https://github.com/bit=
coin/bitcoin/blob/0.11/doc/release-notes.md#0110-change-log</a>, or follow =
pull requests for a while, to see how many decisions about changes are made=
from day to day. No, I'm not sitting on my hands, and so is none of th=
e other contributors that you'd like to get rid of.<br></blockquote><di=
v><br></div></span><div>The analogy goes further even. Even though I disagr=
ee with some of the changes you're making, I respect Mike's (and an=
yone's) right to make a fork of Bitcoin Core. That's how open sourc=
e works: if people disagree with changes made or not made, they can maintai=
n their own version. However:<br></div><span class=3D""><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
Consensus changes are *much* more difficult, on the other hand. Even relati=
vely straightforward softforks come with a long discussion process (see BIP=
62, BIP66). A hardfork is hard to do at the best of times (everyone needs t=
o upgrade their software!), and simply not possible if almost the entire te=
chnical community disagrees with you.<br></blockquote><div><br></div></span=
><div>Consensus changes - in particular hardforks - are not about making a =
change to the software. You are effectively asking users of the system to m=
igrate to a new system. Perhaps one which is a philosophical successor to t=
he old one, but a different system, with new rules that are incompatible wi=
th the old one.</div></div></div></div></blockquote><div><br></div><div>Ind=
eed.=C2=A0 I think Mike is glossing over this major facet.</div><div><br></=
div><div>Consensus changes - worded another way - change Bitcoin's Cons=
titution - The Rules that everyone in the system is -forced- to follow, or =
be ignored by the system.</div><div><br></div><div>Changing bitcoin's r=
ules IS IN NO WAY like Wikipedia or other open source software.</div></div>=
<div><br></div>-- <br><div class=3D"gmail_signature">Jeff Garzik<br>Bitcoin=
core developer and open source evangelist<br>BitPay, Inc. =C2=A0 =C2=A0 =
=C2=A0<a href=3D"https://bitpay.com/" target=3D"_blank">https://bitpay.com/=
</a></div>
</div></div>
--001a113cea266910820518cbf9a9--
|
