Up on the FreePBX Developer Corner[1], it says to message the active developers up on the “Development IRC Channel #freepbx-dev on Freenode.”
I just went to that channel, and it’s pretty clear that’s no longer used.
I have two questions… First, is there any active chat/forum where FPBX devs regularly congregate? (I’m thinking it might be Discord or Slack nowadays.)
And second, what is the proper way to change the documentation up on the FPBX Developer Corner Home? Should I file a bug, or send someone an email? Or maybe there is a github project for the FreePBX Open Source Project documentation where I can make changes and submit a PR.
@penguinpbx, thanks for the quick response. I’ll take a look at the FreePBX > Development category. I can already see a couple of interesting topics.
I’ll review the Developer Corner wiki page and post an outline of what I think it needs in a following reply. I think that’s what you’re asking me to do.
Up at FreePBX repositories · GitHub I see 93 repositories, but none look like documentation or “wiki.” It looks like the existing FPBX wiki is a Sangoma wiki hosted off atlassian.net. So there’s not really a way for the community to help maintain it.
Would you consider moving the documentation over to the wiki provided by github? Or are you thinking there should be a new repository under https://github.com/FreePBX/docs?
It’s been ad hoc, e.g., we see a good write-up posted in the forums, blogosphere, etc., and we then contact the author – or are contacted by them – and work with our internal Sangoma documentation team to publish in the FreePBX Community Documentation space in the (gated) Atlassian-based “wiki”.
Maybe. Do you have a good example to share that we might emulate ?
Some content is packed in the READMEs, e.g. devtools repo, and any particular module that needs a README update – lots of these to do before a new wiki is launched IMHO – is open to reasonable* Pull Requests that are attached to issues in the issue tracker repo in order to properly get into the work queue, as suggested in the FreePBX project’s main GitHub landing page:
Inside your patch comment in any specific module repo, you can link back to specific issues in the issue-tracker repo with a line like Bugfix FreePBX/issue-tracker#XYZ where XYZ is the issue number.
…so those are a couple of places to get started right away with the existing infrastructure.
Not at this time, no… although the Asterisk project does this with their documentation repo and that seems to work quite well for them (and many ideas are shared daily between the people working on the Asterisk and FreePBX projects.)
* Please note that AI slop is not considered to be reasonable and is particularly troublesome for documentation due to the high error rates.
I think people miss the fact that until there was the big Wiki blowup a few years back the community had ability to add/update documentation. Sangoma changed platforms and never restored that feature.
Honestly, the ability for the community to maintain community/open source documentation was a real benefit for the community and Sangoma. The Wiki has also been highly outdated and at least the community was able to keep it up to date when needed.
At this point in time the Wiki still has screenshots, examples, etc from v12 and v13. Many pages says “This was updated for v13” (because of GUI changes). Outside of that, a lot of documentation hasn’t been touched in years meaning that updates/changes/removals of things in Asterisk haven’t been accounted for. Basically, there’s been major updates to both Asterisk and FreePBX since much of the documentation was created and it hasn’t been maintained to reflect those changes in the last 5-10 years, give or take.
and, specifically, the 
Do you have a good example to share that we might emulate ?
– is open to reasonable* Pull Requests that are attached to issues in the