[bisq-network/roles] Support Maintainer (#76)

[Chris Beams]

## 2018.10 report

@KanoczTomas stepped up this month to help process a months-long backlog of reimbursement requests, and as mentioned in his compensation request at https://github.com/bisq-network/compensation/issues/152, he offered to take on a dedicated role for doing this kind of work. So I'll transition primary ownership of this role to him over the next month.

Tomas, I'd suggest reading https://docs.bisq.network/roles.html#maintainer. I'll grant you write access to this repository so you can properly handle the issues, e.g. assigning and labeling them, etc. Otherwise, there's not much to be done other than handling incoming reimbursement requests. I think it's an open question whether this repository should handle anything else, e.g. other support issues. We have the forum for that, and more technical support requests often end up in the main bisq-network/bisq repository, which isn't necessarily a bad thing. In any case, as maintainer, you'll be free to work with the main repo maintainers and suggest what you think makes sense.

Also please read https://docs.bisq.network/roles.html#reporting and follow the instructions there starting with next month's compensation request cycle.

It's a good idea to read the whole roles doc, actually, so you've got full context.

In any case, if that all goes smoothly, I'll fully hand over primary ownership of this to you next month. Please let me know what you need in the meantime, thanks!

BSQ Requested: `25`

/cc bisq-network/compensation#160

-- 
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/76#issuecomment-434836367
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20181031/9fe8d491/attachment.html>