Module owners and peers

Community Ops
#1

I was just having a chat with @mrz on IRC, and he mentioned how we need to formalize the idea of module owners and peers.

Specifically, we should figure out (and document) the roles and responsibilities of module owners and of their peers. Whom do we contact in case of an issue with the site? What kind of access are the peers expected to have for the given module? Etcetera.

Also, there’s the question of how people become owners and peers. Do we continue just self-appointing (or appointing by the module owners)? Should there be some kind of vote?

I’d definitely appreciate @majken’s input on this, as well as that of anyone else who contributes to Community IT.

#2

I’d suggest we add ideas to https://communityit.etherpad.mozilla.org/modules

#3

It’s a bit chicken and egg, but I would say we should have our policy
discussions first. That will help define the responsibilities that will
then belong to owners and peers. Ideally owners and peers will also meet
our policy requirements for being admins.