[bisq-network/roles] Roles Maintainer (#28)

[Chris Beams]

## Cycle 12 report

As per the comments above, I've taken over this role from @m52go. In practice, I'm most often the one making changes to roles and their GitHub teams, etc. The role is well aligned with also playing the role of GitHub Admin, as some operations require GitHub organization Owner access. 

The main change that's been made recently with roles is the addition of roles for each of the team lead positions (bisq-network/admin#31). I've also slowly been creating stub documentation on the wiki for each role. Role issue descriptions have been updated to reflect this.

We need to get to a place where owning a role means owning and keeping up to date the documentation for that role. This has always been the idea, but it's never been fully implemented. It's important that contributors feel they can rely on accurate documentation for each role, both to assess whether a contributor is properly fulfilling the duties of that role (and therefore eligible for compensation), and it's also important from the perspective of transferring role ownership from one person to another. We want to be in a place where it's possible for someone to take over a role and rely on the documentation being there that tells them what needs to be done. There will always be a human aspect to these kinds of transfers, but writing stuff down is important in order to avoid siloed knowledge.

/cc bisq-network/compensation#533

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/28#issuecomment-613852280
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200414/1da8e605/attachment.html>