-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Budget #200
Comments
@wiz |
It's just the budget, of course you can request lower if you want. Thanks burning man! |
@wiz, it looks like we've already got pretty good consensus to approve this, but it might be worth submitting it as a DAO proposal just to make it official and to make sure everybody got their eyes on it. Do you plan to do that? |
Also, I'd say let's lower the burning man budget down to $250 based on @burningman2's comments. No need to have this extra float in the budget if it's not going to get claimed. It might find better uses. Plus, we all need to think about ways to trim the budget after the April security incident. |
@cbeams I made the edit you requested, and since since there was no objections I think we can consider this proposal as accepted. In any case, once we get a Support Team Lead, they will be in charge of the budget, so this was only a temporary thing for the cycles where we had no Support Team Lead. |
I've added the |
@bisq-network/support
@bisq-network/support-agents
@bisq-network/l1-support-agents
@bisq-network/refund-agents
@bisq-network/intern-support-agents
I propose to fix the compensation for Support team members as follows
refund agent: 1000 USD
burning man: 250 USD
mediators: 1000 USD
support agents: 500 USD
support interns: 0 USD
The previous per-case compensation disincentivizes support team members from reporting/fixing bugs because it would reduce their salary, but flat-rate compensation incentivizes support team members to report/fix bugs to get their case load down. We should always try to make incentives in Bisq align properly as much as possible.
The text was updated successfully, but these errors were encountered: