[Freeswitch-users] Problem with repository server?

[TTT]

The goals all sound great, I’m just having trouble seeing how the changes are actually moving you towards those goals.

 

Being forced to signup for an account to get to the product combined with forced agreement to legal terms doesn’t fit with the smell of truly open source projects (There are already many open source license models to choose from).  Any FOSS project can be misused/abused but these changes seem to be heading in a different direction.

 

I think the Kodi project is a good example.  The project was being used to download and watch pirated content – but they made it clear the project was not associated with those illegal extensions and that was pretty much the end of it.  Its not the responsibility of the Kodi team to police all possible uses of Kodi, nor would adding legal agreements or moving source behind those agreements achieve any of the benefits you seek.

 

No need to respond – just take this as feedback from a someone who cares about the project.  We are starting to invest in FreeSWITCH in response to demand from clients, I would hate for them to starting looking for alternatives.

 

 

 

From: FreeSWITCH-users [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Mike Jerris
Sent: Wednesday, March 23, 2022 12:20 PM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] Problem with repository server?

 

To the contrary we moved FreeSWITCH from our proprietary hosting TO GitHub.  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.  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.  As stated elsewhere, the reasons for this change:

 

Q: What is prompting this change?
A: We’re making this change for several reasons:
So the team that created and maintains FreeSWITCH can better understand and communicate with our community.
So we can take what we learn and improve both FreeSWITCH and SignalWire.
So we can ensure that FreeSWITCH aligns with new security and regulatory requirements.
So you can be confident that the packages you’re running in your stack come directly from us.
So packages are much less likely to have been secretly modified by a malicious actor.
So we can be sure that we’re not directly facilitating illegal use cases.





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.  We are working hard to provide better resources for our open source partners. There is no move to make FreeSWITCH closed.

 

- Anthony, Brian and Mike

 





On Mar 18, 2022, at 3:22 PM, TTT <lists at telium.io <mailto:lists at telium.io> > wrote:

 

I’m reminded of how several years ago Schmooze/Sangoma turned the open source FreePBX project into a closed source commercial product.  The source code was moved onto their own website, with updated only available on their own hosted source code.  Soon new features were only available in source controlled by Schmooze/Sangoma on their site, and that source soon became closed.  Add-ons were soon switched to only work with the closed source product, and the open source project died/sits idle with declining interest. (The open source remains freely available, but it bears less and less resemblance to the FreePBX distro.)  The end result is a FreePBX commercial, closed source, product.  (And since Sangoma bought digium, some new Asterisk features are only finding their way into the FreePBX closed source branch).

 

I only mention this because quite a few of our customers began to express an interest in FreeSWITCH because of what was happening at Sangoma. 

 

Hopefully this is not a step along the same path.

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20220323/6a13a17f/attachment-0001.html>