Before I found this issue, I added a brief note to Confluence myself. Joshua Hoblitt may wish to expand, correct or replace what I've written.

I swear added a blurb to developer guide long ago but it appears to have been lost...

Looks like my blurb has been lost to the either. John Swinbank thanks for putting those notes together – I don't think I can add much to that.

Jonathan Sick Do you want to sit down at some point to go over what John Swinbank posted?

I'd prefer to have the policy/procedure documents be self-contained rather than referring to RFCs (except perhaps for reasoning or background), so I think John Swinbank's modification still needs to be expanded a bit.

Sorry, I just found this ticket. Yes, the self-merge policy is technically documented in https://developer.lsst.io/build-ci/new_package.html :

The new package must be added to the etc/repos.yaml file in the lsstsw package along with its corresponding GitHub URL. This file is governed by a “self-merge” policy: upon opening a pull request, it will be checked by the Travis CI system, and developers may merge without further review on success. Refer to RFC-75 for background.

But I think I can restructure that page a bit to make the process easier to follow and have policies more clearly defined. I'll take the ticket on.

This has been done already: see https://developer.lsst.io/stack/adding-a-new-package.html