At the Toolchain Summit this year, one of the discussion sessions was to reflect on how the
DBIx::Class ownership conflict was handled. We didn't only discuss DBIx::Class, but how a range of other situations were handled. One of the outcomes of that session was a request that the PAUSE admins document the rules and principles for how PAUSE is operated, and how various situations are, or will be going forward, resolved.
Since then the PAUSE admins have been discussing various scenarios and gradually working on a document which we ended up calling the PAUSE Operating Model. The name reflects that it not only describes how PAUSE works, but how the PAUSE admins run the service.
The rest of this post gives an outline of what the document covers, and where you can read it.