Where is the attack or the ad hominem text?
Just because YOU think the rules don’t apply to you doesn’t mean they don’t. They do.
Go read the thread that has been linked. If you don’t like the rules that you are required to abide by, don’t be here.
Edit: I can just imagine you being dragged away by the police screaming ‘I DON’T CONSENT TO BEING ARRESTED’.
3 Likes
I think we’re getting away from what this thread was originally about. Questioning the current state of support, quality of the product and how they appear to be cutting corners. Now as someone who isn’t a former (or current) employee and shareholder but as someone who has seen how this project has been run under various leadership over the years. This isn’t a new conversation as these points have been brought up numerous times in the past, regardless of the management or team roster. The results have always been the same.
It’s a shame this can never be a serious conversation or dialogue with Sangoma.
4 Likes
I think I can describe myself as someone who pushes buttons and breaks things, but you are obviously much better at it than I. Aside from some small code contributions that have made it into the project, from posts I’ve made on the forum, I haven’t contributed much to the underlying project. So, forgive me if this question is obtuse, but if you’re willing to take back the project, why not just fork it? How much value is there really in the FreePBX trademark?
4 Likes
Good question indeed.
2 Likes
@penguinpbx ufda… lot of words flying around and a good amount of it is off topic.
Please consider reinstating The James. Seems clear that he was in bounds and should not be silenced.
#freethejames!
4 Likes
I want to call out two specific things James raised that would really help the project and community to move forward.
This forum is about FreePBX open source, FreePBX distro, and by extension, PBXact. So I’ll keep the topic focused on these. None of these projects seem to have a roadmap available to the public. A lot of angst would be relieved if the community had a sense of where the projects were going, even a vague sense. Instead, the community is left to speculate and they usually don’t speculate positively (not necessarily speaking for myself; the forums have plenty of it). Personally I see FreePBX as more or less stagnant for the last five years. Great to take the time to pay off technical debt but that was a hard road and now, what’s next?
@penguinpbx I believe this is one of the top things to do as an advocate for the open source project – put on a product manager hat and throw out a gantt chart and some forward thinking, perhaps once a quarter.
This along with reported poor support experiences are undermining the commercial side of FreePBX (commercial modules and PBXact). I don’t see this as your role @penguinpbx since you are representing the open source side of things, but it would be great if we could hear from the support organization what is going on. Chris D used to jump on here and represent support. Who’s left? How big is the support team that can support FreePBX/PBXact? What are the support tiers?
And a footnote:
Generally speaking this community has been in a lot better shape in the past, especially when the paid developers were active and engaging the community. @kgupta and others chime in from time to time, usually to say “raise a bug report.” That’s not community engagement. Is it too much to ask? I understand that it’s a time commitment but guarantee you will write better software and understand the community’s pain points better if you spend some time here where people complain about things.
5 Likes
Hi @billsimon
How are you? 
Well, I’d like to know too.
Obviously, the dev team has been moved to India.
What about the number of people on the Q.A team?
Anyway, the big project regarding FreePBX 17 on Debian can be useful looking at requests from the community, but also, an enormous work additionnaly the current job too. It’s evident Kapil and his tam can be flooded of tasks and over booked.
It’s for this reason the team cannot be on the forum, and work on the project and other current tasks every day.
However, a thought for Kapil for his work. I imagine it must not be a piece of cake every day.
I wouldn’t want them to dig their own grave and Sangoma to kill FreePBX.
Is FreePBX 17 born to kill FreePBX? I hope not…
1 Like
@mwhite Perhaps following your recent post on LinkedIn Michael White on LinkedIn: 🚀 AI for FreePBX - NEW PRODUCT LAUNCH: We’ve been very busy at Sangoma,… you could actually chime in here and put your money where your mouth is and try to bring some calmness to the community!
4 Likes
Yes and answer why FreePBX v17 is having all these really, really basic bugs that should never exist being pushed into the production.
2 Likes
I want to add that Kapil has resolved every issue I raised via support tickets. Often they are resolved in a few days. So I have no issue with Kapil Gupta and his associates. This whole thread revolves around one person being banned for pointing out the elephant in the room.
Again, if the plan is to sunset FreePBX, that would be kinder than letting it die of neglect. The community needs some real answers from the management at Sangoma.
3 Likes
Well, the thread turned into that, but the original topic posted by James was “support, quality, cutting corners.” I was responding to that original topic.
Issues I have raised on Github have been resolved adequately as well. I do not have any concerns about the developers fixing bugs that are raised. However, that is a very narrow focus. Quality software development isn’t about reacting to bug tickets.
7 Likes
Well said.
3 Likes
And that is the “elephant in the room” to which I refer.
3 Likes
If freePBX is an open source project, wouldn’t fixing bugs be a task of the open source community too? The same applies to the community forum…why are there just a few, who respond to questions and try to help?
And that person banned also contributes to bug fixes and submitting PRs for bug fixes.
5 Likes
One would think but there is a serious disconnect with that. The Developer’s Corner section of the wiki is out of date, the old “dev environment” was having issues. The documentation at the developer’s level is pretty non-existent. There’s no real communication channel for Sangoma devs and community devs. As @billsimon pointed out there’s no road-map or tasks list for anyone to work off of.
3 Likes
That is correct…
1 Like
I agree with you. But not fully.
There is a documentation, but often, there is no update.
I know it’s not easy to write or update a documentation. But, need to do. Indeed.
1 Like
There’s some but bare bones “how to make hello world module” and yes, it’s completely out of date.
Yeah and those of us community members that use to have that ability lost it. Then again, the new documentation site is not a great replacement for Confluence.
2 Likes