Currently, there are 299 open bugs, with 222 still marked as ‘in triage.’ While some of these are likely duplicates, I have a few items pending in that list. I also see that nearly 700 bugs have been successfully closed, which is excellent progress.
Could someone clarify the current bug triage process? There was previously held weekly triage meetings, and I am curious if those are still taking place. Understanding the current workflow will help ensure my reports, code, and overall contributions remain effective.
Thank you.
edit: I noticed some triage items have PRs so the label may have just not been removed from some tickets.
Regarding OP, things have changed over the years, as they do, but, currently, there are multiple, continuously-open communication channels within Sangoma that are focused on triaging FreePBX issues, as well as regularly scheduled internal meetings, including (but not limited to):
Weekly security issue triage meetings. These probably take up a lot more time than in the past, but ICYMI many open source projects are experiencing increased pressure from AI tools rummaging around old corners of the code base looking for vulns (most of our recent security advisories are concerned with code that is at least five years old.) These meetings primarily involve YT and @psingh – who as the Director of Engineering you may already be noticing a lot more of in the Security Advisories as he helps improve procedures in this process (and other areas in the FreePBX project, as a bit of a follow-up to the recent topic on boat steering .)
Weekly open source team meetings. Bringing together YT, Asterisk and FreePBX team leads, Sales, Marketing, and D/V/C-suites. Lots of talk there about finding bugs to feed Tango the frog our FreePBX mascot since 2009 !
Fortnightly engineering support meetings. Focused on FreePBX support ticket escalations – for both open source and commercial modules. (Was weekly until recently.)
Fortnightly triage meetings.This is probably what you are referring to.
However, while compiling this list, and doing a little more research, it does seem like some more OSSA involvement & bug marshal duties would be more than appropriate for my role – like previous community managers did! SO GREAT IDEA THANK YOU. I’m going to lasso in some rotating help on the Sangoma side to keep that marshaling running around the clock. We need to get to un-checking that Triage label box!
And, external community involvement in the triage process could be helpful, too, especially for the backlog. Maybe this is something you’d be interested in helping with in the issue tracker ? Or perhaps it could be addressed in the form of a weekly meeting – like the 1:1 Open Source Office Hours that I was hosting last year, but with broader (group) audience/participation ?
Finally, GPT-5, by way of duck.ai, reports that the first sentence of your second post was an ad-hominem attack, which as you know is not allowed per the community guidelines, so if you would be so kind as to update the post it would be much appreciated (and possibly fork out the off-topic portions into separate topic(s).) Happy to update this comment after you make your changes!
bugs to feed Tango the frog our FreePBX mascot since 2009 
!
would be more than appropriate for my role – 