From 3f36a2ca4b58dfb023be4889ed74937578f052c6 Mon Sep 17 00:00:00 2001 From: Daira Emma Hopwood Date: Fri, 29 Sep 2023 15:12:30 +0100 Subject: [PATCH] Revert "Revert a change as discussed in the 2023-09-27 ZIP Editors' meeting," This reverts commit 01190867fddd747ac6556955efbc24821822aa35. --- zip-0000.html | 3 +-- zip-0000.rst | 20 +++++++++----------- 2 files changed, 10 insertions(+), 13 deletions(-) diff --git a/zip-0000.html b/zip-0000.html index d3a5f89d..0b5a43e8 100644 --- a/zip-0000.html +++ b/zip-0000.html @@ -295,8 +295,7 @@ Updates:

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.)

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.

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.

-

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 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).

If a non-editorial update is made to an Obsolete, Withdrawn, or Rejected ZIP, its status MUST be changed appropriately.

diff --git a/zip-0000.rst b/zip-0000.rst index 02726b7c..fd6d455a 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -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