On Friday 18 March 2022 at 21:35:00, Brian : wrote:
Freeswitch team sent this info out to mailing list.
Interesting. Can you point me at the archied copy of that please? I'm bothered that my mail server never delivered it to me, and I'd like to see the timestamp / headers of the message so I can investigate the problem. Thanks, Antony.
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.
Q: What about the source code on GitHub? A: This change does not affect open source code, which will continue to be freely available on GitHub.
This does not in any way change the license to the software.
It may affect how you obtain FreeSWITCH dependencies or FreeSWITCH packages from our package repositories such as our Debian repository.
Q: What does “packages” refer to? The commercial packages? The packages for Debian etc.? Or the raw code/releases? A: This refers to binary package repositories such as Debian repo.
-- Users don't know what they want until they see what they get. Please reply to the list; please *don't* CC me.