Mautic bounty programme

What follows is the Mautic project’s approach to operating a bounty program for contributions to Mautic Core and officially supported Plugins via relevant GitHub repositories.

If you have feedback on this policy, please join the next team meeting on Slack in #t-product. Get an invite at Mautic Community Slack.

About the program

The Mautic core team is very small and always looking for new contributors to the Open Source codebase. Mautic’s bounty program is an opportunity to address neglected yet important issues and also allows Mautic members to bring attention to issues they care about by providing a financial incentive. Contributors who fix issues with an associated bounty receive financial compensation through invoices on Open Collective, provided that their contribution meets all requirements and a core team member merges their pull request.

No compromise on quality

Mautic requires all contributions to meet high standards. Pull requests are only accepted if they’re:

  • Completed to a high standard

  • Fully covered by automated tests

  • Prepared in a reasonable time frame, including prompt responses to feedback

  • Resolving the linked issue in its entirety

  • For bug fixes, submit the pull request against the upcoming major release branch - for example, 6.x - with a companion PR against the current minor release branch - for example, 5.1. You must meet all quality criteria, and wait for a maintainer to merge the PRs, for payout eligibility.

Mautic seeks quality contributions only. For general pull request guidelines, see the Mautic-pr-requirements.

A contribution is only approved for payment after a maintainers has merged all related pull requests.

Developers should only request to work on tasks and projects that they’re confident of completing in their entirety, seen through to completion, and which they’re capable of working on at their current knowledge and skill level.

Mautic’s 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 - it’s expected developers work on the task without requiring direct support from the team.

Workflow for bounty program contributors

  1. Verify that you can receive payments from Open Collective and create an account on Open Collective.

  2. Look for issues with attached bounties: browse bounty issues.

  3. Express interest by commenting on the issue and asking the Core Team to assign it to you.

  4. Open a Pull Request within 7 days of assignment and request feedback and review.

  5. Address feedback from the Core Team, if applicable, within 7 days of receiving it.

  6. Wait for the core team to review the PR, approve it, and merge it.

  7. Submit an invoice on Open Collective with links to the issue and PRs.

  8. The Mautic Legal & Finance team reviews and approves payment requests where appropriate.

  9. Receive payment from Open Collective - processed twice a week on Tuesdays and Thursdays.

If you live in certain countries, you may need to use a workaround like Payoneer. Review Open Collective Payout Method for more information.

Important notes

  • Some regions may not be eligible for Open Collective payments due to payment provider restrictions or trade limitations. Review the Mautic Financial Policy for details.

  • Contributors are responsible for any tax obligations from program earnings. Open Collective may require relevant tax forms for withdrawals exceeding $600 per year.

  • Discuss your participation with your employer to ensure that it complies with your employment terms.

Workflow for bounty providers

If you wish to sponsor a bounty for a specific issue, follow these steps.

Note

Providing a bounty doesn’t guarantee issue resolution, Core Team acceptance, prioritization, or a specific release date.

The Core Team or any Mautic member may contribute funds to the Bounties Project on Open Collective for a specific issue. Here’s how:

  1. Log in on Open Collective.

  2. Navigate to the Bounties Project, then scroll to the Donation button.

  3. Enter your donation amount, and select the appropriate Organization on the next screen if you want an organization to pay and/or display as the funding source. Otherwise it’s associated to your individual profile.

  4. Provide the necessary payment details and complete payment.

  5. Comment on the issue with a link to the transaction and the amount added. A Triage Team member can update the issue title with the bounty amount and add the Bounty label.

  6. Wait for a developer to work on the issue, or search for one.

  7. When a pull request is available, test it thoroughly and provide an approval review on GitHub; this is mandatory for the Core Team to consider it for merging.

  8. After merging the pull request and any companion pull requests, the contributor submits an invoice on Open Collective. The Core Team’s Legal & Finance representative reviews and approves it for payment.