[bisq-network/projects] Establish compensation request review process (#7)

[Chris Beams]

_ at bisq-network/team-leads and @bisq-network/compensation-maintainers, please read and respond to this asap, as it deals with the orderly processing of Cycle 10 compensation requests, thanks._

## Criteria for delivery

- [ ] All Cycle 10 compensation requests submitted by the Monday Feb 10th deadline have been reviewed by their respective team leads
- [ ] Review feedback has been acknowledged and applied by each contributor
- [ ] The [Compensation Requests board](https://github.com/bisq-network/compensation/projects/1?fullscreen=true) has been used to facilitate the review process
- [ ] The process is documented on the wiki and ready to go for Cycle 11

## Tasks

- [x] @m52go to ask all contributors to submit their compensation request GitHub issues one week prior to the end of the proposal phase in order to allow for team lead review and subsequent adjustments prior to submitting the proposal via the DAO (#9)
- [x] @cbeams to put together Compensation Requests board
- [x] @cbeams to assign compensation requests to team leads as appropriate
- [x] @cbeams to write up proposed review process (see below)
- [x] @cbeams to grant write access to bisq-network/compensation to all @bisq-network/team-leads such that they are able to transition issues on the Compensation Requests board
- [x] @bisq-network/team-leads to review proposed process and provide feedback
  - [x] @m52go 
  - [x] @ripcurlx 
  - [x] @wiz 
  - [x] @leo816 (with an eye toward taking over this aspect of the support team lead role)
- [x] @bisq-network/compensation-maintainers to review proposed process and provide feedback
  - [x] @MwithM 
- [ ] @bisq-network/team-leads to review their respective team members' compensation requests per the process
- [ ] Contributors to submit proposals to dao per the process
- [ ] @bisq-network/team-leads to transition issues to `Proposal Submitted` as each proposal is submitted
- [ ] @bisq-network/compensation-maintainers to close compensation requests with appropriate labels when voting is complete
- [ ] Document this process on the wiki (possibly in conjunction with migrating the existing compensation documentation at docs.bisq.network to the wiki)

## Proposed Process

### Submit compensation request GitHub issues
Contributors who wish to request compensation for the current cycle should submit a compensation request GitHub issue no later than 1 week prior to the end of the current cycle proposal phase.

WIP (Work in Progress) compensation requests may be submitted with a `[WIP] ` prefix in the title, e.g. `[WIP] For Cycle 10`.

When a contributor removes the `[WIP]` prefix from a compensation request issue, they should also add a comment stating `This issue is ready for team lead review`.

### Add new compensation requests to the Compensation Requests board
@bisq-network/compensation-maintainers should be watching the bisq-network/compensation repository, and upon being notified of a new compensation request issue, should add the issue as to the [Compensation Requests board](https://github.com/bisq-network/compensation/projects/1), putting `[WIP]` requests in the `In Progress` column, and putting non-WIP requests in the `In Review` column.

When a compensation request issue is transitioned to the `In Review` column, @bisq-network/compensation-maintainers should also assign the appropriate team lead(s) to that issue. The compensation maintainer must actually look at the content of the request and determine which team lead or leads are responsible. A given compensation request may include dev and growth work, for example, and so both @ripcurlx and @m52go should be assigned to review. When in doubt, the compensation maintainer should simply post a comment in the compensation request issue asking which team leads are appropriate.

### Team lead review

When a team lead is assigned to a compensation request issue, they should propmtly 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.

When the review process is complete, i.e. all team lead feedback has been addressed, the team lead should (a) transition the issue to the `Review Complete` column and (b) add a comment asking the contributor to submit their DAO proposal and to post the resulting TXID in a comment.

### Submit compensation request DAO proposals
Once a compensation request has been transitioned to the `Review Complete` column, the contributor is free to submit their request as a DAO proposal per the usual process. When complete, the contributor should add a comment that reads `DAO proposal transaction ID: <txid>`.

When @bisq-network/compensation-maintainers or @bisq-network/team-leads see the `DAO proposal transaction ID` comment, they should transition the issue to the `Proposal Submitted` column.

### Close compensation requests after voting

Per the usual process, when the vote reveal phase is complete, @bisq-network/compensation-maintainers should close each proposal in the `Proposal Submitted` column appropriately, indicating via comment and label whether the request `was:approved` or `was:rejected`.
When a team lead is assigned 

### Notes

When the above process has been completed, the Compensation Requests board should be empty save for any new `[WIP]` compensation requests for future cycles that may have come in during the process.

The process above assumes prompt action from both @bisq-network/compensation-maintainers and @bisq-network/team-leads with regard to responding to issue state changes, transitioning issues on the board appropriately, etc. If anyone has doubts about their ability to do this in a timely fashion (same-day), please speak up.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200217/b619d17e/attachment-0001.html>