[bisq-network/compensation] [WIP] For Cycle 12 (#538)

Chris Beams notifications at github.com
Thu Apr 16 18:57:19 UTC 2020


> @cbeams I have the electrum wallet ready to make the payment, had a call with sentineo to make the first steps with him but we still had some doubts about a few things. You mentioned that I should always do the reimbursement in btc correct? or will the bsq ones get refunded by the DAO.

I need to walk through a specific case here to figure out what the right thing to do is. Please schedule some time with me. Monday 8a-11a CET are my next available times. I'll ping you in Keybase about this.

Also, a correction for this section of your compensation request:

> Mediator: [bisq-network/roles#83](https://github.com/bisq-network/roles/issues/83) (comment) 1000 USD
> Fee Reimbursement Agent: [bisq-network/roles#76](https://github.com/bisq-network/roles/issues/76) (comment) 0 USD
> L1 Support Agent: [bisq-network/roles#64](https://github.com/bisq-network/roles/issues/64) (comment) 500 USD

The links you're providing there are links to the role issue itself, but you'll notice that the "(comment)" part, which should be part of the link, is actually just plain text. The reason you see this in other folks' compensation requests is because they're linking to a specific comment on the role issue—a cycle report comment. Here's one from one of the roles I play: https://github.com/bisq-network/roles/issues/16#issuecomment-613295763. Now, the link you see there is nice and short and presents cleanly with the (comment) suffix, but the actual URL I pasted into this comment was `https://github.com/bisq-network/roles/issues/16#issuecomment-613295763`. GitHub shortens this link on your behalf and turns it into that more readable format. Looking at the "Contributions Delivered" section of your compensation request, you're providing a lot of detail about the different roles you play. These are better reported in cycle report comments on the role issue itself. You'll see this is how other folks do it. It keeps too much information from being siloed in the compensation requests, and puts them in the role issues themselves, which are much more useful and convenient for people to look through to see what's going on with a particular role. In the case of the Mediator role, for example, there are multiple people playing that role, so when each one of them does a cycle report on the role issue, you get this nice effect of seeing everybody's info together in one place, e.g. how many cases they handled, which were the most common bugs causing problems, etc. This is all documented at https://docs.bisq.network/roles.html#reporting (though a few things there are slightly out of date).

-- 
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/538#issuecomment-614836161
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200416/777ceb3f/attachment.html>


More information about the bisq-github mailing list