Difference between revisions of "Compensation Maintainer"
Plebeian9000 (talk | contribs) (place compensation maintainer role duties in role article (copied from compensation article -- in both places, for now)) |
|||
| Line 13: | Line 13: | ||
== Duties == | == Duties == | ||
| − | + | ||
| + | === Announce BSQ-USD rate === | ||
| + | |||
| + | Compensation requests [https://github.com/bisq-network/compensation/issues/519 should use a 90-day volume weighted average] to calculate a value for BSQ and mitigate its volatility. At the end of a Bisq DAO Cycle and beginning of a new one, the 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 the [[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). | ||
== Rights == | == Rights == | ||
Revision as of 04:06, 16 June 2020
This article documents the Compensation Maintainer role.
Contents
Issue
Team
github
wiki
Duties
Announce BSQ-USD rate
Compensation requests should use a 90-day volume weighted average to calculate a value for BSQ and mitigate its volatility. At the end of a Bisq DAO Cycle and beginning of a new one, the Compensation Maintainer should create a pinned issue with the title: BSQ rate for Cycle X is Y.YY USD per 1 BSQ 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 Ready for review one week prior to the end of current cycle's proposal phase.
The date and reminders will be announced at @bisq-network/dao, the Compensation board and the Events Calendar
Triage incoming requests
The Compensation Maintainer watches the compensation repository and proceeds to triage:
Incoming issues are classified as Work in progress if they have [WIP] at the beginning of the title or as In Review 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 Proposal Submitted 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 archive all issues in the Done 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 Done 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
was:acceptedorwas:rejectedaccording 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 Done 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).
Rights
- Repo Access: https://github.com/bisq-network/compensation/
Bonding
N/A
