[bisq-network/compensation] For April 2018 (#63)

[Chris Beams]

Thanks, @mrosseel. Some feedback:

Rather than grouping stuff into a single "Hosting" section directly within your compensation request, please post a monthly update comment on each of the respective roles, e.g.:

 - Pricenode Operator at https://github.com/bisq-network/roles/issues/14
 - Seednode Operator at https://github.com/bisq-network/roles/issues/15
 - Bitcoin Node Operator at https://github.com/bisq-network/roles/issues/67
 - Monitoring Operator / Maintainer at https://github.com/bisq-network/roles/issues/10

Doing things this way maximizes the usefulness of these reports over time. Mostly, people will not go digging through individual compensation requests to see who has been hosting what, or how much they paid to host those things on various hosting providers. But if all operators consistently post monthly report comments on their respective operator role issues, it becomes very easy for operators new and old alike to see who is hosting what where, which hosting providers are overused from a a censorship resistance / network resiliency perspective, which contributors are overloaded / operating too much stuff, to evaluate which hosting providers are delivering the best "bang for the buck", etc.

Also in the "Roles" section of future compensation requests, please name the role as well as linking to the monthly report comment, so that voting stakeholders can see at a glance what roles you played, and which they wish to click on and review. For example:

> - Freenode Admin: https://github.com/bisq-network/roles/issues/22#issuecomment-385487001

-- 
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/compensation/issues/63#issuecomment-387346124
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/github/attachments/20180508/fffaf53b/attachment.html>