Using Mautic in your business? Join as a corporate member!
Tiers from $1,200 to $30,000/yr
✅ Support open source
✅ Ensure project sustainability
✅ Get voting rights at our June 25th General Assembly
Invest in the tool powering your marketing:
Using Mautic in your business? Join as a corporate member!
Tiers from $1,200 to $30,000/yr
✅ Support open source
✅ Ensure project sustainability
✅ Get voting rights at our June 25th General Assembly
Invest in the tool powering your marketing:
Bountysource stopped paying out recently, so we've set up a new system.
Check out the debate on our Community Portal: https://community.mautic.org/assemblies/product-team/f/39/debates/2.
This is implemented for GitHub issues, but it might expand into other teams and non-code tasks later.
As a Mautic member, you can support those who fix important issues for you or those you want to get sorted.
🔎Check out the docs here: https://contribute.mautic.org/product-team/mautic-bounty-programme
#Mautic #OpenSource #Bounties #Sustainability #SustainableOpenSource #BountySource
Recently we have heard that Bountysource has become insolvent and since early 2023 has not been paying out bounties to developers who fix issues.This impacted us recently because a bounty was placed on an issue and a developer fixed it but was not able to claim the money back.While we don't hugely promote the opportunity for bounties - mainly because the bountysource extension for Github has been broken for some time - I feel like it's important that we do have a system available if people want to back an issue being fixed with money.I'm starting this debate as an opportunity for us to explore different systems that are available, and pick one that we decide to use for Mautic going forward.Let's say we can have this debate over a period of two weeks and then at the end of that, make a decision?