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
|
Return-Path: <jgarzik@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 417839CA
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 14:20:28 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BD9B413D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 14:20:26 +0000 (UTC)
Received: by wicja10 with SMTP id ja10so9883275wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 07:20:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=Dppm3DaTAjITVRfjScs1Ts0vmRsJ/1jZJn28z0yNsU0=;
b=g5U6HRwh48cxazzgZjtMoq2ETG85Q0HG3VEXeaXQTQheKogl9GtKzFnSN9Qont17Sk
TWjVwSQTt1JPMpjWVvBvLyEPBu9FHyKX29c6jb4N0XrxxBBi97XTbhXdD7tElfXOIPbx
qde6qh0G3u11xhKEQlYVk5bk2TAfujgWZgQ4ueKkNJPhyJE9rpvBj3g8EmCn1AJ+mJPQ
eUcjJWcOLrJXXlAnFP4BcfOaCQ1XwiB3vwAsjYaSFcK4GzgIfMhBkEUqW8B5DICmHdeR
D3zN4cjcVquQ5wWwyzitEO5gCNj8TYCMuLDiqZFXvaFV7iB1TWVhSbRc4IhbUhBIzTRG
BmRQ==
MIME-Version: 1.0
X-Received: by 10.194.238.39 with SMTP id vh7mr23422953wjc.109.1439994025478;
Wed, 19 Aug 2015 07:20:25 -0700 (PDT)
Received: by 10.28.52.84 with HTTP; Wed, 19 Aug 2015 07:20:25 -0700 (PDT)
In-Reply-To: <CADJgMzsPT7n+favkjHSuWh1YGQPZQAFLyOgxu4wDNwXSa_-3og@mail.gmail.com>
References: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
<CADJgMzsPT7n+favkjHSuWh1YGQPZQAFLyOgxu4wDNwXSa_-3og@mail.gmail.com>
Date: Wed, 19 Aug 2015 10:20:25 -0400
Message-ID: <CADm_WcYdWyeVhfvzbW=smqinCupTEvf7sz=ctU4ht+LssM3=Tw@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: multipart/alternative; boundary=089e0141aa1a5e0f88051daabc9a
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham 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 14:20:28 -0000
--089e0141aa1a5e0f88051daabc9a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
bitcoin-dev for protocol discussion and bitcoin-core for Bitcoin Core
discussion?
As Jorge notes, a general discussion list has existed for a long time with
little use.
On Wed, Aug 19, 2015 at 5:58 AM, Btc Drak via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Wed, Aug 19, 2015 at 9:59 AM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrot=
e:
>
>> 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 o=
n
> -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 wh=
o
> are developing and maintaining Bitcoin protocol software, or services tha=
t
> 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 -de=
v
> 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 mailin=
g
> list.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--089e0141aa1a5e0f88051daabc9a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">bitcoin-dev for protocol discussion and bitcoin-core for B=
itcoin Core discussion?<div><br></div><div>As Jorge notes, a general discus=
sion list has existed for a long time with little use.</div><div><br></div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Aug=
19, 2015 at 5:58 AM, Btc Drak via bitcoin-dev <span dir=3D"ltr"><<a hre=
f=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoi=
n-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gma=
il_quote"><span class=3D"">On Wed, Aug 19, 2015 at 9:59 AM, Jorge Tim=C3=B3=
n <span dir=3D"ltr"><<a href=3D"mailto:jtimon@jtimon.cc" target=3D"_blan=
k">jtimon@jtimon.cc</a>></span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>Apparently that existed already: <a href=3D"http://sourceforge.net/p/bitco=
in/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></span><div>Regarding disruptors, if there are clear rules about wha=
t is acceptable on -dev, one can simply moderate out offenders. It's ab=
solutely necessary we have a forum where we can share and discuss purely ac=
ademic and technical matters. No-one can accuse censorship because all mode=
ration would say would be to "take it to the other list". It'=
s essential for all people who are developing and maintaining Bitcoin proto=
col software, or services that rely on it. The mailing list used to be very=
low volume.</div><div><br></div><div>While we are at it, we should also th=
ink about a bitcoin-announce read only list which consumers of Bitcoin Core=
can subscribe for announcements about new versions of Bitcoin Core, and an=
y critical warnings. Miners and service providers would particularly benefi=
t from this. The list is moderated so only say Bitcoin Core commit engineer=
s are allowed to post.=C2=A0</div><span class=3D""><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" 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></span><div>The potential downside is too much s=
eparation becomes confusing although I would not oppose such a change. My o=
wn suggestion would be try just a -dev and -discuss list and see how that g=
oes first. It used to work well. Whatever the case I am very confident we n=
eed a general discussion mailing list.</div></div><br></div><div class=3D"g=
mail_extra"><br></div></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>
--089e0141aa1a5e0f88051daabc9a--
|
