Compensation Maintainer - Revision history

MwithM: /* Announce request submission deadline */ new github projects

2024-08-22T16:27:39Z

Announce request submission deadline: new github projects

MwithM: /* Propose BSQ rate for next cycle at submission deadline */ Pre-consensus not used anymore

2022-03-17T08:21:00Z

Propose BSQ rate for next cycle at submission deadline: Pre-consensus not used anymore

MwithM: /* Announce request submission deadline */ reminder at compensation repo

2022-03-17T08:19:29Z

Announce request submission deadline: reminder at compensation repo

MwithM: /* Duties */ rates are announced just at Cycle's beginning

2022-03-17T08:17:05Z

Duties: rates are announced just at Cycle's beginning

Plebeian9000: move compensation role description from the compensation page to this page

2021-04-09T14:51:03Z

move compensation role description from the compensation page to this page

Plebeian9000: place compensation maintainer role duties in role article (copied from compensation article -- in both places, for now)

2020-06-16T04:06:55Z

place compensation maintainer role duties in role article (copied from compensation article -- in both places, for now)

Cbeams at 07:47, 8 June 2020

2020-06-08T07:47:54Z

HunterNyan: Fixed link

2020-04-27T18:09:04Z

Fixed link

HunterNyan: linked duties to process

2020-04-27T18:08:46Z

linked duties to process

HunterNyan: fixed formatting

2020-04-27T05:23:19Z

fixed formatting

@@ Line 23: / Line 23: @@
 [[File:Compensation_board.png|400px|right|thumb|Compensation board]]
-Dates and reminders will be announced on a pinned issue at github [https://github.com/bisq-network/compensation/issues compensation repository], the [https://github.com/orgs/bisq-network/projects/5 compensation board], and the [[events calendar]].
+Dates and reminders will be announced on a pinned issue at github [https://github.com/bisq-network/compensation/issues compensation repository], the [https://github.com/orgs/bisq-network/projects/20/ compensation board], and the [[events calendar]].
 === Triage incoming requests ===

@@ Line 37: / Line 37: @@
 * dragging and dropping existing issues to categories
 * using the "Projects" section in the right sidebar of an issue's page
 === Archive previous cycle requests at the end of the proposal phase ===

@@ Line 23: / Line 23: @@
 [[File:Compensation_board.png|400px|right|thumb|Compensation board]]
-Dates and reminders will be announced on the [https://github.com/orgs/bisq-network/teams/dao/discussions/ @bisq-network/dao] discussion board, the [https://github.com/orgs/bisq-network/projects/5 compensation board], and the [[events calendar]].
+Dates and reminders will be announced on a pinned issue at github [https://github.com/bisq-network/compensation/issues compensation repository], the [https://github.com/orgs/bisq-network/projects/5 compensation board], and the [[events calendar]].
 === Triage incoming requests ===

@@ Line 13: / Line 13: @@
 === Announce BSQ-USD exchange rate ===
-Compensation requests use a [https://github.com/bisq-network/proposals/issues/313 30-day volume-weighted average] to determine a BSQ/USD rate that discounts outliers. Until Cycle 23, compensation requests [https://github.com/bisq-network/compensation/issues/519 used a 90-day volume-weighted average].
+Compensation requests use a [https://github.com/bisq-network/proposals/issues/313 30-day volume-weighted average] to determine a BSQ/USD rate that discounts outliers.
+At the beginning of the cycle, the Compensation Maintainer should create a pinned issue with the title "BSQ rate for Cycle X is Y.YY USD per 1 BSQ".
-Toward  the end of a cycle, the Compensation Maintainer should create a pinned issue with the title "BSQ rate for Cycle X is Y.YY USD per 1 BSQ" and link to the proposal where the rate was determined.
+<!-- https://github.com/bisq-network/compensation/issues/782 -->
 === Announce request submission deadline ===

@@ Line 1: / Line 1: @@
-This article documents the ''Compensation Maintainer'' [[role]].
+The '''Compensation Maintainer''' handles announcements and issue triaging for compensation requests.
 __TOC__
 == Issue ==
-* [https://github.com/bisq-network/roles/issues/102 Support Team Lead #102]
+https://github.com/bisq-network/roles/issues/86
 == Team ==
-===github===
+[https://github.com/orgs/bisq-network/teams/compensation-maintainers @bisq-network/compensation-maintainers]
 == Duties ==
-=== Announce BSQ-USD rate ===
+=== Announce BSQ-USD exchange 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.
+Compensation requests use a [https://github.com/bisq-network/proposals/issues/313 30-day volume-weighted average] to determine a BSQ/USD rate that discounts outliers. Until Cycle 23, compensation requests [https://github.com/bisq-network/compensation/issues/519 used a 90-day volume-weighted average].
 === 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]]
+To allow time for team leads to discuss and review compensation requests, requests need to be ready for review 1 week before the end of current cycle's proposal phase.
 === Triage incoming requests ===
@@ Line 26: / Line 29: @@
 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.
+Incoming issues are categorized as <code>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. The Compensation Maintainer assigns <code>In Review</code> issues to the appropriate team leads (or determine which team leads are responsible if it isn't obvious).
-The Compensation Maintainer should transition reviewed requests with DAO proposals transaction ID submitted to <code>Proposal Submitted</code> column.
+The Compensation Maintainer should submit a proposal for 30-day and 90-day weighted average BSQ rates (without outliers) to be used for the following cycle. The purpose of this proposal is to make sure there is rough consensus for the suggested rates. In case rough consensus is not reached, different proposals should be discussed and then submitted to the DAO for voting. The proposal with the highest vote weight wins and takes effect in the next cycle.
-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.
+See [https://github.com/bisq-network/proposals/issues/270 this proposal] for background on this process.
 === 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.
+Once a cycle's proposal phase is over, 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.
+The reason for waiting to archive these issues is so that contributors can easily see how many requests were made in the last cycle, quickly find their own request, and easily review which ones were accepted and rejected. Requests are archived in order to keep the board clean and make room for requests in the next cycle.
 === Close current cycle requests after the vote reveal phase ===
@@ Line 43: / Line 55: @@
 # 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".
+# Close the issue with a comment indicating the request's outcome (e.g., "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).
+Once closed, the issues will automatically move 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 (see above).
 == Rights ==
-<!-- list in bullet points all special privileges that owner(s) of this role are granted, e.g. repository access -->
+* "Triage" access to the [https://github.com/bisq-network/compensation/ compensation repository]
 == Bonding ==

← Older revision		Revision as of 07:47, 8 June 2020
Line 23:		Line 23:

	[[Category:Roles]]		[[Category:Roles]]
−	~~[[Category:Admin]]~~
	[[Category:Maintainer]]		[[Category:Maintainer]]

← Older revision		Revision as of 05:23, 27 April 2020
Line 28:		Line 28:
	[[Category:Roles]]		[[Category:Roles]]
	[[Category:Admin]]		[[Category:Admin]]
		+	[[Category:Maintainer]]