If you really want to pursue this...then the original holder of the intellectual property rights to Asterisk and issuer of the GPL (Digium) should be contacted and your concerns made known regarding release of the source code, which is required when executables are released.  I am assuming that the rights to the app-rpt module are, like the core, GPL'd, but held by the inheritor of Jim's IP.  Now, they can re-write from scratch the repeater module, but if they are basing it on the non-commercial Open Source version of Asterisk, then Digium's restrictions and requirements should be respected. 

That's what Digium has counsel for.  It's not up to us, per se, to manage, but the holder of the intellectual property rights to the software.  We can flail around and stamp our feet, but, in reality have no standing to force the issue--Digium does--which is why  complaints to the other party get blown off.  So, if it is THAT important, the owner of the rights (and it's not us, not the other party) should be consulted as to how THEY will enforce their intellectual property right.

Just a thought.  I'm not an intellectual property (or other) lawyer, nor do I play one on TV.  But, I  stayed in a Holiday Inn once. 

BB

 

On 7/13/2017 9:27 AM, Pierre Martel wrote:
interresting.

Le jeu. 13 juil. 2017 à 09:13, Alan Crosswell <n2ygk@weca.org> a écrit :
Unless he executed a commercial license: https://www.digium.com/products/asterisk/licensing

On Thu, Jul 13, 2017 at 9:00 AM, Willem Schreuder <willem@prinmath.com> wrote:
On Thu, 13 Jul 2017, Jeremy Utley wrote:

It's his right not to do so...

Absolutely not.  We all benefit from the work Mark Spencer and many others did in creating Asterisk.  Those folks released Asterisk under the GPL, which obligates EVERYBODY who uses Asterisk as a base to build something else to in turn release the source code.

If you refuse to release your source code, you may NOT use Asterisk.  If you don't want to release your code, go write your own Asterisk.