|
@@ -1,5 +1,5 @@
|
|
|
<pre>
|
|
|
- BIP: 1
|
|
|
+ PIP: 1
|
|
|
Title: PIP Purpose and Guidelines
|
|
|
Type: Process
|
|
|
Impact: None
|
|
@@ -18,7 +18,7 @@ PIPs are intended to be the primary mechanisms for proposing new features and do
|
|
|
|
|
|
## Copyright
|
|
|
|
|
|
-This BIP is dual-licensed under the Open Publication License and BSD 2-clause license.
|
|
|
+This PIP is dual-licensed under the Open Publication License and BSD 2-clause license.
|
|
|
|
|
|
|
|
|
## PIP Workflow
|
|
@@ -50,7 +50,7 @@ A PIP submission should be written in mark-down (GitHub flavor) and consist of t
|
|
|
- <b>Specification</b> -- Full technical description of the proposed new feature, clear enough for i
|
|
|
- <b>Rationale</b> -- Discussion why was the specification was chosen over alternate designs. Evidence supporting the specification should be provided here, as well as community concerns and consensus.
|
|
|
- <b>Backwards Compatibility</b> -- Any backwards incompatibilities should be described here, as well as work-arounds/solutions for these incompatibilities.
|
|
|
- - <b>Reference Implementation</b> -- The reference implementation must be provided before BIP is Completed.
|
|
|
+ - <b>Reference Implementation</b> -- The reference implementation must be provided before PIP is Completed.
|
|
|
- <b>Links</b> -- references and links to relevant material
|
|
|
|
|
|
PIP editors can use [this online editor](https://jbt.github.io/markdown-editor/) for editing and/or previewing their PIP submission.
|
|
@@ -59,7 +59,7 @@ PIP editors can use [this online editor](https://jbt.github.io/markdown-editor/)
|
|
|
|
|
|
<pre>
|
|
|
PIP: <<i>PIP number, or "?" before being assigned</i>>
|
|
|
- Title: <<i>BIP title; maximum 44 characters</i>>
|
|
|
+ Title: <<i>PIP title; maximum 44 characters</i>>
|
|
|
Type <<i>The type of PIP, see below for options</i>>
|
|
|
Author: <<i>list of authors' real names and email addrs</i>>
|
|
|
Impact <<i>How impactful the proposed changes are, see below for details.</i>>
|