From a452b2070941c4b3119a4e7ebf49bb5f824f057e Mon Sep 17 00:00:00 2001 From: Kathryn Mohror Date: Sun, 15 Dec 2019 10:26:42 -0800 Subject: [PATCH 1/2] Changes to add guidance for minor changes to PMIx standard Signed-off-by: Kathryn Mohror --- pmix_governance.tex | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/pmix_governance.tex b/pmix_governance.tex index 5ff1bbb..a2c3ee4 100755 --- a/pmix_governance.tex +++ b/pmix_governance.tex @@ -449,6 +449,33 @@ \subsubsection{Release Schedule Guidance}\label{release-schedule-guidance}} Release Managers will prioritize major releases of the standard over waiting for additional changes that are in progress but not yet accepted by the ASC. +\hypertarget{administrative-changes-guidance}{% +\subsubsection{Minor Document Changes Guidance}\label{administrative-changes-guidance}} +The intention of the rigorous process outlined in +Section~\ref{the-standardization-process} for proposed +changes to the PMIx Standard is to ensure quality and consistency of +the interface and the overall document. However, in some cases, +PMIx participants may propose minor changes to the document that +should not require the full process required for substantive changes. +Examples of these minor changes include fixes for typographical errors +(``typos''), missing or erroneous punctuation, and formatting changes. + +In the case minor changes are proposed, the proposer should +create an issue and pull request as described in Sections~\ref{initial-discussion} +and \ref{proposed-modification} and then bring the +changes to the attention of the ASC Co-Chairs and Release Managers. +The Co-Chairs and Release Managers will evaluate the proposed +changes to determine whether they are minor or substantive. +If all Co-Chairs and Release Managers determine that the +changes are minor and do not alter the meaning of the current standard text, +then the changes do not require the full process and +the changes can be applied to the document in the next release. +Alternatively, if any of the Co-Chairs or Release Managers determine +that the changes do or could alter the meaning of the current standard text, +the changes will be handled using the full rigorous process +as described in Section~\ref{the-standardization-process}. + + \hypertarget{the-standardization-process}{% \subsection{The Standardization From 94d46e810ee401f161b271a11f170eb2a18e0ef2 Mon Sep 17 00:00:00 2001 From: Kathryn Mohror Date: Tue, 17 Dec 2019 07:35:08 -0800 Subject: [PATCH 2/2] adding text to clarify that all participants are encouraged to examine and comment on proposed changes Signed-off-by: Kathryn Mohror --- pmix_governance.tex | 3 +++ 1 file changed, 3 insertions(+) diff --git a/pmix_governance.tex b/pmix_governance.tex index a2c3ee4..d145cdf 100755 --- a/pmix_governance.tex +++ b/pmix_governance.tex @@ -466,6 +466,9 @@ \subsubsection{Minor Document Changes Guidance}\label{administrative-changes-gui changes to the attention of the ASC Co-Chairs and Release Managers. The Co-Chairs and Release Managers will evaluate the proposed changes to determine whether they are minor or substantive. +Additionally, all PMIx participants are encouranged to examine +and comment on the changes in the pull request to aid the +Co-Chairs and Release Managers in their decision. If all Co-Chairs and Release Managers determine that the changes are minor and do not alter the meaning of the current standard text, then the changes do not require the full process and