From: Luke Dashjr <luke@dashjr•org>
To: Matt Corallo <lf-lists@mattcorallo•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Reminder on the Purpose of BIPs
Date: Sun, 25 Apr 2021 21:00:06 +0000 [thread overview]
Message-ID: <202104252100.07296.luke@dashjr.org> (raw)
In-Reply-To: <64807e52-14ea-198b-4caf-29be92e89655@mattcorallo.com>
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
next prev parent reply other threads:[~2021-04-25 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 2:09 [bitcoin-dev] Proposed BIP editor: Kalle Alm Luke Dashjr
2021-04-23 3:36 ` Jeremy
2021-04-23 7:49 ` John Newbery
2021-04-23 7:50 ` Pindar Wong
2021-04-23 9:11 ` Eric Martindale
2021-04-23 15:34 ` Antoine Riard
2021-04-24 10:16 ` nopara73
2021-04-25 20:29 ` [bitcoin-dev] Reminder on the Purpose of BIPs Matt Corallo
2021-04-25 21:00 ` Luke Dashjr [this message]
2021-04-25 21:14 ` Matt Corallo
2021-04-25 21:22 ` Luke Dashjr
2021-04-25 21:31 ` Matt Corallo
2021-04-26 19:43 ` David A. Harding
2021-04-26 20:04 ` Greg Maxwell
2021-04-27 19:43 ` Melvin Carvalho
2021-04-27 9:04 ` W. J. van der Laan
2021-04-27 11:49 ` Erik Aronesty
2021-04-27 11:33 ` John Newbery
2021-04-27 12:16 ` Jorge Timón
2021-04-26 15:02 ` [bitcoin-dev] Proposed BIP editor: Kalle Alm Sjors Provoost
2021-04-26 16:56 ` James O'Beirne
2021-04-26 18:13 ` W. J. van der Laan
2021-09-15 9:50 [bitcoin-dev] Reminder on the Purpose of BIPs Prayank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202104252100.07296.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox