Product Team
#MauticProductTeam Steering Mautic's Development: The Product Team,Pioneering Release Cycles and Roadmaps
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?
The debate was closed on 21/12/2023 11:30 with these conclusions:
We have implemented a system which uses our existing Open Collective infrastructure.
Report inappropriate content
Is this content inappropriate?
Close debate
What is the summary or conclusion of this debate?
Comment details
You are seeing a single comment
View all comments
Hi folks! Thanks so much for engaging in this discussion!
We decided to go with a simple approach of using a project on Open Collective for this purpose, and following a similar workflow to what Open Collective itself uses for bounties. New docs are here: https://contribute.mautic.org/product-team/mautic-bounty-programme and the PR implementing a message on issues raised can be found here: https://github.com/mautic/mautic/pull/12916. Here's an example of what it drops into the issue under a horizontal rule: https://github.com/mautic/mautic/issues/13094.
I'll go ahead and close this debate now and we'll make a public announcement soon.
Loading comments ...