[bisq-network/compensation] For May 2018 (#71)

[Chris Beams]

Note that I'm not saying that you shouldn't claim this amount of BSQ, but that how we account for it matters.

The fact is that you're doing work that is presumably required in order to produce some end result of finished work to users. Should this work be accounted for when that end work gets produced? That might be hard to keep track of which conversations with which contributors led to which work getting done. So that might not be feasible. Should it be accounted for as part of the work of being a 'Maintainer' for different given repositories and projects? That might work well. It's pretty easy, because if we route Slack conversations and GitHub issues well, all the conversations you're having with contributors should already be pretty well aligned with the roles you play, e.g. being one of the @bisq-network/exchange-maintainers. And it would be pretty useful to how much of this kind of cost is going into each of our different roles. We could ask why some are so much more expensive than others, and we could share knowledge about how to transfer information faster, create better onboarding experiences for new contributors, better build dev environment rollouts, whatever helps.

-- 
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/71#issuecomment-393931662
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180601/132ff74a/attachment-0002.html>