To be quite honest and transparent, determining what everyone actually wants and picking that information out has been difficult - some stuff is obvious, other stuff isn’t, and to this point there hasn’t been a real list. Now that one has been started it can be worked on. There’s also not going to be an immediate resolution to everything - other teams are involved for some of this and things can’t change in an instant. I’d like them to, but reality is otherwise.
So a list gives Nenad (and me to a degree because I don’t care about titles and will push things in the various ways I can) objectives to work on and things to deliver here.
The list can also change. If someone reading this looks at it and has other requests/queries/concerns, then that can go on the list.
My only asks:
If you have something, try to make your concern/request as clear as possible and what you believe should be a resolution.
This is going to be a continuing dialog. Some stuff will take time.
@adell4444 I haven’t forgotten about that thread either. I found the direct actual link in my browser history and should have information in a few days.
What is the status of FreePBX v15? Based on various communications it should, at this point, be End of Life. However, the activity on it suggests other wise. As well, how long will FreePBX v16 be supported before going to Security Fixes only (where I think it should be at this point) and End of Life.
Both of these versions are running top to bottom on end of life system and software. Supporting and maintaining both of these is extra work and removal of focus from development of v17 and beyond.
That would be a good place to start and provide clarity on. The list is a good start and covers things well but the current status of releases has been an ongoing question.
I feel like this is the most important question for FreePBX-specific issues, and I know it has been asked directly and clearly multiple times in the last few weeks since the confusion regarding EOL and SFO timelines was started.
@adell4444 I can actually give an update now! The original thinking for deletion of the thread was due to potential disclosure of personal information. We reached out to the poster to get permission on restoring the entire thread confirming they were okay with it, or if there was any information that shouldn’t be present so it can be removed, but did not get a response confirming either option. Since there was not an approval on restoring it I don’t feel comfortable doing so.
Going forward such a situation will be handled as such:
The specific post will be flagged, be it by a Sangoma employee or the community (if you see something you think is private and shouldn’t be public flag it)
If post originates from Sangoma then training/discussion will occur on personal information disclosure, and the post either modified or deleted
If post originates from non-Sangoma we’ll reach out to the poster to have them confirm it’s okay or give them an opportunity to edit it, or if they want just delete it
If deletion occurred a message will be added stating what happened
The only cases where thread deletion will occur:
Someone requests it explicitly - this usually comes up when people want us to erase their presence on the forum for some reason
Spam - this is usually caught before it ever appears and noone sees it though some spam solutions are clever and they make convincing enough posts that I let them through, only to delete them after I realize it. If someone has responded I try to message to give a heads-up over why the thread disappeared.
Hope that answers your question somewhat, and provides information on how it’ll work going forward.
Thanks @jcolp. It seemed odd at the time because the discussion was regarding Sangoma support standards for FreePBX (if I recall correctly) and then all of a sudden the post disappears. Also odd because it was asked directly multiple times after it happened and the questions were just ignored, until you stepped in. It seems like such an easy thing to say “the post contained private information that needed to be hidden”.
There are 5 admins and 3 moderators on this forum, so the long delay only exacerbates recent complaints regarding censorship. That hasn’t been an issue as I can tell in the last 2 weeks and that’s in large part to your involvement and moderation so I appreciate that, for what it’s worth.
In regards to recent times, credit also goes to the community for starting anew and keeping the past in the past so we can all make progress.
I forgot some other things I wanted to mention:
Splitting of topics won’t happen by us proactively, if a thread you create forks into different conversations and you want things to split just flag it and we’ll split it up for you.
Merging of threads I will do, but generally it’s if someone creates a new thread to continue one they already created. Just something I’ve always done.
This concludes my forum talk. Anything else just shout my way or make a new thread.
Hi @BlazeStudios thank you. We will provide a clear response to this as early as end of day Monday no later than next week. There seems to be a bunch of conflicting info out there we will update freepbx.org with clear EOL dates. Bottom line is that we are trying to follow OS security updates in the future, where EOL comes inline with end of security updates. We have not been able to do that in the past, but with Debian and post FreePBX 17 we will. Thank you.
To be transparent, I reached out about splitting off the previous conversation privately to @tmittelstaedt and got permission to so I have done so. This was done to keep this thread on topic for requests/comments between the community and Sangoma so it doesn’t get overwhelmed with other discussions. Everyone is welcome to continue discussion on the new conversation.
Thanks!.. Though I do feel bad the Asterisk guy is being made to do it.