[bisq-network/proposals] Change policy for compensation requests (#38)

[Manfred Karrer]

After discussions and feedback from various contributors I think there are several good reasons to rethink our current policy that requests are only done for shipped code. 

As we have seen with the long lasting projects the current policy comes with several drawbacks.

- Waiting long time will make valuation harder as the contribution is further back in memory. To evaluate a huge chunk of work would also take then much more time as not all is remembered as fresh as at the end of a one months work.
- Having a monthly compensation gives higher motivation to contributors as it would be if the compensation comes after several months
- Adding up a lot of such requests can end up in a very large request which will be harder to evaluate
- It is less risky for both sides if requests are done earlier with smaller amounts in case expectations are different for any of the sides.
- Code which is in master is accessible for those who run from source code, so the shipping definition is not constrained to the binary shipping only.

I would suggest that we change the current policy from "being shipped" to "being merged to master". I think that still holds the goal that we don't spend funds on work which might never lead to value for a user but reduces delays, gives more motivation and reduces risks. 

@cbeams What do you think?

-- 
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/proposals/issues/38
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180830/119ab200/attachment.html>