Haven’t stopped by in months, glad to see the community has maintained its commitment to drama. 
That’s an easy commitment to make. A commitment to open source software by a corporation, however, is harder and has to be more than lip service. Most importantly it has to include meaningful financial and logistical support to in-house developers. Otherwise, all it’s “committing” to is gatekeeping access to the project.
There should be a minimal standard of code and project management that dictates well-documented code with a consistent style, helpful explanations of changes to that code, and testing before allowing a change into the codebase. The fact that this doesn’t happen with FreePBX means that Sangoma either isn’t willing to pay for the best people, and/or isn’t willing to properly support and manage them once they’re in place.
Taking the the most recent commits to the framework module as an example: 18 February, a PR is opened at 2AM Pacific time. No description or explanation for the changes is given in the PR, though the title suggests some kind of connection to an issue. The author’s profile has no identifying details but their commit history shows 3 years of activity on mostly FreePBX repos, so maybe they’re affiliated with Sangoma somehow? Less than an hour later, the PR is merged, without comment or explanation. Then, 15 minutes later, the change is reverted: again with no explanation given.
Maybe there was some internal communication around this; we – the open source community – don’t know. All we see is chaos: some random dev wiping out a public method from a core framework class for no reason is okayed by Sangoma, followed by a hasty undo. This time the (presumed) mistake was caught early before going out into release. Many times it isn’t. This is just one example, and sure: I was looking for something to criticize. But I was expecting to have to scroll through a little more than (checking notes, counting on fingers) zero commits to find it. Coders all make mistakes, but industry best practices are made to prevent us from showing those mistakes in public.
Walk the walk, put your money where your mouth is, etc, etc. If you have a commitment to open source, you must have a commitment to your developers and good development practices.
(lost post from 2025-03-19 16:46:15 restored by mod on 2025-03-22 and requested review by @miken32)