|
|
| (20 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | __TOC__
| + | '''Compensation''' is an important element of the [[Decentralized_autonomous_organization|Bisq DAO]] that incentivizes people to contribute to the Bisq software and, over time, enables them to take on a greater stake in its governance. |
| | | | |
| − | == Processes by role ==
| + | This article covers the several parties involved in the process of requesting, approving, issuing, and guiding compensation. |
| | | | |
| − | === Compensation Maintainer ===
| + | __TOC__ |
| − | | |
| − | ==== Announce BSQ-USD exchange rate ====
| |
| − | | |
| − | Since proposal [https://github.com/bisq-network/compensation/issues/114 #114], compensation requests should use a 90 day average to calculate value for BSQ and mitigate its volatility. At the end of a Bisq DAO Cycle and beginning of a new one, Compensation Maintainer should create a pinned issue with the title: <code>BSQ rate for Cycle X is Y.YY USD per 1 BSQ</code> and a screenshot of DAO Dashboard to announce the rates for the ongoing cycle.
| |
| − | | |
| − | ==== Announce request submission deadline ====
| |
| − | | |
| − | To give time for team leads to discuss and review Compensation Requests, requests need to be <code>Ready for review</code> one week prior to the end of current cycle's proposal phase. [[File:Compensation_board.png|400px|right|thumb|Compensation board]]The date and reminders will be announced at [https://github.com/orgs/bisq-network/teams/dao/discussions/ @bisq-network/dao], the [https://github.com/orgs/bisq-network/projects/5 Compensation board] and [https://calendar.google.com/calendar/embed?src=adfiuiokq9jtac8t9keomc00b0%40group.calendar.google.com&ctz=Europe%2FMadrid Events Calendar]
| |
| − | | |
| − | ==== Triage incoming requests ====
| |
| − | | |
| − | The Compensation Maintainer watches the [https://github.com/bisq-network/compensation/issues compensation repository] and proceeds to triage:
| |
| − | | |
| − | Incoming issues are classified as <code>Work in progress</code> if they have <code>[WIP]</code> at the beginning of the title or as <code>In Review</code> if they don't. Compensation Maintainer assigns 'In review' issues to corresponding team leads after looking at the content of the request. When in doubt, Compensation Maintainer should ask in the issue which team leaders are the appropriate for the issue.
| |
| − | | |
| − | The Compensation Maintainer should transition reviewed requests with DAO proposals transaction ID submitted to <code>Proposal Submitted</code> column.
| |
| − | | |
| − | Triage is controlled from the Compensation board, drag-and-dropping issues and using "add cards" to triage incoming issues, and directly from the issues, using the "projects" section in the right sidebar.
| |
| − | | |
| − | ==== Archive previous cycle requests at the end of the proposal phase ====
| |
| − | | |
| − | At the completion of the current cycle's proposal phase, the Compensation Maintainer should [https://help.github.com/en/github/managing-your-work-on-github/archiving-cards-on-a-project-board archive] all issues in the <code>Done</code> column from the previous phase.
| |
| − | | |
| − | The reason for waiting to archive these issues is so that contributors can easily see how many requests were made in the last phase, to quickly find their own prior request, and to to easily review which ones were accepted and rejected. We archive them at the end of the proposal phase in order to keep the board clean and make room for requests in the current phase to populate the <code>Done</code> column.
| |
| − | | |
| − | ==== Close current cycle requests after the vote reveal phase ====
| |
| − | | |
| − | When the reveal vote phase is complete, the Compensation Maintainer should take the following steps:
| |
| − | | |
| − | # Label each compensation request issue as <code>was:accepted</code> or <code>was:rejected</code> according to the vote result
| |
| − | # Close the issue with a comment that reads "Closing as accepted" or "Closing as rejected".
| |
| − | | |
| − | Once closed, the issues will automatically transition to the <code>Done</code> column of the board where they remain for reference until they are archived at the end of the next cycle's proposal phase (as per the section above).
| |
| − | | |
| − | | |
| − | === Contributor ===
| |
| − | | |
| − | ==== Create your compensation request issue ====
| |
| − | | |
| − | If you wish to request compensation for the current [[Glossary#DAO Cycle|cycle]], you should [https://docs.bisq.network/compensation.html#submit-your-compensation-request create a compensation request issue] no later than '''one week prior''' to the end of the current cycle's proposal phase. This is in order to allow time for review by your [[Team Lead]]. Reminders about this deadline are sent every cycle to the [https://github.com/bisq-network/teams/dao @bisq-network/dao] team, so you should make sure you are watching discussions for that team.
| |
| | | | |
| − | WIP (Work in Progress) compensation requests may be submitted with a <code>[WIP]</code> prefix in the title, e.g. <code>[WIP] For Cycle 10</code>. Such WIP requests are assumed not to be ready for review until the WIP prefix is removed. This allows you a convenient way to incrementally add content to a compensation request throughout the course of a cycle without triggering a review prematurely. To indicate that a WIP compensation request is now ready for review, remove the <code>[WIP]</code> prefix from the compensation request issue and add a comment stating ''"This request is ready for review"''. Any compensation request submitted without a WIP prefix will be assumed to be ready for review.
| + | == Compensation Maintainer == |
| | | | |
| − | ==== Incorporate review feedback for your request ====
| + | The compensation maintainer oversees the day-to-day process of compensation requests, triages issues, and determines rates. |
| | | | |
| − | When your team lead or other stakeholders review your compensation request, they will provide any feedback or requests for changes in the form of a comment on your request issue. Please respond to it promptly. When there is no further feedback, your team lead will add a comment asking you to submit this compensation request as a DAO proposal. The instructions how to do so are in the next section.
| + | See the [[Compensation Maintainer]] article for more details on this role. |
| | | | |
| − | ==== Submit your request as a DAO proposal ==== | + | == Contributor == |
| | | | |
| − | Follow the instructions on how to [https://docs.bisq.network/compensation.html#file-your-compensation-request-in-the-dao file your compensation request as a DAO proposal]. When complete, add a comment to your proposal issue that includes the transaction ID of your proposal.
| + | Contributors are welcome to create compensation requests for work they've done on the Bisq project. See instructions in [[Making_a_compensation_request|this guide]]. |
| | | | |
| − | === Team Lead ===
| + | If you'd like to contribute to Bisq but are unsure where to start, check out the [[contributor checklist]]. |
| | | | |
| − | ==== Review team member requests ==== | + | == Burning Men == |
| | | | |
| − | When a team lead is assigned to a compensation request issue, they should promptly review it with regard to whether the work meets the definition of delivered, and whether it fits within the team budget. The team lead should add feedback and comments as a appropriate, and assign the contributor to the issue to indicate that they are expected to respond to the review.
| + | Any contributor can also act as Burning Man. This is part of Bisq's decentralized [[Burning Men]] protocol. Contributors to Bisq can choose to burn the BSQ they receive to have a chance of receive bitcoin trade fees paid by traders. The process of burning BSQ also help strengthen the DAO by decreasing the BSQ supply. |
| | | | |
| − | When the review process is complete, i.e. all team lead feedback has been addressed, the team lead should add a comment asking the contributor to submit their proposal to DAO and to post the resulting TXID in a comment.
| + | == Stakeholder == |
| | | | |
| − | === Stakeholder ===
| + | Just as stakeholders may review and vote on any DAO proposal, stakeholders may review and vote on any contributor's compensation request. After all, compensation requests are merely another type of DAO proposal. |
| | | | |
| − | ==== Review contributor requests ====
| + | No special permissions are needed—a stakeholder can simply add feedback in the form of a comment on a compensation request or an emoji reaction (thumbs-up, thumbs-down, confused face, etc). |
| − | Remember that just as stakeholders may vote on any DAO proposal, stakeholders may review any contributor's compensation request. To do so, simply add your review feedback in the form of a comment, and react to the compensation request issue with a thumbs-up, thumbs-down or confused face emoji as appropriate. Note that with the exception of team leads, there is no obligation to perform these reviews, and in general you should only review compensation requests that you are knowledgeable about.
| |
| | | | |
| | + | There is no obligation for stakeholders to perform these reviews, but it's advised to only review compensation requests that you are knowledgeable about. |
| | | | |
| | [[Category:Processes]] | | [[Category:Processes]] |
Compensation is an important element of the Bisq DAO that incentivizes people to contribute to the Bisq software and, over time, enables them to take on a greater stake in its governance.
This article covers the several parties involved in the process of requesting, approving, issuing, and guiding compensation.
Compensation Maintainer
The compensation maintainer oversees the day-to-day process of compensation requests, triages issues, and determines rates.
See the Compensation Maintainer article for more details on this role.
Contributor
Contributors are welcome to create compensation requests for work they've done on the Bisq project. See instructions in this guide.
If you'd like to contribute to Bisq but are unsure where to start, check out the contributor checklist.
Burning Men
Any contributor can also act as Burning Man. This is part of Bisq's decentralized Burning Men protocol. Contributors to Bisq can choose to burn the BSQ they receive to have a chance of receive bitcoin trade fees paid by traders. The process of burning BSQ also help strengthen the DAO by decreasing the BSQ supply.
Stakeholder
Just as stakeholders may review and vote on any DAO proposal, stakeholders may review and vote on any contributor's compensation request. After all, compensation requests are merely another type of DAO proposal.
No special permissions are needed—a stakeholder can simply add feedback in the form of a comment on a compensation request or an emoji reaction (thumbs-up, thumbs-down, confused face, etc).
There is no obligation for stakeholders to perform these reviews, but it's advised to only review compensation requests that you are knowledgeable about.
