Skip to content

Commit

Permalink
Merge pull request #10 from kathrynmohror/ticket0v2
Browse files Browse the repository at this point in the history
Adding guidance for minor changes to the standard
  • Loading branch information
jjhursey authored Apr 15, 2020
2 parents be255b6 + 94d46e8 commit 2e8b1d0
Showing 1 changed file with 30 additions and 0 deletions.
30 changes: 30 additions & 0 deletions pmix_governance.tex
Original file line number Diff line number Diff line change
Expand Up @@ -449,6 +449,36 @@ \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.
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
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
Expand Down

0 comments on commit 2e8b1d0

Please sign in to comment.