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
|
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 E8EFB1676
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 29 Sep 2015 15:45:00 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com
[209.85.212.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EC2501D6
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 29 Sep 2015 15:44:58 +0000 (UTC)
Received: by wicgb1 with SMTP id gb1so155301866wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 29 Sep 2015 08:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=DputPZbXUfYeATJCumnWSx2Sj9GWdDINJDgsNhBu3j0=;
b=mO2+URrSJuwQWI5MwEH/W2cb5P4pM+6TTv0zNHKDFz4oyZinT49T2WxmwtBo67Ha5E
l3VZl1r+8PdevHjKmECz9xdf6SE6xjzQtY6rJS7KvD8NsFmhCF0reVe5Bbt9owZTc0De
KdgXHhonEIoZRiOwEEZuTVZHBrFOkAiVk5HCGq0LOLICMOg9YILCiLQqtLNMPNrowJ2I
mkMlevALzSamNTsEQMG5QSy/YYUFNAjsMNK/GWJ7KysRfLPUK8vH6PspfSLu4Ucut3hC
U5DWihvNCFUrVnwXBS2IoO0bghXeGBE1x8OL571FRKD5PAOaX6LCBws2M+qdMFAj8vIz
2f6Q==
MIME-Version: 1.0
X-Received: by 10.180.37.113 with SMTP id x17mr24374879wij.33.1443541497462;
Tue, 29 Sep 2015 08:44:57 -0700 (PDT)
Received: by 10.28.158.9 with HTTP; Tue, 29 Sep 2015 08:44:57 -0700 (PDT)
Date: Tue, 29 Sep 2015 11:44:57 -0400
Message-ID: <CADm_Wcbf+p=ShdfQqKzbWPvVWJ6WMxR2dF4Y4M5N+yzoqZtTCw@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=e89a8f502ef82cc8b00520e4b25f
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
Subject: [bitcoin-dev] On bitcoin-dev list admin and list noise
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: Tue, 29 Sep 2015 15:45:01 -0000
--e89a8f502ef82cc8b00520e4b25f
Content-Type: text/plain; charset=UTF-8
This was discussed in IRC, but (did I miss it?) never made it to the list
outside of being buried in a longer summary.
There is a common complain that bitcoin-dev is too noisy. The response
plan is to narrow the focus of the list to near term technical changes to
the bitcoin protocol and its implementations (bitcoin core, btcd, ...)
Debates over bitcoin philosophy, broader context, etc. will start seeing
grumpy list admins squawk about "off-topic!"
It is a fair criticism, though, that "take it elsewhere!" needs to have
some place as a suggested destination. The proposal is to create a second
list, bitcoin-tech-discuss or perhaps just 'bitcoin', with a more general
rubric. This split has served IRC well and generally manages to keep the
noise down to a productive level. We want this list to achieve that same
goal; if bitcoin-dev is not productive then it's not useful.
--e89a8f502ef82cc8b00520e4b25f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">This was discussed in IRC, but (did I miss it?) never made=
it to the list outside of being buried in a longer summary.<div><br></div>=
<div>There is a common complain that bitcoin-dev is too noisy.=C2=A0 The re=
sponse plan is to narrow the focus of the list to near term technical chang=
es to the bitcoin protocol and its implementations (bitcoin core, btcd, ...=
)</div><div><br></div><div>Debates over bitcoin philosophy, broader context=
, etc. will start seeing grumpy list admins squawk about "off-topic!&q=
uot;</div><div><br></div><div>It is a fair criticism, though, that "ta=
ke it elsewhere!" needs to have some place as a suggested destination.=
=C2=A0 The proposal is to create a second list, bitcoin-tech-discuss or per=
haps just 'bitcoin', with a more general rubric.=C2=A0 This split h=
as served IRC well and generally manages to keep the noise down to a produc=
tive level.=C2=A0 We want this list to achieve that same goal; if bitcoin-d=
ev is not productive then it's not useful.</div><div><br></div><div><br=
></div></div>
--e89a8f502ef82cc8b00520e4b25f--
|
