Bounty policy

[Betree]

To leverage the talent of developers in our community and encourage participation, we're going to set bounties on a certain number of issues. Check for the bounty label and get paid to contribute to open source!

Intro

The CaptainFact team is small and we're always looking for new contributors to our open source codebases. Our Bounty program is an opportunity to solve issues that could be neglected otherwise. Contributors who fix these issues will be rewarded financially.

How it works

We want to attract quality contributions. The issue will only be considered complete and approved for payment if the Pull Request is merged by a core contributor.

Workflow for Bounty Hunters

1. Search for issues with attached bounties

2. Express interest by commenting on the issue and ask to be assigned

3. Open a Pull Request and ask for feedback and review

4. Incorporate feedback from core contributors

5. PR is reviewed, approved, and merged by a core contributor

6. Get paid:

   • If you can issue an invoice, submit it as an expense on Open Collective
   • If you can't issue an invoice, ask to be rewarded with an Open Collective Gift Card or other swags (please note that swag's value probably won't match the bounty value)

Workflow for Core Contributors

1. Tag issues with the "bounty" label and amount (e.g. "20€")

2. Add a comment with a basic explanation of the Bounty process and link to this issue

   💸 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.

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

Base amounts

These amounts are meant to be adjusted based on the importance of the issue, and are just there to serve as a reference.

Complexity	Simple	Medium	Complex
Amount	20€	30€	100€