[Asterisk-Users] Help with GPL license of Asterisk

[Armand A. Verstappen]

Hi,

On Mon, 2003-09-29 at 16:40, Mark Spencer wrote:
> > 1) if your application is not released to a 3rd party, you do not have
> > to make the source available
> 
> This is TRUE.
> 
> > 2) if you build your application as a module that loads into a stock
> > asterisk server, you do not have to disclose your source
> 
> This is FALSE.  Even modules for Asterisk MUST be released under GPL,
> unless you obtain a license to release them outside of GPL from Digium.

Maybe this should be re-thought? Allowing third parties to release
modules under a non-GPL license (through a 'Mark exception' analogue to
the 'Linus exception referenced below) could be intresting.
A third party that really wants to release under a non-GPL license can
do so by creating their application as an AGI script, or have it work
using the management interface. Heck, they could release a wrapper to
'exec()' as GPL, and then use that application to call their non-gpl'ed
code anyway, right?
So, if 3rd parties are doing or going to do that, then why not allow
them to do it in a way that doesn't require bypassing proper design?
A third party could then for example start selling G.723 codecs, if they
are prepared to pay the fee that allows them to do so.

> > 3) if you need to make changes to the core in order for your application
> > to work, you'll need to disclose source for your changes to the core,
> > but not for your application.  This sounds horrid, but it's not too bad,
> > as your simply augmenting the core API and keeping your goodies in the
> > binary only portion of the release.
> 
> This is also FALSE.  You MUST release both the module AND core changes
> unless you obtain license from Digium.  I believe you are confusing the
> "Linus exception" which is an exception for the Linux kernel explicitly
> made by Linus Torvalds, allowing binary only modules to the kernel only.

My suggestion above is based on my own egoistic view as a user of the
software. I have no intention to create non-GPLed modules myself, but
wouldn't mind to pay for some kind of third party module that does
something for me thats not available in GPLed code. I prefer GPL, other
forms of open source (payed for or not) is acceptable. I dislike closed
source, but if it solves my problem against an acceptable rate with
acceptable service and support, why not. 

With a 'mark exception', I'd be able to run GLP-ed asterisk with a
channel driver from a third party. Win for me. Without the 'mark
exception', I'll have to purchase a non-GPLed version of Asterisk, as
well as the third parties' module. I'm not clear if that will lock me
into paying upgrade fees to Digium, or if a non-GPL license will still
allows me to follow CVS as I do now. I'll have the same question
regarding the third party's module in the other case of course.

I'm not sure how a 'mark/digium exception' would work out for the the
Asterisk community. A third party would no longer be required to pay a
fee for a non-GPLed Asterisk, and Digium would loose some revenue. Since
Digium still is the primary sponsor of Asterisk development, this is a
loss for the community. On the other hand, it is possible that under the
suggested construction many more third party modules spring to live,
causing Asterisk to be more usable for businesses, in turn generating
more revenue for Digium. And, since third parties would benefit from a
more stable Asterisk, there may be more parties be actively involved in
maintaining and extending the core. I have no idea which way the balance
would swing.

wkr,

-- 
Envida                     http://www.envida.net/
Armand A. Verstappen       Graadt van Roggenweg 328
armand at nl.envida.net       3531 AH Utrecht
tel: +31 (0)30 298 2255    Postbus 19127
fax: +31 (0)30 298 2111    3501 DC Utrecht
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20030929/44ce0600/attachment.pgp