From: Luke Dashjr <luke@dashjr•org>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP 2 revival and rework
Date: Sat, 24 Sep 2016 06:36:00 +0000 [thread overview]
Message-ID: <201609240636.01968.luke@dashjr.org> (raw)
I've revived BIP 2 (from Deferred Status) and given it some updates. Most
notably, I have reworked it to be a *replacement* for BIP 1 rather than an
addendum.
https://github.com/luke-jr/bips/blob/bip0002_squash/bip-0002.mediawiki
Please review it. If things go well, hopefully we can get this done by
Christmas. ;)
Other recent changes include:
* OPL will no longer be an acceptable license. Many in the community feel that
prohibiting publication is unacceptable for BIPs, and I haven't heard any
arguments in favour of allowing it.
* Accepted Status has been renamed to Proposed. The name "Accepted" seems a
constant source of confusion since it requires only action from the author.
* Non-image auxiliary files are permitted in the bip-XXXX subdirectory. This
was already the norm despite BIP 1.
* Email addresses are now required for authors. The Travis script has been
enforcing this for months now already.
* The Post-History header may be provided as a link instead of a simple date.
A few BIPs were already doing this.
* Markdown format is no longer permitted for BIPs. I don't see the point in
allowing multiple formats, and so far we've been fine with just MediaWiki.
* The Resolution header has been dropped, as it is not applicable to a
decentralised system where no authority exists to make final decisions.
Other changes already in the previous draft of BIP 2:
* An implementation is now required (when applicable) before BIPs can proceed
to Proposed Status.
* BIP Comments are newly introduced.
* The License preamble headers have been added.
Thanks,
Luke
next reply other threads:[~2016-09-24 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 6:36 Luke Dashjr [this message]
2016-09-24 9:41 ` Tom
2016-10-15 10:25 ` Marco Falke
[not found] ` <CAK51vgAhpOFQRgnSxrNrP1JyhBZA3dr7mWKYKD15h0xgO6rR5A@mail.gmail.com>
2016-10-15 11:00 ` Tom Zander
2016-10-15 12:12 ` Marco Falke
2016-10-15 14:21 ` Tom Zander
2016-10-15 15:02 ` Marco Falke
2016-10-16 14:56 ` Tom Zander
2016-10-15 13:01 ` Luke Dashjr
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=201609240636.01968.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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