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
|
Return-Path: <luke@dashjr.org>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
by lists.linuxfoundation.org (Postfix) with ESMTP id BC99DC000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 25 Apr 2021 21:01:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id AB4E4606AE
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 25 Apr 2021 21:01:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level:
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001,
RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=dashjr.org
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ZoyHki-uwYON
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 25 Apr 2021 21:01:01 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from zinan.dashjr.org (zinan.dashjr.org [IPv6:2001:470:88ff:2f::1])
by smtp3.osuosl.org (Postfix) with ESMTP id 6FDFD60636
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 25 Apr 2021 21:01:00 +0000 (UTC)
Received: from ishibashi.lan (unknown [12.153.231.213])
(Authenticated sender: luke-jr)
by zinan.dashjr.org (Postfix) with ESMTPSA id CA90138A0019;
Sun, 25 Apr 2021 21:00:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dashjr.org; s=zinan;
t=1619384456; bh=JxE+WbGpHr+V9toTZ5TcDb8sLX0/ucC20Oj4KBYAQyU=;
h=From:To:Subject:Date:Cc:References:In-Reply-To;
b=XJH07RnVrB/kme7imfogBbLkKetaclE5z6PJY8NGV+YUA4SWFRWyXhh0kz4QxqnWW
9MQCaDnR1pJz9EmnOpXAgpVPnDADOD7BVZWRumhny6AOCDBz8HhebbguPCwnLZ1n22
zLDUqgJR6yt87soPm50v+fGPm6OwUrfrN9SG133w=
X-Hashcash: 1:25:210425:lf-lists@mattcorallo.com::r0nxcEQUl=8DXFag:aFffY
X-Hashcash: 1:25:210425:antoine.riard@gmail.com::i/W7I9+WNp8K9d4F:V6PT
X-Hashcash: 1:25:210425:bitcoin-dev@lists.linuxfoundation.org::E0WhEKGu7gePDKNH:n5+Q
X-Hashcash: 1:25:210425:karljohan-alm@garage.co.jp::z17RU9TQM8OlGcY9:auAMj
From: Luke Dashjr <luke@dashjr.org>
To: Matt Corallo <lf-lists@mattcorallo.com>
Date: Sun, 25 Apr 2021 21:00:06 +0000
User-Agent: KMail/1.9.10
References: <202104230209.05373.luke@dashjr.org>
<CALZpt+Hz3jFnA8z1w6yictdHWnnKReMK+6eEHg_jUZ7==xNZzQ@mail.gmail.com>
<64807e52-14ea-198b-4caf-29be92e89655@mattcorallo.com>
In-Reply-To: <64807e52-14ea-198b-4caf-29be92e89655@mattcorallo.com>
X-KMail-QuotePrefix: >
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <202104252100.07296.luke@dashjr.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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: Sun, 25 Apr 2021 21:01:01 -0000
On Sunday 25 April 2021 20:29:44 Matt Corallo wrote:
> If the BIP editor is deliberately refusing to accept changes which the
> author's approval (which appears to be occurring here),
It isn't. I am triaging BIPs PRs the same as I have for years, and will get to
them all in due time, likely before the end of the month.
Rather, what we have going on is a few bad actors trying to misportray the
BIPs as an approval process so they can pretend ST is somehow official, or
that the preexisting Core+Taproot client is "breaking" the spec. And to
further their agenda, they have been harassing me demanding special
treatment.
I will not become an accomplice to this deception by giving special treatment,
and will process the BIP PR neutrally according to the currently-defined BIP
process.
Despite the continual harassment, I have even made two efforts to try to
(fairly) make things faster, and have been obstructed both times by ST
advocates. It appears they intend to paint me as "deliberately refusing" (to
use your words) in order to try to put Bitcoin and the BIP process under
their control, and abuse it in the same manner in which they abused Bitcoin
Core's usual standards (by releasing ST without community consensus).
Luke
|
