yearn-vaults-v3
yearn-vaults-v3 copied to clipboard
Populate repo with issues/bounties
We need help writing the tickets for issues / bounties.
Bounty tickets will receive a payment for its creation. It will only be paid when it receives the to-do
tag.
Each bounty needs:
- Short description: An explanation of what this bounty will achieve.
- If required, longer description + references / docs to understand the underlying problem better.
- Dependencies: other bounties / issues / tasks that need to be done before the bounty can be completed
- Acceptance Criteria: a short list of deliverables / clear checks to be sure the objective is accomplished. Answer to these must be either Completed or Non-completed
- Payment trigger: the action that will queue the payment (e.g. the PR is merged)
- Category: PM or DEV
- Difficulty: Estimated level (0-3) of difficulty or time it will take
Different difficulty levels will receive different payment amounts. The lower the level, the smaller amount of effort is needed and the lower the payment.
As an example:
Bounty 0: Writing tickets for project's bounties
Description:
This project uses bounties for external contributors. These bounties need to be written to be specific enough.
Dependencies:
NA
Acceptance criteria:
Bounty is created as a ticket in the Issues section of the yearn-vaults-v3 repo.
Payment Trigger:
Ticket receives the to-do
tag
Category:
PM
Level:
0