Minor suggestions for cleanups in https://github.com/lsst/LDM-294/pull/85.

Note that we don't have a position called “Science Platform Lead”. We have a “Science Platform Manager”.

After some discussion, it is apparent that in the current text the line has not properly been drawn between "release tooling" and the build/packaging system.

Specifically, the tooling provided by SQuaRE is limited to the Jenkins installation and the Groovy scripts in dm-jenkins-jobs that it executes. The build/packaging system has been assigned to Architecture by default and includes newinstall.sh, lsstsw, lsst_build, etc.

An explicit description of this will likely be helpful for readers.

The build/packaging system has been assigned to Architecture by default...

I think we should also take this opportunity to question whether this is the right place to draw that line. Specifically, I think it's true to say that Tim has taken the lead on much of this work historically (perhaps leaving aside more long-term-research projects, like BVan on Conda packaging). As he moves into the Middleware Manager position, is that still practical? I imagine he'll be pushed for time.

Gabriele has also contributed significantly to lsstsw and newinstall recently.

i have made this more explicit in SQUARE and DM Sys Eng  – I believe this is then good to go (for this version).