From: アルム カールヨハン <karl@dglab.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] RFC BIP-0002: Defer, not reject.
Date: Tue, 13 Oct 2020 19:06:09 +0900 [thread overview]
Message-ID: <CALJw2w5bvLFeBAdWs=zQhR+hTcXqV18ntV3+tC-DzBuzCWPTOg@mail.gmail.com> (raw)
Hello,
I am making a minor proposed change to BIP-0002
https://github.com/bitcoin/bips/pull/1012
I propose that we change the 3-year-rule to allow anyone to change the
status of a BIP to "Deferred", rather than "Rejected".
Rejecting a BIP already has ambiguous meaning in BIP-0002 as it
stands, with "hard" rejects:
> The BIP editor will not unreasonably reject a BIP. Reasons for rejecting BIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Bitcoin philosophy.
and "soft" rejects:
> BIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in three years. Such a BIP may be changed to Draft status if the champion provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraph.
My proposal is that we disambiguate the second into "deferred" instead.
Alternatively, we add a new status e.g. "Inactive".
next reply other threads:[~2020-10-13 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 10:06 アルム カールヨハン [this message]
2020-11-02 12:11 ` [bitcoin-dev] RFC BIP-0002: Defer, not reject アルム カールヨハン
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='CALJw2w5bvLFeBAdWs=zQhR+hTcXqV18ntV3+tC-DzBuzCWPTOg@mail.gmail.com' \
--to=karl@dglab.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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