Our concern has always been two-fold: (1) the encrypted module signatures that make anything contributed by anyone else display all sorts of glaring messages suggesting that your server has been compromised and (2) the hidden module repositories that are actually used by the GUI to monitor and update modules. These repos are entirely separate from GitHub with entirely different "GPL" content. The FreePBX GitHub repos do NOT include module signatures so ALL of those modules will display tampering errors unless you rip out the module signature checking component OR sign your life away to Sangoma so you can generate your own signatures, something we're unwilling to do.
We'll see how this goes, but it is BIG NEWS. Keeping FreePBX modules current isn't a very big deal so long as Sangoma keeps their GitHub repo current which, to date, they have done as best I can tell.
As for patent claims, I've read Tony's comments about patent infringement. I've also spoken to Tony numerous time about patent claims. He owned the company at the time, and nothing would preclude him from disclosing what the patent claims were. My recollection is that all the patents Tony mentioned to me have long since expired. Until we see some actual facts surrounding the patent claims, it's premature to draw many conclusions. Whether intended or not, this obviously dissuades others from forking FreePBX based upon some undisclosed boogey man which may or may not exist. That inures to the benefit of Sangoma. If, in fact, someone were sued for patent infringement based upon a FreePBX module, then Sangoma obviously is going to be joined as a party... unless you've signed their indemnification agreement. And, if Sangoma were joined as a party, presumably they would assert that the patent claim already has been settled. That would be a defense to all parties, not just Sangoma. This is NOT legal advice but solely an off-the-cuff opinion as to how the American legal system works.