[bisq-network/proposals] Role owners should itemize compensation on a per-role basis in monthly compensation requests (#30)

Christoph Atteneder notifications at github.com
Thu Jul 12 10:21:59 UTC 2018


> @bisq-network/desktop-maintainers. The primary duties of this role include merging pull requests after sufficient review, triaging incoming issues, and performing releases. If, as the roles doc stipulates, we separate out development and review activities from this role, and itemize them as normal (non-role) contributions, do you still feel it would be necessary to "track in detail" your efforts on this role? 

The problem is that I track my development efforts atm per release including the efforts as desktop maintainer (merging PR, issues management, release tasks) and reviewing PRs. So the issue is not so much about tracking the exact efforts of the desktop-maintainer role, but more on separating it from every other contribution in the bisq-desktop repository, as I'm working on multiple bug fixes & features in parallel. Of course we don't want to value work based on time spent, but it helps to put a price label on something. Doing it just after you've completed work, results in my experience in either under- over overvaluing of completed work packages.

And that is just one of the roles I'm having (of course it is the one which consumes most of my time). So for every other role I have to track the efforts there as well, to be able to come up with a proper valuation. Of course maybe we can find a monthly compensation value for each role, which would make it easier to create compensation requests each month. I just didn't used a flat fee each month for each roles so far as the time that I'm able to contribute varies a lot between months atm.

-- 
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/30#issuecomment-404465423
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180712/189b88cc/attachment-0001.html>


More information about the bisq-github mailing list