Skip to content
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

For Cycle 24 #842

Closed
pazza83 opened this issue May 6, 2021 · 9 comments
Closed

For Cycle 24 #842

pazza83 opened this issue May 6, 2021 · 9 comments
Assignees
Labels
parsed:valid https://bisq.wiki/Compensation#Ensure_your_request_is_valid team:growth https://bisq.wiki/Growth_Team team:support https://bisq.wiki/Support_Team was:accepted Indicates that a compensation request was accepted by DAO voting
Milestone

Comments

@pazza83
Copy link

pazza83 commented May 6, 2021

Summary

Contributions delivered for Cycle 24

Add contributions you have delivered 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 bisq-network/roles#38 (comment) This is progressing well, more comments below and on report
Support Agent *Support 500 bisq-network/roles#64 (comment) I am enjoying the role and feel like I am getting positive responses from traders I help

Request for feedback

I have now been contributing for Bisq for 6 months 🙂

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 and compensation only for work that has been delivered.

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.

Compensation for the payment maintainer has not been defined. I made the following comment in my first compensation request for the role here:

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, 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). 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. 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) I created a MVP approach Add Buy-Monero Keybase channel on Bisq for fiat trading pairs using BSQ bonds as the security deposit. 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 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 which I have accepted, and if approved I will start next cycle.

@ghost ghost added parsed:valid https://bisq.wiki/Compensation#Ensure_your_request_is_valid team:growth https://bisq.wiki/Growth_Team team:support https://bisq.wiki/Support_Team labels May 6, 2021
@m52go
Copy link

m52go commented May 7, 2021

Approved.

From my perspective, the payment methods maintainer role is hard to evaluate because most work isn't delivered in the form of merged code or other tangible deliverable, and in addition, pazza83 is approaching the role with a relatively long time horizon. So while there aren't really any concrete milestones that directly justify the compensation...there is a well-defined process and timeline for the broader goals, and work is being approached systematically and thoroughly.

By approving compensation in this manner, it's fair to say we're trusting that all the groundwork pazza83 has been doing (and will be doing for the next couple of cycles) will translate into a pile of new payment methods implemented by the end of the year. This is not a customary way of going about compensation. But given pazza83's overall dedication to the project so far, and to this role in particular, I think it's a fair bet for the DAO to make.

Interested to hear others' feedback on compensation for the payment methods maintainer role, if any...pazza83's request was almost rejected last cycle, so if there are any objections to his requests for this role, how he's going about it, how it's being compensated, or any other work, please speak up.

@cbeams
Copy link
Member

cbeams commented May 7, 2021

I think there's a lot of value in having a proactive payment method owner, and so long as progress continues, I think the proposed compensation scheme is reasonable. Like @m52go, I make this assessment based heavily on @pazza83's demonstrated dedication to the role. The context and particulars matter here.

@MwithM MwithM added this to the Cycle 24 milestone May 7, 2021
@MwithM
Copy link
Contributor

MwithM commented May 7, 2021

I find your approach too methodical and a little bit slow, but that's just because I would not be able to do it that way.
It looks like all this process is giving some new promising and unknown (to me) payment methods for Bisq and the thorough process to include them makes me confident that they are secure and Bisq won't have to remove them.

@leo816
Copy link

leo816 commented May 10, 2021

@pazza83 I think you have shown to be committed to bisq and have been working really well throughout this semester, giving a lot of insight as to how we could improve on the support team and in general. I agree with @m52go 's assessment on the maintainer role in the sense that It's not how we normally go about compensation but I believe this will be a good incentive for you and will help bisq scale in the long run.
Reviewing all of your work so far and your ongoing initiative, you also have my approval.

My Team Lead review is complete and I approve this request. Please submit your DAO proposal and paste the transaction ID here as a comment when complete, thanks.

@pazza83
Copy link
Author

pazza83 commented May 10, 2021

Thanks for for all the feedback much appreciated.

I understand the DAO is placing their trust in me to deliver on the payment methods. I will continue to work hard to re-pay the trust and ensure the work is delivered.

Tx ID: 05a951b589975512d8b688f05026598e694e46bfa9467eaf263fdf4605529ca1

Hoping it confirms in time!!

@m52go
Copy link

m52go commented May 13, 2021

I find your approach too methodical and a little bit slow

For the record, I agree and I shared this with pazza on our call -- we had a very enthusiastic market maker in Kuwait appear weeks ago who's probably already long gone, people in India asking about UPI all the time, etc...not sure the long drawn-out approach is worth it. pazza is convinced it is, and no one has suggested anything better (aside from shortening time period for feedback) so it is what it is.

@pazza83
Copy link
Author

pazza83 commented May 13, 2021

Thanks for the feedback.

I agree the process takes time. I disagree that anything has been done too methodically.

It would be great to be as responsive as possible to the needs of market makers and users in getting payment methods added. Being responsive enough to add a payment method quickly requires dev involvement as well as myself.

The reality of adding payment methods to take are that they take time. Take SWIFT for example that was recommended to be added 20th December 2020 and is still with devs.

Recognizing the limitating factors to add new payment methods would be the available dev resources I am working to make everything as easy as possible for them to get the new payment method added. This includes figuring out all the variables, designing the UI and noting any non-custom requirements.

23 payment methods have been completed and are at this stage. A rough price for the dev work to add each payment method has been agreed and all the resources are in place for them to be added. This batched process should hopefully mitigate the limitations of dev time.

I remain flexible in my approach and will adapt to take on board any feedback, suggestions, and changes in resources.

@MwithM MwithM added the was:accepted Indicates that a compensation request was accepted by DAO voting label May 18, 2021
@ghost
Copy link

ghost commented May 18, 2021

Issuance by Team:

team amount BSQ amount USD
growth 416.67 1000.00
support 208.33 500.00

Total Issuance: 625.00 BSQ (equivalent to: 1500.00 USD)

@MwithM
Copy link
Contributor

MwithM commented May 18, 2021

Closed as accepted.

@MwithM MwithM closed this as completed May 18, 2021
@pazza83 pazza83 mentioned this issue Jun 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
parsed:valid https://bisq.wiki/Compensation#Ensure_your_request_is_valid team:growth https://bisq.wiki/Growth_Team team:support https://bisq.wiki/Support_Team was:accepted Indicates that a compensation request was accepted by DAO voting
Projects
Archived in project
Development

No branches or pull requests

5 participants