bisq-network / roles

@bisq-network contributor roles
https://bisq.wiki/Roles
16 stars 16 forks source link

Compensation Maintainer #86

Open m52go opened 5 years ago

m52go commented 5 years ago

Docs: https://bisq.wiki/Compensation#Compensation_Maintainer Team: @bisq-network/compensation-maintainers

MwithM commented 4 years ago

Cycle 5 report: Close all Compensation Requests for Cycle 5 and below, more than 40 total. Request 2 CR to change to Cycle 6 because they didn't submit their CR to the DAO, then manually closed due to inaction. Request #367 to change title.

MwithM commented 4 years ago

Cycle 7 report:

Closed all CR except #399, which is left open for discussion. #389 was not available to vote. Updated USD/BSQ rates for cycle 8.

MwithM commented 4 years ago

Closed all CR except rejected #446, #431 and #417, which are left open a while for discussion. Updated USD/BSQ rates for cycle 9.

MwithM commented 4 years ago

Closed all CR except rejected #453, #455 and #462. Apparently, #456 forgot to send CR to DAO voting. Updated USD/BSQ rates for cycle 10.

cbeams commented 4 years ago

I've updated the description of this role to include a link to the new compensation maintainer role documentation at https://bisq.wiki/Compensation#Compensation_Maintainer, which @MwithM has been putting together in bisq-network/admin#32.

MwithM commented 4 years ago

This cycle had more to do because of changes described on earlier post. I helped to write compensation wiki and it took a little effort to understand the new process, but the overall view is very positive. All compensation requests were accepted, and the new compensation board has been managed without remarkable issues. New rates and expected delivery times for new requests have been announced on the board, and I still have to send a message to all contributors announcing when should they submit their proposals.

MwithM commented 4 years ago

Cycle 11 report

All compensation requests were accepted except one previously withdrawn. In general, the process has been followed without remarkable issues, from mine or contributor's end.

There might be a change in the way BSQ price is calculated already in cycle 12, using volume weighted average price. Discussion is encouraged and if the change is finally made, I'll try to keep every contributor informed.

Edit: I added 20USD to the price of my compensation request of 100USD because due to mempool congestion, I spent about 15USD in mining fees to send 4 DAO trading fee change parameter proposals.

MwithM commented 4 years ago

Cycle 12 report

The 90 day USD volume weighted average have been used for compensation request USD/BSQ rate, and it will be for next cycles. At this moment, there's no proposal to use the 30 day average instead of the 90 day, and I'm not going to create it because I don't have strong arguments in favor of that change.

3 contributors did not submit their compensation request on time, they submitted it after the proposal phase expired. 3 compensation requests have been rejected, all related to translation. The rest of the 23 compensation requests have been accepted.

There was no need to update the BSQ discount.

cbeams commented 4 years ago

@MwithM, per https://github.com/bisq-network/roles/issues/102#issuecomment-644737088, please assign all support team compensation requests to @leo816 instead of myself, effective immediately in the current cycle (Cycle 14). Thanks!

MwithM commented 4 years ago

Cycle 13 report

21 compensation requests were accepted, 3 rejected and 1 was not submitted (postponed). BSQ trading fee discount was updated and USD/BSQ rate was calculated using the 90 day USD volume weighted average.

cbeams commented 4 years ago

@MwithM, per https://bisq.wiki/Compensation#Announce_request_submission_deadline, a message should be posted to the @bisq-network/dao team with the submission deadline for every cycle. You did this for Cycle 13 here, but I didn't see one for Cycle 14. I imagine this was just an oversight, but it's worth pointing out, because if the only notice that gets posted is the issue here in the compensation repository (which you did create), contributors won't get notified about it unless they've put a watch on the compensation repository. By posting the message to the dao team, every active contributor should get notified. If this is feeling like too much of a hassle to post it in both locations, we could change the duty to state that the compensation maintainter must @mention the @bisq-network/dao team in the compensation repository issue; this would also trigger all dao team members to get notified. Again, I assume this was just an oversight though. Thanks.

MwithM commented 4 years ago

I somehow thought that the parsable compensation request template announcement would help contributors to know the deadline, but anyway the my announcement should be made earlier. I'll just keep making the announcement at the beginning of a new cycle, I didn't do it because i expected miners to advance or delay it significantly.

I've been indicating the deadline to WIP requests individually, but not publishing the deadline is a mistake and I hope noone is injured by it.

MwithM commented 4 years ago

Cycle 14 report

27 compensation requests were submitted. 2 of them rejected and 1 not submitted (deprecated). Deadline for Cycle 15 has been announced at the compensation board and dao discussions. This will be the first Cycle that the parsable format will be mandatory. On cycle 14 it worked fine and it will help to have better info of the work done at the DAO and how resources are used.

MwithM commented 4 years ago

Cycle 15 report

All 25 compensation requests were accepted. BSQ trading fee needed to be updated, and the DAO change paramater was accepted. Parsing bot worked as expected.

MwithM commented 4 years ago

Cycle 16 report

20 compensation requests were created, 19 accepted and 1 not submitted to dao. BSQ trading fee didn't need to be updated.

MwithM commented 3 years ago

Cycle 17 report

26 compensation requests were submitted, only 1 of them was rejected under investigation due to possible DAO issues. https://github.com/bisq-network/compensation/milestone/8?closed=1 BSQ trading fee was not updated.

MwithM commented 3 years ago

Cycle 18 report

MwithM commented 3 years ago

Cycle 19 report

MwithM commented 3 years ago

Cycle 20 report

MwithM commented 3 years ago

Cycle 21 report

MwithM commented 3 years ago

Cycle 22 report

This cycle has been more normal, although the failed 20 cycle still made some contributors lagging in their compensation requests.

MwithM commented 3 years ago

Cycle 23 report

MwithM commented 3 years ago

Cycle 24 report

MwithM commented 3 years ago

Cycle 25 report

MwithM commented 3 years ago

Cycle 26 report

MwithM commented 3 years ago

Cycle 27 report

MwithM commented 3 years ago

Cycle 28 report

MwithM commented 2 years ago

Cycle 29 report

MwithM commented 2 years ago

Cycle 30 report

MwithM commented 2 years ago

Cycle 31 report

MwithM commented 2 years ago

Cycle 32 report

MwithM commented 2 years ago

Cycle 33 report

MwithM commented 2 years ago

Cycle 34 report

MwithM commented 2 years ago

Cycle 35 report

MwithM commented 2 years ago

Cycle 36 report

Lack of quorum could become a big problem if compensation requests, reimbursements or change parameters that need to be accepted are rejected instead although they're not controversial. For compensation requests and reimbursements, min is 20.000 BSQ, which, combined with reputation (earned BSQ) stake, are created every cycle so I don't think that the limit being high is the problem. Incentives for actually voting are. For change parameters, which are critical for the DAO, 100.000BSQ are required, which is less than 3% of the total amount of BSQ created. Maybe wider thresholds for BSQ trading fee updated should be used so updates are less regular, but I don't think that this is the main issue.

MwithM commented 2 years ago

Cycle 37 report

MwithM commented 2 years ago

BTW thanks to all voters on this cycle, participation has increased a lot.

MwithM commented 2 years ago

Cycle 38 report

MwithM commented 2 years ago

Cycle 39 report

MwithM commented 1 year ago

Cycle 40 report

Cycle 40 rate was wrong, I realized about that 1 day past the real deadline. Some contributors weren't able to submit reports on time.

MwithM commented 1 year ago

Cycle 41 report

MwithM commented 1 year ago

Cycle 42 report

MwithM commented 1 year ago

Cycle 43 report

MwithM commented 1 year ago

Cycle 44 report

MwithM commented 1 year ago

Cycle 45 report

MwithM commented 1 year ago

Cycle 46 report

MwithM commented 1 year ago

Cycle 47 report

MwithM commented 1 year ago

Cycle 48 report

MwithM commented 1 year ago

Cycle 49 report

MwithM commented 1 year ago

Cycle 50 report