Summary:
<a href="https://hackmd.io/@sbacha/improve-yip-categories">proposed YIP.md here 55</a>
<blockquote>
Add new <code>status</code>(s) to <code>YIPs</code> so that author(s) may better manage their <code>YIPs</code> in the context of community collaboration and so that governance is given the proper procedures to foster community cooperation.
</blockquote>
Abstract:
<blockquote>
This will only add to the current state of <code>proposal YIPs</code> in that it only changes the <code>status</code> of a <code>YIP</code>. It does not add any <code>protocol</code> changes: only documentation and governance procedures (off chain only).
</blockquote>
I proposal the following changes to reflect a new state of possible ‘YIPs’:
<ol>
<li>Modifying YIP Templates</li>
<li>Modifying YIP Validator Gemfile</li>
<li>Modifying YIP README file</li>
</ol>
Motivation:
<blockquote>
The current state of procedures for <code>YIPS</code> is inadequate as it unnecessarily limits the possible outcomes of a proposed <code>YIP</code> while not affording both the author(s) nor the governance council flexibility in being able to deal with community driven <code>YIPs</code>
</blockquote>
This is a documentation and procedure change. In fact there is no explicit description for proposing such changes in governance (that I could find).
This change is needed as it better explains the intent of the YIP format to author(s). It also provides for governance additional functionality in their procedures so as to not potentially ‘alienate’ author(s) by rejecting a YIP when it could have been withdrawn. This ensures that also the author(s) are active in the process of their submitted proposal and in the larger community (in so far as they are knowledgable about other potentially competing YIPS.)
Specification:
<blockquote>
Proposed - a YIP that is ready to be reviewed in a governance call. 
Approved - a YIP that has been accepted for implementation by the yEarn community. 
Implemented - a YIP that has been released to mainnet. 
Rejected - a YIP that has been rejected. 
Withdrawn - a YIP that has been withdrawn by the author(s). 
Deferred - a YIP that governance has decided to wait for another YIP/some other change that should be bundled with it together 
Moribund - a YIP that was once Implemeneted. It is now Obsolete ‘AND’ requires no explicit replacement.
</blockquote>
The “Withdrawn” status is similar - it means that the YIP author has decided that the YIP is actually a ‘bad’ idea, or has accepted that a competing proposal is a better alternative.
<h3>Workflow Specification</h3>
<pre><code>Proposed -&gt; Approved -&gt; Implemented
 ^ |
 +----&gt; Rejected +----&gt; Moribund
 |
 +----&gt; Withdrawn
 v
Deferred
</code></pre>
For:
Against:
Poll:

YIP-44: Improve YIP categories

Got something to add?