A bounty programme in Open Source projects is when a monetary reward is offered for completing a task.
What follows is an initial proposal to implement a bounty programme which we will be trialling for six months (January to June 2021) for contributions to Mautic Core via the Github repository.
If you have feedback on this, please join the next team meeting on Slack in #t-product (get an invite at mautic.org/slack).
The Mautic Community Product Team is small, and we're always looking for new contributors to our Open Source codebases. Our Bounty programme will enable community members to financially reward developers who work on the issues they care about through our partnership with Bountysource.
With Bountysource, issues in the Github issue queue can have a bounty associated with them by one or more people or organisations. This means that one person could add a single bounty of $500 or 10 people could add a bounty of $50, with the person resolving the issue receiving the funds from Bountysource when the fix or feature is merged.
As is already the case, we will not accept pull requests unless they are:
We want to attract quality contributions only. For general guidelines about what's expected in pull requests to Mautic core, see more info here.
The issue will only be considered complete and approved by BountySource for payment if the pull request is merged by a member of the Mautic Community Core Team. Read more in the BountySource FAQs.
Developers may only be assigned tasks and projects that they are confident can be completed in their entirety, seen through to completion, and which they are capable of working on at their current knowledge and skill level.
Our Product Team is happy to answer questions and provide some limited support, but don't have the capacity to mentor junior developers working on bounty issues - developers are expected to work on the task without requiring direct support from the team.
If there is an issue that you want to provide a bounty for, follow these steps.
Please note that providing a bounty does not guarantee that the issue will be resolved, or that the Core Team will accept the contributions. It also does not affect prioritisation by the Core Team and does not guarantee a specific release date, or indeed that it will be merged at all.
Read more and find answers to many questions in the Bountysource FAQs.
Found errors? Think you can improve this documentation? edit this page