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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B9BE97AA
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 09:59:11 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f180.google.com (mail-yk0-f180.google.com
[209.85.160.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 15AF5112
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 09:59:11 +0000 (UTC)
Received: by ykll84 with SMTP id l84so122157813ykl.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 02:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=u3dUJ9540Pc/krDbL7UWVsGq/iTScPBBeyLG610ju3w=;
b=gW+LL06QYqaqKSs+pqhnCZGe4I+TDPoJbiQm1hwPzhYiRwuoFniOUDp/oEC6euL7T1
FrJIs26ZWQN/DhkwOmZAOHF0qHlulfye7T+pofi8p4lojO45wqWo5h0F01+DB/p3igit
zfx5Gtb3d0xx/Uj2dByOO47vY9qju069fWNFKY/uKveMH5PH5C4HWC0xXMnRNImsoCUt
mWVaxBW8YrpFLcMp3uRLsI0ElDJpp2/hl0R4x6U4EckZgOdYY4GKdhzvTDI6D2rTYi70
GwbIJ1lnyTkUpi2oazJ1HeBEKUMYj0boYigge+51G026Og2OJBhbhYnNnrJq0deP2/P4
mVfA==
X-Received: by 10.170.52.205 with SMTP id 196mr12425783yku.81.1439978350226;
Wed, 19 Aug 2015 02:59:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.94.132 with HTTP; Wed, 19 Aug 2015 02:58:50 -0700 (PDT)
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
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=no 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] Separated bitcoin-consensus mailing list (was Re:
Bitcoin XT Fork)
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: Wed, 19 Aug 2015 09:59:11 -0000
--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"><<a href=
=3D"mailto:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>></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'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 "take it to the other list". It'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--
|
