MIME-Version: 1.0
In-Reply-To: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
References: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Wed, 19 Aug 2015 10:58:50 +0100
Message-ID: <CADJgMzsPT7n+favkjHSuWh1YGQPZQAFLyOgxu4wDNwXSa_-3og@mail.gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=001a113938ea0cb370051da71664
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Separated bitcoin-consensus mailing list (was Re:
 Bitcoin XT Fork)
Precedence: list

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

On Wed, Aug 19, 2015 at 9:59 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote:

> Apparently that existed already: http://sourceforge.net/p/bitcoin/mailman=
/
> But technical people run away from noise while non-technical people
> chase them wherever their voices sounds more loud.
>

Regarding disruptors, if there are clear rules about what is acceptable on
-dev, one can simply moderate out offenders. It's absolutely necessary we
have a forum where we can share and discuss purely academic and technical
matters. No-one can accuse censorship because all moderation would say
would be to "take it to the other list". It's essential for all people who
are developing and maintaining Bitcoin protocol software, or services that
rely on it. The mailing list used to be very low volume.

While we are at it, we should also think about a bitcoin-announce read only
list which consumers of Bitcoin Core can subscribe for announcements about
new versions of Bitcoin Core, and any critical warnings. Miners and service
providers would particularly benefit from this. The list is moderated so
only say Bitcoin Core commit engineers are allowed to post.


> One thing that I would like though, is separating Bitcoin
> Core-specific development from general bips and consensus discussions.
>

The potential downside is too much separation becomes confusing although I
would not oppose such a change. My own suggestion would be try just a -dev
and -discuss list and see how that goes first. It used to work well.
Whatever the case I am very confident we need a general discussion mailing
list.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Aug 19, 2015 at 9:59 AM, Jorge Tim=C3=B3n <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Apparently that existed alread=
y: <a href=3D"http://sourceforge.net/p/bitcoin/mailman/" rel=3D"noreferrer"=
 target=3D"_blank">http://sourceforge.net/p/bitcoin/mailman/</a><br>
But technical people run away from noise while non-technical people<br>
chase them wherever their voices sounds more loud.<br></blockquote><div><br=
></div><div>Regarding disruptors, if there are clear rules about what is ac=
ceptable on -dev, one can simply moderate out offenders. It&#39;s absolutel=
y necessary we have a forum where we can share and discuss purely academic =
and technical matters. No-one can accuse censorship because all moderation =
would say would be to &quot;take it to the other list&quot;. It&#39;s essen=
tial for all people who are developing and maintaining Bitcoin protocol sof=
tware, or services that rely on it. The mailing list used to be very low vo=
lume.</div><div><br></div><div>While we are at it, we should also think abo=
ut a bitcoin-announce read only list which consumers of Bitcoin Core can su=
bscribe for announcements about new versions of Bitcoin Core, and any criti=
cal warnings. Miners and service providers would particularly benefit from =
this. The list is moderated so only say Bitcoin Core commit engineers are a=
llowed to post.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One thing that I would like though, is separating Bitcoin<br>
Core-specific development from general bips and consensus discussions.<br><=
/blockquote><div><br></div><div>The potential downside is too much separati=
on becomes confusing although I would not oppose such a change. My own sugg=
estion would be try just a -dev and -discuss list and see how that goes fir=
st. It used to work well. Whatever the case I am very confident we need a g=
eneral discussion mailing list.</div></div><br></div><div class=3D"gmail_ex=
tra"><br></div></div>

--001a113938ea0cb370051da71664--