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

Chris Beams notifications at github.com
Fri Jun 1 16:14:26 UTC 2018


> communication with contributors

Is this [delivered](https://github.com/bisq-network/proposals/issues/19) work? I don't think we've addressed it explicitly anywhere. It's a tough call. You could make the argument that it's directly valuable work on its own, and you could make the argument that it's all part of the process of delivering finished work to end users.

I tend toward the latter definition. That it is a cost of collaborating effectively, not an end-user good on its own. From a paying and/or stakeholding Bisq user's perspective, I want there to be as little "communicating with contributors" as possible required in order to produce valuable features. I certainly don't want to economically incentivize the act of "communicating with contributors" _per se_; I want to incentivize the delivery of useful software into my hands. So from this perspective, as a Bisq user, I would want Bisq contributors to bundle their time and effort into their compensation requests in an undifferentiated way. This will allow me to vote consistently for the work that delivers more value at less overall cost, thereby rewarding very efficient contributors who don't require a lot of "communicating", or more precisely, require a minimum of it when compared with other contributors.

-- 
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-393930039
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180601/456e634b/attachment-0002.html>


More information about the bisq-github mailing list