Age | Commit message (Collapse) | Author |
|
It seems the date is wrong for when this BIP was created. I see here (https://sourceforge.net/p/bitcoin/mailman/message/28106734/) it was created on 9/19/11. I don't see any earlier entries on the mailing list that would suggest the 8/19 date is accurate
|
|
- Update all Accepted status to Proposed (renamed status)
- The BIP Comments preamble headers added to every BIP
- The License preamble headers have been added to all BIPs with a Copyright section
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Greg asked that I take over BIP number assignments
|
|
https://github.com/bitcoin/bips/pull/269#issuecomment-168335009
|
|
|
|
Also, remove an unnecessarily duplicated sentence.
|
|
The previous BIP1 text was ambiguous regarding early steps for taking an
idea from concept and eventually into a BIP. The new text is intended to
make it more clear that the initial email to the bitcoin-dev mailing
list should not be a fully-formed BIP. There have been exceptions to
this in the past for ideas already widely known and implementation in
progress, but "you know it when you see it". Hopefully this will add
clarity to the BIP authoring process and work flow for new authors.
|
|
This switches from specifying "Bitcoin issue tracker" to specifying
"Bitcoin Core issue tracker". Other issue trackers are useful for other
client development activities, although this does not seem necessary to
mention.
|
|
|
|
Previously BIP-0001 listed in its header preamble that is was a "Standards Track"
type proposal. This conflicts with both its own definition of "Standards Track"
proposal as well as the type listed in PEP-0001 of which BIP-0001 is based on.
Defitions of each type of proposal:
A Standards Track BIP describes any change that affects most or all Bitcoin implementations.
An Informational BIP describes a Bitcoin design issue, or provides general guidelines or information to the Bitcoin community, but does not propose a new feature.
A Process BIP describes a process surrounding Bitcoin, or proposes a change to (or an event in) a process.
Specifically: "Any meta-BIP is also considered a Process BIP."
Based on these definitions BIP-0001 should have always been labeled as a "Process" BIP and this patch corrects this.
|
|
From the text: "Some Informational and Process BIPs may also have a
status of "Active" if they are never meant to be completed. E.g. BIP 1
(this BIP)."
|
|
|
|
|
|
A second link to the mailing list was missed and left pointing to the old
list.
|
|
|
|
|
|
This came up on the mailing list.
yyyy-mm-dd (ISO 8601) is the internationally accepted format for numeric
dates. This commit changes all BIPs to use that instead of dd-mm-yyyy.
It also updates BIP 0001 to prescribe the new format.
|
|
- Mention github instead of wiki
- Add markdown as allowed format
- Fix some weirdnesses such as "A BIP editor must subscribe to the
gmaxwell@gmail.com list.". Remove the repetition and create a new
section which lists the BIP editors (currently only gmaxwell).
- Prefer discussion on mailing list to forum
|
|
|
|
https://en.bitcoin.it/w/index.php?title=BIP_0001&oldid=41572
|
|
|