6/4/2023 0 Comments Signalwire freepbx![]() Soon new features were only available in source controlled by Schmooze/Sangoma on their site, and that source soon became closed. The source code was moved onto their own website, with updated only available on their own hosted source code. ![]() > I’m reminded of how several years ago Schmooze/Sangoma turned the open source FreePBX project into a closed source commercial product. There is no move to make FreeSWITCH closed. We are working hard to provide better resources for our open source partners. It also has allowed us to clean up a mess of old infrastructure that was expensive and difficult to maintain, and to get a better handle on abuse of the repositories, which until this change had an entire data center network pipe pegged 100% by people who were abusing the resources. So we can be sure that we’re not directly facilitating illegal use cases. So packages are much less likely to have been secretly modified by a malicious actor. ![]() So you can be confident that the packages you’re running in your stack come directly from us. So we can ensure that FreeSWITCH aligns with new security and regulatory requirements. So we can take what we learn and improve both FreeSWITCH and SignalWire. So the team that created and maintains FreeSWITCH can better understand and communicate with our community. As stated elsewhere, the reasons for this change:Ī: We’re making this change for several reasons: We’ve expanded our team of full time people who work to improve FreeSWITCH on a daily basis and have put multiple man years of work into code quality, ci, testing, and reliability of the codebase. The founding team of FreeSWITCH started SignalWire and as a result we are now commercially sound enough to put even more resources into FreeSWITCH than before. To the contrary we moved FreeSWITCH from our proprietary hosting TO GitHub.
0 Comments
Leave a Reply. |