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
Conversation with Ruth Cheesley
Hi folks, I have a bit of an update - see what you think!
I've written a GitHub Action (well, ChatGPT mostly did it for me!) which adds some text on the bottom of each issue when it's created, linking to an Open Collective project we will use just for bounties.
I've also set it so when the bounty tag is added, it posts a message to say there's a bounty available, and a link to a filtered list of transactions which relate to that issue (it's very crude, it assumes the issue number is used in the transaction somewhere).
Here is a short video: https://watch.screencastify.com/v/1T6TXHczlXiMDo1S9uTe
We have a budget already for bounties which has not been used this year, so the core team can start with assigning that - maybe we can use it to boost up the issues we need fixing before General Availability release of Mautic 5 which aren't already assigned to someone.
Individuals then create an invoice to request payment when the PR is merged by a core team member.
Love it! I'd suggest to add the bounty amount into a comment so multiple people could add bounties to the same issue. But this is already way better than nothing!
@escopecz I thought that too, but it requires more complication than was worth my time exploring to pull the data from the API for a phase 1 implementation. I thought about scraping it from the list of transactions and ChatGPT told me in no uncertain terms that was not the best route to go down 😅, so I guess we'd have to somehow query the Open Collective API, search for transactions with the Issue ID in the reference, and then sum them up, maybe? Or post a comment when that happened (maybe n8n could help there). I was also thinking to add it to the title eg. [$500] as well.
Loading comments ...