From e9469a3d61187841fb20028a05abb2ec7c7c1ffb Mon Sep 17 00:00:00 2001 From: Daira Emma Hopwood Date: Thu, 14 Sep 2023 08:58:50 +0100 Subject: [PATCH] ZIP 0: Formatting and typos. Signed-off-by: Daira Emma Hopwood --- zip-0000.rst | 50 ++++++++++++++++++++++++++++---------------------- 1 file changed, 28 insertions(+), 22 deletions(-) diff --git a/zip-0000.rst b/zip-0000.rst index dcf8050e..ffabd78d 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -173,26 +173,32 @@ The current ZIP Editors are: * teor and Conrado Gouvea, associated with the Zcash Foundation. All can be reached at zips@z.cash. The current design of the ZIP Process -dictates that there are always at least two ZIP Editors: at least one from the -Electric Coin Company and at least one from the Zcash Foundation. +dictates that there are always at least two ZIP Editors: at least one +from the Electric Coin Company and at least one from the Zcash Foundation. -ZIP Editors MUST declare any potential or perceived conflict of interest they have -relating to their responsibilities as ZIP Editors. +ZIP Editors MUST declare any potential or perceived conflict of interest +they have relating to their responsibilities as ZIP Editors. + +Additional Editors may be selected, with their consent, by consensus +among the current Editors. + +An Editor may be removed or replaced by consensus among the current +Editors. However, if the other ZIP Editors have consensus, an Editor +can not prevent their own removal. -Additional Editors may be selected, with their consent, by consensus among the current Editors. -An Editor may be removed or replaced by consensus among the current Editors. -However, if the other ZIP Editors have consensus, an Editor can not prevent their own removal. Any Editor can resign by informing the other Editors in writing. Whenever the ZIP Editors change, the new ZIP Editors SHOULD: -- review this ZIP to make sure it reflects current practice, -- update the owners of this ZIP, -- review access to the `ZIPs repository `, -- update the email alias, and -- invite new Editors to the Zcash Community Forums, and the #zips channel on Discord. + +* review this ZIP to make sure it reflects current practice, +* update the Owners of this ZIP, +* review access to the `ZIPs repository `_, +* update the email alias, and +* invite new Editors to the Zcash Community Forum, and the #zips channel on Discord. If it has been at least 12 months since the last ZIP Editor change, the ZIP Editors SHOULD: -- review this ZIP to make sure it reflects current practice. + +* review this ZIP to make sure it reflects current practice. ZIP Editor Responsibilities @@ -229,7 +235,7 @@ ZIP Editors perform is expected to be independent of their contractual or other relationships. ZIP Owners are free to clarify, modify, or decline suggestions from ZIP Editors. -If the ZIP Editors make a change to a ZIP that the Owner disagrees with, then +If the ZIP Editors make a change to a ZIP that the Owners disagree with, then the Editors SHOULD revert the change. @@ -314,12 +320,11 @@ Communicating with the ZIP Editors Please send all ZIP-related communications either: * by email to , -* by opening an issue on the `ZIPs issue tracker `, or -* by sending a message in the `#zips channel on the Zcash R&D Discord `. +* by opening an issue on the `ZIPs issue tracker `_, or +* by sending a message in the `#zips channel on the Zcash R&D Discord `_. -__All communications should abide by the Zcash Code of Conduct [#conduct]_ -and follow `the GNU Kind Communication -Guidelines `.__ +**All communications should abide by the Zcash Code of Conduct** [#conduct]_ +**and follow the GNU Kind Communication Guidelines** [#gnukind]_. ZIP Editor Meeting Practices ---------------------------- @@ -549,7 +554,7 @@ Consensus Process Informational An Informational ZIP describes non-consensus Zcash design issues, or general guidelines or information for the Zcash community. These ZIPs - do not not necessarily represent a Zcash community consensus or + do not necessarily represent a Zcash community consensus or recommendation, so users and implementors are free to ignore Informational ZIPs or follow their advice. Network @@ -604,8 +609,8 @@ ZIP Status Field The status MAY indicate which node implementation has implemented the ZIP, e.g. "Implemented (zcashd)" or "Implemented (zebra)". -* Final: When a Consensus or Standards ZIP is both implemented - and activated on the Zcash network. +* Final: When a Consensus or Standards ZIP is both implemented and + activated on the Zcash network. * Obsolete: The status when a ZIP is no longer relevant (typically when superseded by another ZIP). @@ -769,6 +774,7 @@ References .. [#RFC3552] `RFC 3552: Guidelines for Writing RFC Text on Security Considerations `_ .. [#zip-0200] `ZIP 200: Network Upgrade Mechanism `_ .. [#conduct] `Zcash Code of Conduct `_ +.. [#gnukind] `GNU Kind Communication Guidelines `_ .. [#rst] `reStructuredText documentation `_ .. [#markdown] `The Markdown Guide `_ .. [#latex] `LaTeX — a document preparation system `_