From 77e372936da63f61f41113dbe74c27f517e7e478 Mon Sep 17 00:00:00 2001 From: Arun Kannawadi Date: Thu, 14 Aug 2025 11:51:12 -0400 Subject: [PATCH 1/2] Clarify team assignment for lsst-dm repos --- stack/adding-a-new-package.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/stack/adding-a-new-package.rst b/stack/adding-a-new-package.rst index 4af879a7..37940741 100644 --- a/stack/adding-a-new-package.rst +++ b/stack/adding-a-new-package.rst @@ -47,10 +47,11 @@ Repository access ----------------- Access to the repository must be granted by a repository administrator to appropriate teams. -For DM-written code, these include "Data Management" and "Overlords." +For DM-written code living in the ``lsst`` organization, these include "Data Management" and "Overlords." For third-party code, either forked or packaged as "TaP" tarball-and-patch, use the "DM Externals" and "Overlords" (but *not* "Data Management") teams. Note that the "DM Auxilliaries" [sic] team is used to mark packages that are *not* part of the release distribution; it is used to tag them alongside the release as well as to catch accidental inclusions. The roles assigned to these teams should typically be "Write" for "Data Management", "Admin" for "Overlords", and "Read" for all others, but most permissions are handled at the organization level, so these could even be "Read" for all teams. +For repositories in the ``lsst-dm`` organization, roles assigned to the teams should typically be "Write" for "Data Management" and "Read" for "DM Auxilliaries". .. warning:: From 7935889dec79d42fdb5c50182bbd43fe6a99a240 Mon Sep 17 00:00:00 2001 From: Arun Kannawadi Date: Thu, 14 Aug 2025 11:58:30 -0400 Subject: [PATCH 2/2] Add a note about build but not distribution Co-authored-by: Kian-Tat Lim --- stack/adding-a-new-package.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/stack/adding-a-new-package.rst b/stack/adding-a-new-package.rst index 37940741..c56b4b86 100644 --- a/stack/adding-a-new-package.rst +++ b/stack/adding-a-new-package.rst @@ -51,7 +51,8 @@ For DM-written code living in the ``lsst`` organization, these include "Data Man For third-party code, either forked or packaged as "TaP" tarball-and-patch, use the "DM Externals" and "Overlords" (but *not* "Data Management") teams. Note that the "DM Auxilliaries" [sic] team is used to mark packages that are *not* part of the release distribution; it is used to tag them alongside the release as well as to catch accidental inclusions. The roles assigned to these teams should typically be "Write" for "Data Management", "Admin" for "Overlords", and "Read" for all others, but most permissions are handled at the organization level, so these could even be "Read" for all teams. -For repositories in the ``lsst-dm`` organization, roles assigned to the teams should typically be "Write" for "Data Management" and "Read" for "DM Auxilliaries". +For the rare repositories in the ``lsst-dm`` organization that are part of the build but not distributed, roles assigned to the teams should typically be "Write" for "Data Management" and "Read" for "DM Auxilliaries". +(There must not be repositories in ``lsst-dm`` that are distributed, and other repositories in ``lsst-dm`` do not need team assignments.) .. warning::