it is important to explicitly flag that the purpose of the practices repo is, and should never be, to ASSESS anybody based on the responsibilities stated.
The purpose is, rather, to empower our tech team with the tools needed to communicate and take ownership of their repositories and the changes made to them.
e.g. We should never say "Hey, you are the maintainer of this repository and there are 10 issues open, you are bad!
But rather, in a PR review, say "as per this definition of maintainer, i do or don't want to approve it, blah blah"
@jdhoffa to elaborate on this issue