Skip to content
Permalink
Browse files

Change order of bug bounty tagging

IMHO it makes more sense if you first check and adjust the issue for newbies and only later actually tag it with a bounty. Thus, you may still see that the issue is not good enough yet or so…
  • Loading branch information...
rugk committed Apr 24, 2019
1 parent be42e1d commit 46ca5a53294e3651a343beaca4c2e579d15e9c4c
Showing with 2 additions and 2 deletions.
  1. +2 −2 BOUNTY.md
@@ -38,10 +38,10 @@ _See [more info about getting paid](https://docs.opencollective.com/help/expense

### Workflow for Core Contributors

1. Make sure the issue is understandable for newcomers and expectations are clearly set

1. Tag issues with the "bounty" label and amount (e.g. "\$100")

1. Add a comment with a basic explanation of the Bounty process and link to BOUNTY.md

> A $100 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $100 when the Pull Request is reviewed, accepted and merged. [More info](BOUNTY.md).
1. Make sure the issue is understandable for newcomers and expectations are clearly set

0 comments on commit 46ca5a5

Please sign in to comment.
You can’t perform that action at this time.