Fee Reimbursement Agent

cbeams commented 6 years ago

Docs: https://bisq.wiki/Fee_Reimbursement_Agent Team: @bisq-network/fee-reimbursement-agents

cbeams commented 6 years ago

2018.07 report

Nothing to report.

BSQ requested: 25

/cc bisq-network/compensation#101

cbeams commented 6 years ago

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

cbeams commented 6 years ago

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

cbeams commented 6 years ago

2018.10 report

@KanoczTomas stepped up this month to help process a months-long backlog of reimbursement requests, and as mentioned in his compensation request at https://github.com/bisq-network/compensation/issues/152, he offered to take on a dedicated role for doing this kind of work. So I'll transition primary ownership of this role to him over the next month.

Tomas, I'd suggest reading https://docs.bisq.network/roles.html#maintainer. I'll grant you write access to this repository so you can properly handle the issues, e.g. assigning and labeling them, etc. Otherwise, there's not much to be done other than handling incoming reimbursement requests. I think it's an open question whether this repository should handle anything else, e.g. other support issues. We have the forum for that, and more technical support requests often end up in the main bisq-network/bisq repository, which isn't necessarily a bad thing. In any case, as maintainer, you'll be free to work with the main repo maintainers and suggest what you think makes sense.

Also please read https://docs.bisq.network/roles.html#reporting and follow the instructions there starting with next month's compensation request cycle.

It's a good idea to read the whole roles doc, actually, so you've got full context.

In any case, if that all goes smoothly, I'll fully hand over primary ownership of this to you next month. Please let me know what you need in the meantime, thanks!

BSQ Requested: 25

/cc bisq-network/compensation#160

cbeams commented 5 years ago

2018.11 report

@KanoczTomas continued to manage the support repository this month, and is now putting together the next batch reimbursement at bisq-network/support#147.

@KanoczTomas, I'd like to make you the primary owner of this role, which would mean doing what you're already doing, plus posting a report like this one here each month. Are you OK with that?

BSQ requested: 25

/cc bisq-network/compensation#179

KanoczTomas commented 5 years ago

@cbeams ok, I am fine with it. I am taking the role and will write the report for december when the time comes.

cbeams commented 5 years ago

Per https://github.com/bisq-network/roles/issues/1#issuecomment-444857417, I'll be away for the next ~2 months. @KanoczTomas has already agreed to take on ownership of this role, and I'm un-assigning myself from it now.

KanoczTomas commented 5 years ago

2018.12 report

There were 17 reimbursements opened for month december which were compensated by #173

BSQ Requested: 25

/cc https://github.com/bisq-network/compensation/issues/201

ManfredKarrer commented 5 years ago

Thanks a lot @KanoczTomas! Very appreciated that you took over responsibility for that task!

KanoczTomas commented 5 years ago

2019.01 report

There are 8 issues with reimbursements opened for month January which will be compensated by #195. There are 60 transactions in this batch totaling 0.09307566 BTC.

BSQ Requested: 25

/cc https://github.com/bisq-network/compensation/issues/201

KanoczTomas commented 5 years ago

2019.02 report

There 3 staged issues and 2 waiting for input from user. They will be reimbursed with #200.

BSQ Requested: 25

/cc https://github.com/bisq-network/compensation/issues/221

KanoczTomas commented 5 years ago

2019.03 report

Processed 12 reimbursement requests in this batch totalling 0,013346 BTC. Reimbursed via #200

BSQ Requested: 600

*note I had a feedback to raise my requested amount as previous requests were undervalued by myself. 600 is a compensation for last requests as well.

/cc https://github.com/bisq-network/compensation/issues/237

wiz commented 4 years ago

@KanoczTomas are you still performing this role? there are many issues in the support repository piling up and it seems you haven't filed a monthly report for the Support Maintainer role in a year...

cbeams commented 4 years ago

@KanoczTomas will do a call to hand off this role to @leo816. Scheduled for 2020-03-27. Afterward, @leo816 will assume this role (and we'll probably rename the role as well).

cbeams commented 4 years ago

I've renamed this role from Support Maintainer to Fee Reimbursement Agent to better reflect its exact nature. The handoff of this process from @KanoczTomas to @leo816 is complete, and @leo816 has prepared the batch reimbursement at bisq-network/support#366, which is now ready to be paid out.

@leo816, could you please own documenting this role? i.e. getting something on the wiki that captures how this work is actually performed? There are docs in various stages of completion (see the description above), and a number of things have changed with the introduction of @KanoczTomas automation scripts. The documentation doesn't necessarily need to be step-by-step detailed for a start, but it would be good to have something in place that captures the basics.

cbeams commented 4 years ago

@leo816, as you may have noticed, fee reimbursement issues have been getting automatically added to the Case Tracking project board, which is not what we want—they should get added to the Fee Reimbursement project board. The reason for this was a GitHub Action workflow that wasn't smart enough to distinguish between the two issue types. I've just removed this workflow in c05825098ecfbd149a0ef87ee0cee28208a58253, meaning that issues will have to be added to their respective boards manually from this point forward.

Could you please go through the outstanding fee reimbursement issues and remove them from the case tracking board and add them to the fee reimbursement board?

And can you also make sure you're watching this repository so you get notified of new incoming issues? When new fee reimbursement issues come in, you should (a) assign them to yourself and (b) add them to the fee reimbursement board. This would be something to document in the wiki as duties this role is responsible for and/or as part of the overall fee reimbursement process documentation. Thanks.

leo816 commented 4 years ago

Cycle 13 report

Made the Fee Reimbursement for all the cases pending from October: https://github.com/bisq-network/support/issues/366#issuecomment-625274968
Payout of 0.01189702 BTC to users = 0.01189702/ 0.00007889 = 151 BSQ
created the first draft for the Fee Refund Agent role (https://bisq.wiki/Fee_reimbursement_agent)

leo816 commented 4 years ago

Cycle 14 report

Have processed 49 Fee reimbursement issues and will make the payout in the following days.
Some fee reimbursements were missing information and there are some technical issues I will solve with the previous owner of the role.
Continued editing the Fee reimbursement role on the bisq.wiki

cbeams commented 4 years ago

Nit: Please use H2 headings (##) in cycle reports, and do not put empty lines in-between bullet points. See my edits to the comment above.

leo816 commented 4 years ago

Cycle 15

Made the Fee Reimbursement for all the cases pending. (44 trades): https://github.com/bisq-network/support/issues/430#issuecomment-660882774
Payout of 0.0653368 BTC to users. 0.0653368/0.00006397= 1021 BSQ

leo816 commented 4 years ago

Cycle 16

There has been some new technical issues regarding the new batch reimbursement and a meeting has been scheduled for next Thursday 27th of August with the previous role holder. The Payout will be made next cycle.

leo816 commented 4 years ago

Cycle 17

Made the Fee Reimbursement for all the cases pending. (39 trades): https://github.com/bisq-network/support/issues/481#issuecomment-699182913
Payout of 0.02572339 BTC to users. 0.02572339/0.00006185= 416 BSQ

leo816 commented 4 years ago