Text improvements

lsst · Dec 24, 2018 · ed0ef06 · ed0ef06
1 parent 2cb4617
commit ed0ef06
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/dmgroups.tex b/dmgroups.tex
@@ -159,9 +159,9 @@ \subsection{DM Change Control Board \label{sect:dmccb}}
                 \item Systems Engineer, Chair (\secref{role:sysengineer}).
                 \item Operations Architect
                 \item Software Architect
-                \item DM Configuration and Release Manager (secretary)
+                \item DM Configuration and Release Manager, Secretary
                 \end{itemize}
-        \item Optional members are involved when topics to discuss are relevant to their areas of expertise:
+        \item Optional members (required when topics to discuss are relevant to their areas of expertise):
                 \begin{itemize}
                 \item DMPM Deputy, when DMPM is not available
                 \item DM Deputy Subsystem Scientist, when DM Subsystem Scientist is not available
@@ -174,7 +174,8 @@ \subsection{DM Change Control Board \label{sect:dmccb}}
 	\end{itemize}
 \end{itemize}
 
-The DM-CCB will meet, physically or virtually, every week for 30 minutes. Agenda will be available beforehand.
+The DMCCB will meet, physically or virtually, every week for 30 minutes. Agenda will be available beforehand.
+Urgent decisions can be taken offline, outside the weekly meeting, in a modality to be defined by the DMCCB itself (email or slack channel).
 
 \subsection{DM Science Validation Team}
 \label{sect:dmsvt}

diff --git a/dmorg.tex b/dmorg.tex
@@ -155,7 +155,7 @@ \subsubsection{Hardware Configuration Control}
 
 The DMCCB maintains the release plan, \citeds{LDM-564}, synchronized with the project milestones.
 
-All releases will be identified by a release issue - but we wish to move to Jira release functionality.
+All releases will be identified by a release issue.
 
 Any unscheduled release, major, minor or patch, needs to be requested by the end user to the DMCCB using a RFC Jira issue. The RFC shall contain:
 
@@ -165,7 +165,7 @@ \subsubsection{Hardware Configuration Control}
 \item A list of proposed functionalities or fixes (Jira issues) which are requested to be implemented in the release.
 \end{itemize}
 
-The DMCCB will assess the release request within one week. If the release is urgent, DMCCB will assess it within 24 hours, procedure to be clarified in \citeds{LDM-564}.
+The DMCCB will assess the release request within one week. If the release is urgent, DMCCB will assess it within 24 hours.
 The DMCCB will approve or reject the proposed release and add a comment to the RFC with the reason of rejection or, in case of approval, with the following information:
 
 \begin{itemize}