[bisq-network/compensation] For April 2018 (#64)
notifications at github.com
Tue May 8 10:50:09 UTC 2018
Thanks, @Emzy. Some feedback:
> Per https://github.com/bisq-network/proposals/issues/13, please write up your comments about each role you play as a comment on the respective role issue. I just wrote very similar feedback to @mrosseel in https://github.com/bisq-network/compensation/issues/63#issuecomment-387346124, so I'll just quote it below (with some slight modifications):
> Rather than grouping stuff into a single 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
> - Mailman Operator at https://github.com/bisq-network/roles/issues/26
> 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.
Many thanks in any case for all the operations work you're doing here. I think no one outside of Manfred is hosting more nodes than you. Hopefully the changes described above can help in our efforts to decentralize this work further.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the github