Some discussion with Parejkoj:
- The procedure in DMTN-027 involves forking the package to another team, then carefully juggling the packages so that the two copies are never in the same place (I assume GitHub will choke on two forks having the same owner?). This is problematic in our case because we want the "active" package to be in lsst-dm, and don't have a good place for the archival copy.
- According to Parejkoj, the motivation for the forking is so that lsst_distrib doesn't break while we're in the process of renaming the package and adding the new package name to repos.yaml. Since we're not part of lsst_distrib, that problem doesn't apply to us.
- GitHub's redirects should take care of other references to the old package name, including working copies.
Therefore, I will follow a modified version of DMTN-027 that does the package rename in place, but still follows the remaining parts of the procedure (commit patterns, repos.yaml, documentation, etc.).