Skip to content

Commit c59cfdb

Browse files
committed
bip-0002: Remove/merge old BIP 1 Status stuff
1 parent 0c203dc commit c59cfdb

File tree

1 file changed

+7
-20
lines changed

1 file changed

+7
-20
lines changed

bip-0002.mediawiki

Lines changed: 7 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -51,25 +51,7 @@ It must be a clear and complete description of the proposed enhancement.
5151
The enhancement must represent a net improvement.
5252
The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly.
5353

54-
The BIP author may update the Draft as necessary in the git repository. Updates to drafts should also be submitted by the author as pull requests.
55-
56-
Standards Track BIPs consist of two parts, a design document and a reference implementation.
57-
The reference implementation is not required to be begun until the BIP is accepted, unless having such an implementation will aid people in studying the BIP.
58-
Standards Track BIPs must include an implementation -- in the form of code, a patch, or a URL to same -- before it can be considered Final.
59-
60-
Once a BIP has been accepted, the reference implementation must be completed. When the reference implementation is complete and accepted by the community, the status will be changed to "Final".
61-
62-
A BIP can also be assigned status "Deferred". The BIP author or editor can assign the BIP this status when no progress is being made on the BIP. Once a BIP is deferred, the BIP editor can re-assign it to draft status.
63-
64-
A BIP can also be "Rejected". Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact.
65-
66-
BIPs can also be superseded by a different BIP, rendering the original obsolete. This is intended for Informational BIPs, where version 2 of an API can replace version 1.
67-
68-
The possible paths of the status of BIPs are as follows:
69-
70-
<img src="bip-0001/process.png"></img>
71-
72-
Some Informational and Process BIPs may also have a status of "Active" if they are never meant to be completed. E.g. BIP 2 (this BIP).
54+
The BIP author may update the draft as necessary in the git repository. Updates to drafts should also be submitted by the author as pull requests.
7355

7456
===Transferring BIP Ownership===
7557

@@ -181,15 +163,20 @@ BIPs may include auxiliary files such as diagrams. Auxiliary files should be inc
181163

182164
There are three kinds of BIP:
183165

184-
* A Standards Track BIP describes any change that affects most or all Bitcoin implementations, such as a change to the network protocol, a change in block or transaction validity rules, or any change or addition that affects the interoperability of applications using Bitcoin.
166+
* A Standards Track BIP describes any change that affects most or all Bitcoin implementations, such as a change to the network protocol, a change in block or transaction validity rules, or any change or addition that affects the interoperability of applications using Bitcoin. Standards Track BIPs consist of two parts, a design document and a reference implementation.
185167
* 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. Informational BIPs do not necessarily represent a Bitcoin community consensus or recommendation, so users and implementors are free to ignore Informational BIPs or follow their advice.
186168
* A Process BIP describes a process surrounding Bitcoin, or proposes a change to (or an event in) a process. Process BIPs are like Standards Track BIPs but apply to areas other than the Bitcoin protocol itself. They may propose an implementation, but not to Bitcoin's codebase; they often require community consensus; unlike Informational BIPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Bitcoin development. Any meta-BIP is also considered a Process BIP.
187169
188170
==BIP status field==
189171

190172
===Specification===
191173

174+
The possible paths of the status of BIPs are as follows:
175+
176+
<img src="bip-0001/process.png"></img>
177+
192178
Champions of a BIP may decide on their own to change the status between Draft, Deferred, or Withdrawn.
179+
The BIP editor may also change the status to Deferred when no progress is being made on the BIP.
193180

194181
A BIP may only change status from Draft (or Rejected) to Accepted, when the author deems it is complete, has a working implementation (where applicable), and has community plans to progress it to the Final status.
195182

0 commit comments

Comments
 (0)