MIME-Version: 1.0
From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
Date: Mon, 5 Oct 2015 12:56:33 -0300
Message-ID: <CAKzdR-rPoByn=+CgsTc1ZnLkjwtYyJnbQLbn-VHOvz0dLciefQ@mail.gmail.com>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a113d59aa0d04bf05215d913a
Subject: [bitcoin-dev] This thread is not about the soft/hard fork technical
	debate
Precedence: list

--001a113d59aa0d04bf05215d913a
Content-Type: text/plain; charset=UTF-8

Some of the people on this mailing list are blindly discussing the
technicalities of a soft/hard fork without realizing that is not Mike's
main intention. At least I perceive (and maybe others too) something else
is happening.

Let me try to clarify: the discussion has nothing to do with technical
arguments. I generally like more hard forks than soft forks (but I won't
explain why because this is not a technical thread), but for CLTV this is
quite irrelevant (but I won't explain why..), and I want CLTV to be
deployed asap.

Mike's intention is to criticize the informal governance model of Bitcoin
Core development and he has strategically pushed the discussion to a
dead-end where the group either:

1) ignores him, which is against the established criteria that all
technical objections coming from anyone must be addressed until that person
agrees, so that a change can be uncontroversial. If the group moves forward
with the change, then the "uncontroversial" criteria is violated and then
credibility is lost. So a new governance model would be required for which
the change is within the established rules.

2) respond to his technical objections one after the other, on never ending
threads, bringing the project to a standstill.

As I don't want 2) to happen, then 1) must happen, which is what Mike
wants. I have nothing for or against Mike personally. I just think Mike
Hearn has won this battle. But having a more formal decision making process
may not be too bad for Bitcoin, maybe it can actually be good.

Best regards
 from a non-developer to my dearest developer friends,
  Sergio.

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

<div dir=3D"ltr">Some of the people on this mailing list are blindly discus=
sing the technicalities of a soft/hard fork without realizing that is not M=
ike&#39;s main intention. At least I perceive (and maybe others too) someth=
ing else is happening.<div><br><div>Let me try to clarify: the discussion h=
as nothing to do with technical arguments. I generally like more hard forks=
 than soft forks (but I won&#39;t explain why because this is not a technic=
al thread), but for CLTV this is quite irrelevant (but I won&#39;t explain =
why..), and I want CLTV to be deployed asap.</div><div><br></div><div><div>=
Mike&#39;s intention is to criticize the informal governance model of Bitco=
in Core development and he has strategically pushed the discussion to a dea=
d-end where the group either:</div><div><br></div><div>1) ignores him, whic=
h is against the established criteria that all technical objections coming =
from anyone must be addressed until that person agrees, so that a change ca=
n be uncontroversial. If the group moves forward with the change, then the =
&quot;uncontroversial&quot; criteria is violated and then credibility is lo=
st. So a new governance model would be required for which the change is wit=
hin the established rules.</div><div><br></div><div>2) respond to his techn=
ical objections one after the other, on never ending threads, bringing the =
project to a standstill.</div><div><br></div><div>As I don&#39;t want 2) to=
 happen, then 1) must happen, which is what Mike wants. I have nothing for =
or against Mike personally. I just think Mike Hearn has won this battle. Bu=
t having a more formal decision making process may not be too bad for Bitco=
in, maybe it can actually be good.</div><div><br></div><div>Best regards=C2=
=A0</div><div>=C2=A0from a non-developer to my dearest developer friends,</=
div><div>=C2=A0 Sergio.<br><div><br></div></div></div></div></div>

--001a113d59aa0d04bf05215d913a--