[bisq-network/compensation] For Cycle 24 (#842)

[m52go]

[Approved](https://bisq.wiki/Compensation#Team_Lead). 

>From my perspective, the payment methods maintainer role is hard to evaluate because most work isn't delivered in the form of merged code or other tangible deliverable, and in addition, pazza83 is approaching the role with a relatively long time horizon. So while there aren't really any concrete milestones that directly justify the compensation...there is a well-defined process and timeline for the broader goals, and work is being approached systematically and thoroughly. 

By approving compensation in this manner, it's fair to say we're trusting that all the groundwork pazza83 has been doing (and will be doing for the next couple of cycles) will translate into a pile of new payment methods implemented by the end of the year. This is not a customary way of going about compensation. But given pazza83's overall dedication to the project so far, and to this role in particular, I think it's a fair bet for the DAO to make.

Interested to hear others' feedback on compensation for the payment methods maintainer role, if any...pazza83's request was almost rejected last cycle, so if there are any objections to his requests for this role, how he's going about it, how it's being compensated, or any other work, please speak up.

-- 
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/842#issuecomment-834053820
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210506/bd5b9c80/attachment.htm>