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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id AF4BA83D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 10:21:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com
[209.85.214.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 22633144
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 10:21:58 +0000 (UTC)
Received: by obbfr1 with SMTP id fr1so255316obb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 03:21:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=Mr/U1t/YnneuwZdqw/SWkqs4oZP2QO7TFeMkB3Q+M0o=;
b=O4feQMyLdPoTvXjGDcCz4tfwoBux+Ll71TIuIifyeMswxC7kpSPPEE8a+avO44bFI3
G3LIanihxIfd91Vm8wpNR8VEm6lztwkM8nlbWw/sVwTEjYXL1jyttWYQuXsPPStEY3ff
Vcj5eMkPPDqmZgEaigC5DtbTDijMmuj0EwxoCLh4CiIPgyytXMlquYv0dtPPT2Lu2R4Q
cMZPaqOyhSSuyMDQRqZHmpyLa5eMslm+Slmcn8BRCqdCSAsFh1ChIsiYNdCGXzCe4Tg5
Jk8LIP402B1QFshqvV54DlWD2r4EqxP+sL0zN7g01Cy37tebX0SIZfoKqKRNuExCeWhA
LaBw==
X-Gm-Message-State: ALoCoQmbR+qCpHCujnrORg0KrF9Pu88nTskDyZ1QqUHs7d8BxQm1ynCf7coj9AgBSCyuLuXjEbkc
MIME-Version: 1.0
X-Received: by 10.60.76.69 with SMTP id i5mr9849546oew.42.1439979717486; Wed,
19 Aug 2015 03:21:57 -0700 (PDT)
Received: by 10.202.71.85 with HTTP; Wed, 19 Aug 2015 03:21:57 -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 12:21:57 +0200
Message-ID: <CABm2gDq0FEji=cx9gEjoB3zuT8Vykxw6GgqdDv6GyOJjnd6m2w@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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 10:21:58 -0000
On Wed, Aug 19, 2015 at 11:58 AM, Btc Drak <btcdrak@gmail.com> 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/mailma=
n/
>> 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 wo=
uld
> 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 re=
ly
> on it. The mailing list used to be very low volume.
I don't disagree with anything you have said. But I think that having
a list specific to Bitcoin Core development will make defining the
"clear rules" easier.
> While we are at it, we should also think about a bitcoin-announce read on=
ly
> list which consumers of Bitcoin Core can subscribe for announcements abou=
t
> new versions of Bitcoin Core, and any critical warnings. Miners and servi=
ce
> providers would particularly benefit from this. The list is moderated so
> only say Bitcoin Core commit engineers are allowed to post.
Not sure if necessary but not opposed to this either.
>> 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.
As said, that list already exists, it's just that nobody uses it:
http://sourceforge.net/p/bitcoin/mailman/bitcoin-list/
|
