[bisq-network/compensation] For Cycle 23 (#826)
pazza
notifications at github.com
Mon Apr 5 19:29:53 CEST 2021
<!--
Compensation requests have a specific format that enables them to be evaluated by a bot for more efficient budgeting. Please make sure you stick to the template. A linter will evaluate your request after you remove [WIP] from the issue title and notify you of any issues.
See the following link for details:
https://bisq.wiki/Making_a_compensation_request
Feel free to browse other requests if you're not sure about something, or reach out in #compensation on Keybase (https://keybase.io/team/bisq).
-->
## Summary
- **BSQ requested**: **`[688.07]`**
- USD requested: [1500]
- BSQ rate: [2.18 USD/BSQ] USD per BSQ as per #805
- Previous compensation request: #798
## Contributions delivered for Cycle 23
> _Add contributions you have [delivered](https://github.com/bisq-network/proposals/issues/19) and roles you have performed here as new rows in the table below. Role line-items should include an asterisk (*) in the team column._
Title | Team | USD | Link | Notes |
| --- | --- | --- | --- | --- |
| Payment Maintainer Role | *Growth | 1000 | https://github.com/bisq-network/roles/issues/38#issuecomment-813519670 | All going well. Major challenge to resolve is what happens with account limits as BTC price increases |
| Support Agent | *Support | 500 | https://github.com/bisq-network/roles/issues/64#issuecomment-813469809 | Everything going well, I am enjoying the role, and the support calls have been really helpful |
## Future potential work in progress
I have agreed to project manage the [new-user-onboarding and new user interface design](https://github.com/bisq-network/projects/issues/49) this looks likely to proceed to it's first stage of developing the GUI for new user onboarding.
I have suggested the following project for discussion: [Add Monero to fiat trading pairs using BTC as the security deposit (multi-sig)](https://github.com/bisq-network/projects/issues/50) thoughts on how this can be achieved are welcome as I see it as a good opportunity for Bisq.
I have also started working on [running the numbers on Bisq DAO revenues](https://github.com/bisq-network/bisq/discussions/5171). Hopefully will have some figures for review/discussion next cycle.
<!--
Each contribution should be a new line-item in the table above.
Title - optional, string.
Team - optional, must one of the following: admin, dev, growth, ops, support (case-insensitive). If the line-item is for a role, please add a `*`. See Example 2 below.
USD - optional, number. Please do not specify 'USD', as the column title makes units clear.
Link - optional, string.
Notes - optional, string.
Example 1 - typical contribution:
| Add local Bitcoin node configuration detection | dev | 240 | https://github.com/bisq-network/bisq/pull/3982
Example 2 - role (note the asterisk):
| Community manager | growth* | 400 | https://github.com/bisq-network/roles/issues/95#issuecomment-628431613
Example 3 - list of minor contributions, such as reviews:
| | | | https://github.com/bisq-network/bisq/pull/3968 | This and PRs below too small to be valued separately. See total at bottom.
| | | | https://github.com/bisq-network/bisq/pull/4040
| | | | https://github.com/bisq-network/bisq/pull/4044
| | | | https://github.com/bisq-network/bisq/pull/4048
| | | | https://github.com/bisq-network/bisq/pull/4066
| | dev | 400 | https://github.com/bisq-network/bisq/pull/4062 | Total for items above.
-->
--
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/826
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210405/f6d922d1/attachment.htm>
More information about the bisq-github
mailing list