Skip to content

Commit 6d3b92d

Browse files
Merge pull request #726 from lsst-dm/u/arunkannawadi/lsst-dm-team-roles
Clarify team assignment for lsst-dm repos
2 parents e6e75c8 + 7935889 commit 6d3b92d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

stack/adding-a-new-package.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,12 @@ Repository access
4747
-----------------
4848

4949
Access to the repository must be granted by a repository administrator to appropriate teams.
50-
For DM-written code, these include "Data Management" and "Overlords."
50+
For DM-written code living in the ``lsst`` organization, these include "Data Management" and "Overlords."
5151
For third-party code, either forked or packaged as "TaP" tarball-and-patch, use the "DM Externals" and "Overlords" (but *not* "Data Management") teams.
5252
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.
5353
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.
54+
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".
55+
(There must not be repositories in ``lsst-dm`` that are distributed, and other repositories in ``lsst-dm`` do not need team assignments.)
5456

5557
.. warning::
5658

0 commit comments

Comments
 (0)