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
|
Return-Path: <truthcoin@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 23FE2B2A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Jul 2017 22:04:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f173.google.com (mail-qk0-f173.google.com
[209.85.220.173])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A64FC171
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Jul 2017 22:04:50 +0000 (UTC)
Received: by mail-qk0-f173.google.com with SMTP id p73so2512564qka.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 17 Jul 2017 15:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-transfer-encoding:content-language;
bh=LoPjg4BqdPDlCYtONP7rm6CmsL9qusKt+ZTpibTut8o=;
b=MmEzKX97gYbCKK+oEnYQpUKoZnmT1Uf7qttRxc0/BuSxOYjL7w1srvqBPLY1WquKua
s35ZsZmrcCRe+RDwLNxlvjAMTDSvcVkSz1Ou9idQhoDAz8gNcy8kHaR+Hmy42uUJQWhg
rHTHqoZ+b73JivxaphoVwByhDE8kHDxUlIGO0aa7r8v0m75XrdwklMVzwoiTRpIrjdgc
hIl2j5vibe59l1Kj00xr69K1U+PfZfX99eOW0mwqtpBukQ56WU9okVueAy8Jqro8Gs4E
xVSMDrnF0dgaLKxggmt0TwWU0yonqg1phIoO/3f8RcJzOonp6evlIGZMSqwlrNtvxmtF
mcTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding
:content-language;
bh=LoPjg4BqdPDlCYtONP7rm6CmsL9qusKt+ZTpibTut8o=;
b=iSa/C/sSGMGFBChKvkbivdxSXa4AS5RZZmoa+ZYnRN9xutI1QUTGrTqCfnbjh6W28N
P9tw9tQmOQl9KDTY7ncgWgy3ANIKT9p3OhFPMv5K+aY8lieBXx6wachiKoSrcBZIcvel
Y0xJVxCQc6n9gurJfZeEkaPSdD7pOE/j1Jiyj1q0v6IbdG5LJ7/WhSO2j6fZamNH4ld+
RzLxoDC/hGrDtFmGg3eGBKvqESOLaPZxyVTTG7mrs93WzDDVPfjaHYnrNSXSile4Vm0i
doSni5Iqc6Gq6jKuo26Rhcy0Q1kyO8RBN7L2hRkxNvwSgC8rn3MPieUltDwQf+6ufpBn
rB5g==
X-Gm-Message-State: AIVw111hnbEhd525qafouwNeJdnT9DTEkTcdwBbHyg6DyLzXE+RCI0TJ
RV0Ixj0X6ycD7Mv8
X-Received: by 10.233.220.195 with SMTP id q186mr28415608qkf.244.1500329089475;
Mon, 17 Jul 2017 15:04:49 -0700 (PDT)
Received: from [192.168.1.100] (ool-45726efb.dyn.optonline.net.
[69.114.110.251]) by smtp.googlemail.com with ESMTPSA id
k138sm292506qke.41.2017.07.17.15.04.48
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 17 Jul 2017 15:04:48 -0700 (PDT)
To: "David A. Harding" <dave@dtrt.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <0119661e-a11a-6d4b-c9ec-fd510bd4f144@gmail.com>
<01194110-04f0-82f5-cd5e-0101822fa2b1@gmail.com>
<20170717214704.ksegcrdqf3zeslah@fedora-23-dvm>
From: Paul Sztorc <truthcoin@gmail.com>
Message-ID: <292fa654-30e8-b55f-fbb6-7d47c3f08789@gmail.com>
Date: Mon, 17 Jul 2017 18:04:49 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170717214704.ksegcrdqf3zeslah@fedora-23-dvm>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 18 Jul 2017 02:34:45 +0000
Subject: Re: [bitcoin-dev] Updating the Scaling Roadmap [Update]
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: Mon, 17 Jul 2017 22:04:51 -0000
On 7/17/2017 5:47 PM, David A. Harding wrote:
> On Mon, Jul 17, 2017 at 01:13:30PM -0400, Paul Sztorc via bitcoin-dev w=
rote:
>> However, without interest from the maintainers of bitcoincore.org
>> (specifically these [3, 4] pages and similar) the document will probab=
ly
>> be unable to gain traction.
>> [...]
>> [3] https://bitcoincore.org/en/2015/12/21/capacity-increase/
>> [4] https://bitcoincore.org/en/2015/12/23/capacity-increases-faq/
> The BitcoinCore.org maintainers are not psychic. If you want your
> document to appear on the website, please open a PR. If you would like=
> help formatting your document for the website, please feel free to send=
> me an email off list or open an issue[1] regarding the inadequacy of
> the site's readme.
I meant only to convey that the document would appear on bitcoincore.org
iff the PR were ultimately accepted. In other words, while it is up to
"the community of Core Contributors" in a philosophical sense, it is up
to the maintainers of BitcoinCore.org in a practical sense, because they
are the ones who ultimately decide if the standard has been met.
I think it is perfectly reasonable to keep site-updates narrowly
organized in the GitHub PR sphere (and to ignore everything else).
> [1] https://github.com/bitcoin-core/bitcoincore.org/issues/new
>
> Speaking as the instigator of [3] and the primary author of [4] (both
> originally published on Bitcoin.org), I'll point out that Maxwell's
> reply to you was a slightly rewritten version of a reply to me sent on =
4
> November 2016 (as noted elsewhere in the thread and confirmed in my
> mailbox). I include below my signature a complete copy of my reply to
> him (and CC'd to others).
>
> If I had followed through on my earlier plan to post a copy of Maxwell'=
s
> reply on BitcoinCore.org (assuming Bitcoin Core contributors supported
> publishing it), you probably would've known that some Bitcoin Core
> contributors were resistant to roadmaps prior to you writing your
> proposed roadmap. For that failure, and the time you may have wasted
> because of it, I offer you my apologies.
I appreciate you saying that. Thank you.
-Paul
> I will make opening a PR to BitcoinCore.org with his statement a priori=
ty=20
> so that hopefully future confusion can be avoided.
>
> Sincerely,
>
> -Dave
>
> On Fri, Nov 04, 2016 at 07:17:11PM +0000, Gregory Maxwell wrote:
>> [...]
> I just wanted to say that I thought this was an amazing reply. I was
> hoping that if I waited long enough to respond I might find something
> meaningful to add, but nothing has come to mind and I didn't want to
> leave the impression that your reply didn't merit a response.
>
> Maybe we can find a place on the website to post something like this so=
> that we can link to it when other people ask for roadmaps and other
> commitments to future plans.
>
> Thanks!,
>
> -Dave
|
