From 6d8c63916f426972c0aae1b9180d2b27e9b74106 Mon Sep 17 00:00:00 2001 From: Daira Hopwood Date: Fri, 24 Jan 2020 15:27:53 +0000 Subject: [PATCH] ZIP 0: replace nonbreaking spaces with ordinary spaces. Signed-off-by: Daira Hopwood --- zip-0000.rst | 92 ++++++++++++++++++++++++++-------------------------- 1 file changed, 46 insertions(+), 46 deletions(-) diff --git a/zip-0000.rst b/zip-0000.rst index 726153e5..396ae554 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -205,42 +205,42 @@ appropriate. The ZIP Editors MAY reject a proposed ZIP or update to an existing ZIP for any of the following reasons: -* it violates the Zcash Code of Conduct [#conduct]_ ; -* it appears too unfocused or broad; -* it duplicates effort in other ZIPs without sufficient technical justification - (however, alternative proposals to address similar or overlapping problems - are not excluded for this reason); -* it has manifest security flaws (including being unrealistically dependent - on user vigilance to avoid security weaknesses); -* it disregards compatibility with the existing Zcash blockchain or ecosystem; -* it is manifestly unimplementable; -* it includes buggy code, pseudocode, or algorithms; -* it manifestly violates common expectations of a significant portion of the - Zcash community; -* it updates a Draft ZIP to Released when 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 +* it violates the Zcash Code of Conduct [#conduct]_ ; +* it appears too unfocused or broad; +* it duplicates effort in other ZIPs without sufficient technical justification + (however, alternative proposals to address similar or overlapping problems + are not excluded for this reason); +* it has manifest security flaws (including being unrealistically dependent + on user vigilance to avoid security weaknesses); +* it disregards compatibility with the existing Zcash blockchain or ecosystem; +* it is manifestly unimplementable; +* it includes buggy code, pseudocode, or algorithms; +* it manifestly violates common expectations of a significant portion of the + Zcash community; +* it updates a Draft ZIP to Released when 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); -* in the case of a Released ZIP, the update makes a substantive change to - which there is significant community opposition; -* it is dependent on a patent that could potentially be an obstacle to - adoption of the ZIP; -* it includes commercial advertising or spam; -* it disregards formatting rules; -* it makes non-editorial edits to previous entries in a ZIP's Change history; -* an update to an existing ZIP extends or changes its scope to an extent - that would be better handled as a separate ZIP; -* a new ZIP has been proposed for a category that does not reflect its content, - or an update would change a ZIP to an inappropriate category; -* it updates a Released ZIP to Draft when the specification is already - implemented and has been in common use; +* in the case of a Released ZIP, the update makes a substantive change to + which there is significant community opposition; +* it is dependent on a patent that could potentially be an obstacle to + adoption of the ZIP; +* it includes commercial advertising or spam; +* it disregards formatting rules; +* it makes non-editorial edits to previous entries in a ZIP's Change history; +* an update to an existing ZIP extends or changes its scope to an extent + that would be better handled as a separate ZIP; +* a new ZIP has been proposed for a category that does not reflect its content, + or an update would change a ZIP to an inappropriate category; +* it updates a Released ZIP to Draft when the specification is already + implemented and has been in common use; * it violates any specific "MUST" or "MUST NOT" rule in this document; -* the expressed political views of a Owner of the document are inimical - to the Zcash Code of Conduct [#conduct]_ (except in the case of an update - removing that Owner); -* it is not authorized by the stated ZIP Owners; -* it removes an Owner without their consent (unless the reason for removal - is directly related to a breach of the Code of Conduct by that Owner). +* the expressed political views of a Owner of the document are inimical + to the Zcash Code of Conduct [#conduct]_ (except in the case of an update + removing that Owner); +* it is not authorized by the stated ZIP Owners; +* it removes an Owner without their consent (unless the reason for removal + is directly related to a breach of the Code of Conduct by that Owner). The ZIP Editors MUST NOT unreasonably deny publication of a ZIP proposal or update that does not violate any of these criteria. If they refuse a @@ -314,29 +314,29 @@ ZIP header preamble Each ZIP must begin with an RFC 822-style header preamble. The following header fields are REQUIRED:: -  ZIP: -  Title: -  Owners: -  Status: -  Category: + ZIP: + Title: + Owners: + Status: + Category: Created: -  License: + License: The following additional header fields are OPTIONAL:: Credits: Original-Authors: Discussions-To: - Network Upgrade: - Obsoleted by: - Updated by: + Network Upgrade: + Obsoleted by: + Updated by: Obsoletes: Updates: The Owners header lists the names and email addresses of all the Owners of the ZIP. The format of the Owners header value SHOULD be:: - Random J. User  + Random J. User If there are multiple Owners, each should be on a separate line. @@ -493,8 +493,8 @@ MUST be referenced by their respective abbreviation given below. For example, a preamble might include the following License header:: - License: BSD-2-Clause -    GNU-All-Permissive + License: BSD-2-Clause + GNU-All-Permissive In this case, the ZIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and