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
|
Return-Path: <karljohan-alm@garage.co.jp>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id F3CAFAB2
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 01:23:27 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 657F41B4
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 01:23:27 +0000 (UTC)
Received: from ip-10-217-1-36.ap-northeast-1.compute.internal
(localhost.localdomain [127.0.0.1])
by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id D2A4214C0C1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 10:23:25 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1)
by 0 with SMTP; 12 Jul 2017 10:23:25 +0900
X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1])
by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id C61BE4C03C
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 10:23:25 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
Received: from gw31.oz.hdemail.jp
(ip-10-173-133-236.ap-northeast-1.compute.internal [10.173.133.236])
by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id C321D14C0C1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 10:23:25 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
X-Durian-MailFrom: karljohan-alm@garage.co.jp
X-Durian-RcptTo: bitcoin-dev@lists.linuxfoundation.org
Received: from gw31.oz.hdemail.jp (gw31.oz.hdemail.jp [127.0.0.1])
by gw31.oz.hdemail.jp (gw31.oz.hdemail.jp [127.0.0.1]);
Wed, 12 Jul 2017 10:23:22 +0900
X-Received: from mail-qt0-f198.google.com (lb1.oz.lo.hdemail.jp
[54.248.222.53])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(No client certificate requested)
by gw31.oz.hdemail.jp (Postfix) with ESMTP id 2026D148C12D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 12 Jul 2017 10:23:22 +0900 (JST)
X-Received: by mail-qt0-f198.google.com with SMTP id o8so4368298qtc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Jul 2017 18:23:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=Zmi65gYAELnk4DuAP99xv85OiKkkHQUR1BVwTQlehX8=;
b=bDMN8G33xNImMBWlhTke/NgpQuNqrzbMYDt5u4kPkN7KgPV6WUCuP97cSm8b9LksSz
sLSYOZOQp1qztsQBC6MbuvFPBR/WVzFgZ3CUYsQy2yktMI58P81qK7ItgsNa5vAx6kmE
17X2//DLCfpNCohGRLrztqoysgDVfdN+pu0I8GDFz5/eJehLVHGKFVM3UVtMKwnzW/tB
scEe6pCo+L45W5C2zDaHXzJsvZh0NtbnGkLanpkTiRFVfU4cRe50XYcM3cZV6l+jzj0r
Q01iTRuXmWqgqhobKd1jx3Om7HeDTkwdgC2IeChDRFbQMjp/dQwGBPYUuQfSge6u65e6
4lHA==
X-Gm-Message-State: AIVw110Kff/6EoMwu/IyK2U1jbnANN4UqC44yDbKc9/M6Wa93hBTe/8L
ij4d19jM6b8bLALQS2FvZ9+X1SZ+mF6JizaWOzfxEnm2S8NTuKkhsx+Ao9dMtf5EF7SBDhyqbPd
vCsXJprjLgMDkntI7sArt0P8ESHg7CqIYWBIcfURK6MdMLg==
X-Received: by 10.237.56.40 with SMTP id j37mr3494484qte.45.1499822600077;
Tue, 11 Jul 2017 18:23:20 -0700 (PDT)
X-Received: by 10.237.56.40 with SMTP id j37mr3494469qte.45.1499822599814;
Tue, 11 Jul 2017 18:23:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.12.146.47 with HTTP; Tue, 11 Jul 2017 18:22:59 -0700 (PDT)
In-Reply-To: <CAAS2fgRDVgdMYZo776iLwbm23aGNDWL85YgD=yF=M-0_vqJ5nQ@mail.gmail.com>
References: <0119661e-a11a-6d4b-c9ec-fd510bd4f144@gmail.com>
<CAAS2fgRDVgdMYZo776iLwbm23aGNDWL85YgD=yF=M-0_vqJ5nQ@mail.gmail.com>
From: Karl Johan Alm <karljohan-alm@garage.co.jp>
Date: Wed, 12 Jul 2017 10:22:59 +0900
Message-ID: <CALJw2w5uh8y1EMJdJVDhuFs3NG7LeM8T5HzfLHp8kXN15ryrXw@mail.gmail.com>
To: Gregory Maxwell <greg@xiph.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Wed, 12 Jul 2017 01:26:57 +0000
Subject: Re: [bitcoin-dev] Updating the Scaling Roadmap
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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, 12 Jul 2017 01:23:28 -0000
On Wed, Jul 12, 2017 at 6:11 AM, Gregory Maxwell via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> IMO the way to do "roadmaps" in Bitcoin is to roadmap the finalization
> and release process once the basic technology is done; because it's
> only past that point that guarantees can really start being made.
Bitcoin development differs from Linux kernel development in a number
of obvious ways, such as the fact Bitcoin is being "patched in
flight". The current political situation over Bitcoin development is
also quite different, with scalability being a major concern for a lot
of users, and conflicting views leading to risky technical gambles.
Having *something* like a roadmap that gives the average user some
insights into what exactly is being planned for Bitcoin is very
desirable, arguably even necessary, in particular for the scaling
solutions. Putting deadlines and dates in would of course be highly
irresponsible, as no one can predict how much of their free time
volunteer developers will put into the project in advance (or whether
they will stick around for the next X months or stop being
contributors).
I think there is necessity for a document that describes the project
intentions for scaling solutions, but I don't think adding dates and
deadlines is appropriate. That may or may not be a roadmap. I imagine
such a document would be updated regularly as appropriate, which means
it may be less of a roadmap than the traditional kind.
|
