zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #723 from daira/zip-0-updates-3 

ZIP 0: Leftover change from #716
This commit is contained in:
Daira Emma Hopwood 2023-10-31 14:28:28 +00:00 committed by GitHub
parent 6db2ef822c 3f36a2ca4b
commit b1410c0f42
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
zip-0000.html
View File

@ -295,8 +295,7 @@ Updates:</pre>
<p>A ZIP SHOULD NOT be changed from a non-Released status to a Released status if there is significant community opposition to its content. (However, Draft ZIPs explicitly MAY describe proposals to which there is, or could be expected, significant community opposition.)</p>
<p>A Released ZIP MUST NOT be changed to a non-Released status if the specification is already implemented and is in common use, or where a Process ZIP still reflects a consensus of the community.</p>
<p>A Standards ZIP SHOULD only change status from Proposed to Implemented once the Owners provide an associated reference implementation. For Consensus ZIPs, an implementation MUST have been merged into at least one consensus node codebase (currently zcashd and/or zebra), typically in the period after the network upgrade's specification freeze but before the implementation audit. If the Owners miss this deadline, the Editors or Owners MAY choose to update the Deployment section of the ZIP to target another upgrade, at their discretion.</p>
<p>A Process or Informational ZIP SHOULD change status from Draft to Active when it achieves rough consensus on the forum or PR. Such a proposal is said to have rough consensus if it has been open to discussion on the forum or GitHub PR for at least one month, and no person maintains any unaddressed substantiated objections to it. Addressed or obstructive objections can be ignored/overruled by general agreement that they have been sufficiently addressed, but clear reasoning MUST be given in such circumstances.</p>
<p>Any transition directly from Draft to Active MUST also satisfy requirements for transition from Draft to Proposed.</p>
<p>A Process or Informational ZIP SHOULD change status from Proposed to Active when it achieves rough consensus on the forum or PR. Such a proposal is said to have rough consensus if it has been substantially complete and open to discussion on the forum or GitHub PR for at least one month, has been in Proposed status for at least one week, and no person maintains any unaddressed substantiated objections to it. Addressed or obstructive objections can be ignored/overruled by general agreement that they have been sufficiently addressed, but clear reasoning MUST be given in such circumstances.</p>
<p>When an Active, Implemented, or Final ZIP is no longer relevant –for example because its implementation has fallen out of use or its process is no longer followed– its status SHOULD be changed to Obsolete. This change MUST also be objectively verifiable and/or discussed. Final ZIPs MAY be updated; the specification is still in force but modified by another specified ZIP or ZIPs (check the optional Updated-By header).</p>
<p>If a non-editorial update is made to an Obsolete, Withdrawn, or Rejected ZIP, its status MUST be changed appropriately.</p>
</section>

20
zip-0000.rst
View File

@ -658,17 +658,15 @@ the implementation audit. If the Owners miss this deadline, the Editors
or Owners MAY choose to update the Deployment section of the ZIP to
target another upgrade, at their discretion.
A Process or Informational ZIP SHOULD change status from Draft to Active
when it achieves rough consensus on the forum or PR. Such a proposal is
said to have rough consensus if it has been open to discussion on the
forum or GitHub PR for at least one month, and no person maintains
any unaddressed substantiated objections to it. Addressed or obstructive
objections can be ignored/overruled by general agreement that they have
been sufficiently addressed, but clear reasoning MUST be given in such
circumstances.
Any transition directly from Draft to Active MUST also satisfy requirements
for transition from Draft to Proposed.
A Process or Informational ZIP SHOULD change status from Proposed to
Active when it achieves rough consensus on the forum or PR. Such a
proposal is said to have rough consensus if it has been substantially
complete and open to discussion on the forum or GitHub PR for at least
one month, has been in Proposed status for at least one week, and no
person maintains any unaddressed substantiated objections to it. Addressed
or obstructive objections can be ignored/overruled by general agreement
that they have been sufficiently addressed, but clear reasoning MUST be
given in such circumstances.
When an Active, Implemented, or Final ZIP is no longer relevant –for
example because its implementation has fallen out of use or its process