Merge pull request #4 from lsst-sitcom/tickets/SITCOM-1326

SITCOM-1326: Update for consistency with implementation of data security protocols for Rubin Obs communication channels

Author: bechtol

SITCOMTN-076.tex

@@ -39,6 +39,7 @@
 \setDocChangeRecord{%
   \addtohist{1}{2024-01-09}{Initial release version.}{Keith Bechtol}
   \addtohist{2}{2024-02-12}{Clarify definition of electro-optical data and special types of images that can be approved for release.}{Keith Bechtol}
+  \addtohist{3}{2024-05-02}{Update for consistency with Rubin Obs communication channels data security implementation.}{Keith Bechtol}
 }
 
 
@@ -98,6 +99,8 @@ \section{Motivation and Scope}
 
 This document also includes a proposed set of guidelines for the Rubin Observatory Project team that are intended to promote the generation and dissemination of high-quality documentation to support the LSST science community.
 
+%\citedsp{DMTN-286} describes the implementation of data security protocols for Rubin Observatory communication channels.
+
 \subsection{Definitions}
 \label{definitions}
 
@@ -115,7 +118,7 @@ \subsection{Definitions}
   \item \textbf{Astronomical metadata} includes the schedule and sky location for each visit \citedsp{DMTN-263}.
 
   \item \textbf{Approved Project tools} for communication and work planning include Confluence, Slack, Jira, DocuShare, Rubin Observatory webpages, Rubin Observatory LSST Community forum, LSST GitHub organizations, change-controlled documents, technical documents, and email lists (see, e.g., \url{https://project.lsst.org/} and \url{https://developer.lsst.io/}).
-  Given that some of these tools are visible and/or used by both the Project team and broader LSST science community, appropriate controls will be put in place to ensure that information sharing policies are maintained.
+  Given that some of these tools are visible and/or used by both the Project team and broader LSST science community, appropriate controls will be put in place to ensure that data security policies are maintained \citedsp{DMTN-286}.
 
 \end{itemize}
 
@@ -154,11 +157,12 @@ \subsection{Summary}
 
 All pixel images and representations of pixel images of any size field of view, including individual visit images, coadd images, and difference images based on ComCam and LSSTCam commissioning on-sky observations are embargoed for a period of at least 30 days, with the exception of alert postage stamp images that have been publicly released to community alert brokers as well as certain specifically approved types of images that illustrate technical performance aspects of the observatory (Section \ref{special_classes}).
 
-During the period from installation of ComCam and LSSTCam on the telescope to the release of Data Preview 2, all communications (including informal discussion) regarding proprietary engineering and on-sky data with ComCam and LSSTCam are internal to Rubin Project by default.
-Outward-facing communications, including all on-sky ComCam and LSSTCam images, are reviewed by SIT-Com leadership, the Rubin Celebrations Organizing Committee (RCOC) and its relevant subgroups, and the Communications team, and are approved for release by the Project Director or designated alternate.
+Proprietary data products from commissioning, including all focal plane scientific data, may NOT be shared beyond the Project team until their release as part of the Early Science Program (Section \ref{early_science}).
+%During the period from installation of ComCam and LSSTCam on the telescope to the release of Data Preview 2, all communications (including informal discussion) regarding proprietary engineering and on-sky data with ComCam and LSSTCam are internal to Rubin Project by default.
+%Communication regarding specific unreleased engineering and on-sky data products from ComCam and LSSTCam are internal to Rubin Project by default.
+%During the period from installation of ComCam and LSSTCam on the telescope to the release of Data Preview 2, communications regarding proprietary engineering and on-sky data products from ComCam and LSSTCam are internal to Rubin Project by default.
 
 The status of the commissioning effort will be shared frequently with the world.
-
 Example outward-facing communications:
 
 \begin{itemize}
@@ -177,25 +181,54 @@ \subsection{Summary}
 
 \end{itemize}
 
+Rubin Observatory outward-facing communications, including all on-sky ComCam and LSSTCam commissioning images, are reviewed by SIT-Com leadership, the Rubin Celebrations Organizing Committee (RCOC) and its relevant subgroups, the Communications team, and/or are approved for release by the Project Director or designated alternate.
+
 Free and unfettered communication among Project team members is essential for commissioning success.
 Project team members are required to use only approved Project tools, platforms, and processes for communication, data access and analysis, documentation, software development, work management, etc.
-Derived data products are not subject to those restrictions, but are embargoed until approval for release (see Section \ref{technotes}).
+%Derived data products are not subject to those restrictions, but are embargoed until approval for release (see Section \ref{technotes}).
 In practice, we expect most work done by the Project team on the commissioning data to be done within protected directories at the Rubin US Data Facility at SLAC.
+\citedsp{DMTN-286} describes the implementation of data security protocols for Rubin Observatory communication channels.
 
-Prior to the release of associated data products as part of the Early Science program, derived data products from ComCam and LSSTCam on-sky commissioning data may be shared beyond the Project team only in the following situations:
+Prior to the release of associated data products as part of the Early Science program, derived data products from ComCam and LSSTCam on-sky commissioning data may approved for release by
+%may be shared beyond the Project team only in the following situations:
 
 \begin{enumerate}
 
-  \item the derived data product has been approved for release in one of the official Rubin Observatory outward-facing communication channels;
+  %\item the derived data product is approved for released in one of the official Rubin Observatory outward-facing communication channels;
+  \item being shared in one the official Rubin Observatory outward-facing communication channels and/or
 
-  \item the derived data product is documented as part of an approved technote (see Section \ref{technotes}).
+  %\item the derived data product is documented as part of an approved technote (see Section \ref{technotes}).
+  \item being documented as part of an approved technote (see Section \ref{technotes}).
 
 \end{enumerate}
 
+Incidental access to non-image derived data products based on unreleased ComCam and LSSTCam on-sky commissioning data might occur via Rubin Observatory communication channels that are shared with the community (e.g., github, Jira, Confluence); these should be understood as describing infrastructure work in progress.
+
 Derived data products that represent visit, coadd, and difference images from ComCam and LSSTCam on-sky commissioning are embargoed for a period of at least 30 days following the observation, with the exception of alert postage stamp images and certain specifically approved types of images that illustrate technical performance aspects of the observatory (Section \ref{special_classes}).
 
-During the on-sky commissioning period with ComCam and LSSTCam, members of the Project team are allowed to discuss technical details of their work outside the team, and they may freely discuss aspects that do NOT relate to specific on-sky data products from ComCam and LSSTCam or interim science performance.
-Discussion on the general status of commissioning should refer to Project-approved resources for information on the progress of commissioning activities (e.g., digests, news stories, published Project status on the Rubin Observatory website).
+During the on-sky commissioning period with ComCam and LSSTCam, members of the Project team may discuss technical details of their infrastructure work outside the team.
+%, but no aspects of any science result (unreleased information about astronomical phenomena above the Earth atmosphere) may be shared until after the associated data release.
+% provided that (1) it does not compromise the effectiveness of Rubin Observatory communications and (2) it does not relate to
+%, and they may freely discuss aspects that do NOT relate to specific on-sky data products from ComCam and LSSTCam.
+% or interim science performance.
+%Discussion beyond the Project team that involves unreleased on-sky data products from ComCam and LSSTCam should only reference information that is broadly accessible to the Rubin Observatory community via standard shared Rubin Observatory communication channels.
+Discussion on the general status of commissioning and interim science performance should refer to Project-approved resources (e.g., digests, news stories, published Project status on the Rubin Observatory website, approved technotes).
+% for information on the progress of commissioning activities
+
+%In general, we are trying to maintain a broadly open system for Rubin Observatory.
+%This implies that community members have access to a wealth of other information about Rubin Observatory, aside from pixel data.
+%During commission, much of this information will be about problems.
+%We expect the community to be respectful of this information and consider the state of the system, which in commissioning is not finished.
+
+\begin{note}[Be Kind]
+We recognize that there is a tension between data security needs, public outreach and communications effectiveness, collaboration and transparency with the Rubin Observatory science community, and providing equitable access to science-ready data products, all while commissioning a complex new system with a large geographically distributed team.
+In general, we are trying to maintain a broadly open system for Rubin Observatory.
+This implies that community members have access to a wealth of other information about Rubin Observatory, aside from the embargoed pixel data.
+During commissioning, much of the communication will be about problems that are actively being worked.
+We expect the community to be respectful of this information and consider the state of the system, which in commissioning, is not finished.
+\textit{Much of the information that is accessible on Rubin Observatory communication channels (e.g., development branches on github, Slack, Jira, Confluence) should be treated as the work in progress of professional colleagues and collaborators.}
+\href{https://www.lsst.org/about/dei/kindness}{Be kind}.
+\end{note}
 
 \subsection{AuxTel, Electro-optical Datasets from ComCam and LSSTCam, and Non-proprietary Precursor Datasets}
 
@@ -213,12 +246,16 @@ \subsection{Technotes}
 Technotes may present science validation analyses, but are not intended to include novel scientific results / discoveries.
 Each technote should have a well defined scope.
 
-Prior to the associated Early Science release, technotes that involve proprietary on-sky ComCam and LSSTCam data must be first drafted in a restricted space and reviewed/approved by the Project using a standard checklist in a timely manner before posting.
-This process will ensure that released technotes meet basic standards for documentation quality and conform to Rubin Observatory information release policies.
+Technotes are drafted using development branches following the standard development workflow described at \url{https://developer.lsst.io/}.
+For technotes that involve proprietary on-sky ComCam and LSSTCam data, the review will include a standard checklist to ensure that released technotes meet basic standards for documentation quality and conform to Rubin Observatory information release policies.
+The content of a technote is considered to be approved for release once merged to the main branch.
+During development, embargoed pixel images can only be referenced in technotes as authenticated links —- pixel images (e.g., PNGs) must NOT appear in technotes until specifically approved for release.
+%Prior to the associated Early Science release, technotes that involve proprietary on-sky ComCam and LSSTCam data must be first drafted in a restricted space and reviewed/approved by the Project using a standard checklist in a timely manner before posting.
+%This process will ensure that released technotes meet basic standards for documentation quality and conform to Rubin Observatory information release policies.
 As living documents, technotes may describe work in progress and may be updated as studies progress.
 Once released, updated technote versions must maintain compliance with the approval checklist criteria.
 
-Derived data products may be documented and shared via technotes that have been approved for public release.
+Derived data products may be documented and shared via technotes that have been approved for release.
 
 \subsection{Approving Special Types of Pixel-level On-sky Images for Release}
 \label{special_classes}
@@ -285,7 +322,7 @@ \section{Peer-reviewed Journal Publications}
   \item Project team members are free to collaborate with others beyond the Project team on science papers that use released Early Science data (following the Rubin Data Policy \citedsp{RDO-013}), but may not share proprietary commissioning data with collaborators prior to its release.
   The Project team authors are welcome to inform their collaborators about their intent to write such science papers prior to the release, but no aspects of any science result (unreleased information about astronomical phenomena above the Earth atmosphere) may be shared until after the associated data release.
 
-  \item The authors are encouraged, but not obliged, to announce plans for science publications as soon as possible within the Project team and welcome collaboration.
+  \item The authors are encouraged, but not obliged, to announce plans for science publications as soon as possible within the Project team and to welcome collaboration.
   They should discuss relevant publication policies (e.g., from LSST Science Collaborations) well in advance to avoid possible tensions.
 
   \item A technote describing science validation analysis of on-sky commissioning data could become the basis for (parts of) a science paper submitted to a peer-review journal / the arXiv.