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

pazza notifications at github.com
Fri May 7 01:58:17 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**: **`[625]`** 
- USD requested: [1500] 
- BSQ rate: [2.4 USD/BSQ] USD per BSQ as per #830
- Previous compensation request: #826 

## Contributions delivered for Cycle 24

> _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-833922953 | This is progressing well, more comments below and on report |
Support Agent | *Support  | 500 | https://github.com/bisq-network/roles/issues/64#issuecomment-833859700 | I am enjoying the role and feel like I am getting positive responses from traders I help |


## Request for feedback

I have not been contributing for Bisq for 6 months :slightly_smiling_face: 

In my last cycle I only just passed over the voting threshold by the skin of my teeth with (50.46%) of the vote. With this in mind, and considering I have now completed the role for 6 months, I thought it would be a good opportunity to get feedback from my team leads for my roles @m52go and @leo816. I had a voice call with @m52go in which we discussed a multitude of things in relation to the role. Part of what we discussed was [compensation requests in general](https://bisq.wiki/Making_a_compensation_request#Eligible_work) and [compensation only for work that has been delivered](https://github.com/bisq-network/proposals/issues/19).

It was my opinion that the definition of 'delivered work' for the role of support agent and payment method maintainer is somewhat different that that of other roles, eg a dev.

>Delivered work is work that:
>users can use immediately because it has been released
>users can figure out how to use because it has been documented
>users know exists in the first place because it has been announced and promoted

Compensation for the support agent role has been established [separately](https://bisq.wiki/Support_Agent#Compensation). 

Compensation for the payment maintainer has not been defined. I made the following comment in my first compensation request for the role [here](https://github.com/bisq-network/compensation/issues/727#issue-751952118):

>It would be good to outline a budget for the Payment Maintainer Role. The amount of work I did this cycle for the role is the maximum I can commit to (leaving space for me to take on a Support Agent role, and future roles I would like to contribute to). Therefore, for the role I would propose a maximum budget of $1,000 USD per cycle. 

I would like to think that the systematic way I am approaching the payment method maintainer role means that I am documenting and promoting my work as I go along. However the work is not yet released for users. This is partly due to me preferring to work systematically though all the payment methods suggested, [approximately 60](https://github.com/users/pazza83/projects/1), rather than taking an unsystematic piecemeal approach to the work and adding payment methods one at a time. 

I definitely think the systematic / batched approach will result in more value to Bisq over the long term. I also think all the work I have done to date adds value to users and contributors in that if I get hit by a bus tomorrow, all my process, recommendations for inclusion, recommendation against inclusion etc have all been documented and are available to be picked up by anyone.

Going forward I expect to continue to request $1,000 USD per cycle for the payment method role for the rest of 2021. This would be a total cost to Bisq of approximately $12,000 USD for the inclusion of 26 payment methods (2 completed and 24 to be delivered). This works out at about $461 USD per payment method. This does not include all the other work I am doing as part of my role ([defined here](https://github.com/bisq-network/roles/issues/38#issuecomment-727760468)). My thought process to date has generally been... There is a lot of work to do for the payment maintainer role, I want to progress it quickly, and I want to deliver at least $1000 of USD value per month for the role. 

The above are however just my opinions and I though it would be good to set out my thoughts so people can ascertain the value being delivered by by contributions. I welcome any feedback from any stakeholders as how I am getting on with the support agent / payment method maintainer roles. I am keen for my contributions to be as effective and as valuable as possible for Bisq.

>From my perspective I am really enjoying the role. I think things are progressing well and coming to the stage where in the next few cycles the fruits of the previous work will be seen with regards to new payment methods added. 

The challenges for me have been communication and the distributed way of working. But this is also a big part of what I have found enjoyable. 

Any and all feedback welcome :)

## Future potential work in progress

I am still negotiating with the UI dev with regards the [new-user-onboarding and new user interface design](https://github.com/bisq-network/projects/issues/49). I am at the stage where I am keen to share their requests for compensation publicly with stakeholders to get feedback. 

Following the creation of the 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) I created a MVP approach [Add Buy-Monero Keybase channel on Bisq for fiat trading pairs using BSQ bonds as the security deposit](https://github.com/bisq-network/projects/issues/56). This is to avoid the need for any dev resources (main stumbling clock of my larger project) to allow me to crack on with it independently.

I got feedback on my work [running the numbers on Bisq DAO revenues](https://github.com/bisq-network/bisq/discussions/5171) from @cbeams but have yet to implement any changes ready for sharing / discussion etc

@MwithM also asked me to take on the [Proposal Maintainer role](https://github.com/bisq-network/roles/issues/30#issuecomment-833839379) which I have accepted, and if approved I will start 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/842
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210506/cc08697c/attachment.htm>


More information about the bisq-github mailing list