Git-Mirrors/haveno
1
0
Fork 0
mirror of https://github.com/haveno-dex/haveno.git synced 2024-10-01 01:35:48 -04:00
Code Issues Packages Projects Releases Wiki Activity

bounties.md: clarify the changes need to be merged

Browse Source 
This doesn't change the current system. We only specify further that
a patch must be merged for the issue to be considered resolved. This
is assumed, but since we were asked for clarifications we decided
to specify it in the terms of the bounty system.
This commit is contained in:
erciccione 2021-06-02 17:28:41 +02:00 committed by woodser
parent aba3c1b82e
commit 584b3c90ae
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/bounties.md
View File

@ -7,6 +7,7 @@ To receive a bounty, you agree to these conditions:
- Your changes must follow the [styling guidelines](CONTRIBUTING.md).
- Bounties will be set and awarded at discretion of the Haveno core team.
- The issues eligible for a bounty are labelled '💰bounty' and have the amount of the bounty specified in the title in this form: `[$200]` if in dollars or `[ɱ20]` if in Monero.
- An issue is considered resolved when the patch(es) proposed by the contributor is/are merged in the appropriate repository according to terms of the issue.
- The first person who resolves an issue in its entirety will receive the entire amount of the bounty.
- If the issue is resolved collaboratively by more than one person, the reward will be distributed among the contributors at discretion of the Haveno core team.
- Let the Maintainers know if you intend to work on a bounty, so that the issue can be assigned to you. Being assigned to an issue doesn't make that issue resolvable only by the assignee. It's meant to avoid duplication of efforts and not to discourage collective works.