[asterisk-dev] SCF Licencing

Thu Oct 28 19:07:31 CDT 2010

Disclaimer: This is just an opinion and there is always a chance i am 100%
wrong.

So far as i can tell SCF in its current state to access the API you have to
create your client connection with the modified version of ICE (a middleware
application - http://www.zeroc.com) that digium provides (see the new git
server).  While I do agree that the statement in the license is somewhat
overbearing and unclear,  it is still true that if you compile your SCF
application against ICE which is GPLv2 licensed you will still be required
to provide the source code should you choose to distribute it.  Given that
digium has made modifications to the ICE tools I do not know if you are able
to connect with an unmodified version and avoid the restriction by simply
licensing the Ice middleware from ZeroC.

All that said i completely support Digium protecting their IP i just don't
agree with the language used in the 'interpretation'.  I feel that its
missing a few words and should somehow be modified to include the fact that
you would be using a client library to access the API remotely.

FYI, there is a SCF mailing list and this is likely where this conversation
belongs.  There are also some previously internal discussions on licensing
if you look at the mailing list archives.

Donny

On Thu, Oct 28, 2010 at 6:54 PM, Julian Lyndon-Smith <asterisk at dotr.com>wrote:

> so, what if I were to write a system like astmanproxy but for SCF,
> and licence that under the GPLv2 ?
>
> Would not that get around the problem entirely ? I am complying with
> Digium's interpretation , but not adding that extra clause to *my* API
> means that any program using *my* api is not bound by the GPLv2 .
>
> I think ;)
>
> This is absurd.
>
> Julian
>
> On 28 October 2010 23:33, Nicolas Gudino <nicolas at house.com.ar> wrote:
> > Hi Andrew,
> >
> > I do not have a problem with dual licensing! I have signed myself and
> contributed to Asterisk some years ago..
> >
> >  But to  "interpret"  that accesing a dual licensed/gpl2 network
> service/api incumbers the software accesing that api with the gpl2 license
> does not sound quite right to me. Perhaps I am wrong and someone can point
> me to the part of the license that implies that? If I write a sip based soft
> phone, should I license it as gpl2 because it talks to asterisk scf? Perhaps
> is not a good analogy, as the Asterisk AMI is not an open protocol but a
> particular Asterisk API exposed via sockets, just take it as an example.
> >
> > I agree with Julian, I am worried that Digium will try to close the apps
> ecosystem by trying to enforce gpl2 for applications that will access an AMI
> like API for this new project. Ang again, IANAL, but "interpretation" is a
> double edge word.
> >
> > Best regards,
> >
> > --
> > Nicolás Gudiño
> >
> > On Oct 28, 2010, at 7:11 PM, Andrew Latham wrote:
> >
> >> Some of us agree with Digium's interpretation.  The dual license model
> >> is difficult to understand but it is the only method to keep everyone
> >> happy.  If you have an app that you would like to add to Asterisk SCF
> >> then I invite you to contact the wonderful people at Digium.  Even
> >> their lawyers are cool!
> >>
> >>
> >>
> >> ~
> >> Andrew "lathama" Latham
> >> lathama at gmail.com
> >>
> >> * Learn more about OSS
> http://en.wikipedia.org/wiki/Open-source_software
> >> * Learn more about Linux http://en.wikipedia.org/wiki/Linux
> >> * Learn more about Tux http://en.wikipedia.org/wiki/Tux
> >>
> >>
> >>
> >> On Thu, Oct 28, 2010 at 7:01 PM, Marc Blanchet
> >> <marc.blanchet at viagenie.ca> wrote:
> >>> Le 10-10-28 22:56, Nicolas Gudino a écrit :
> >>>> I am also interested in this, and particulary how the paragraph
> starts:
> >>>>
> >>>> "It is Digium’s interpretation"
> >>>
> >>> In other words, they are trying to say "consult your lawyer".
> >>>
> >>> my 2 cents.
> >>>
> >>> Marc.
> >>>
> >>>>
> >>>>
> >>>> On Oct 28, 2010, at 6:36 PM, Julian Lyndon-Smith wrote:
> >>>>
> >>>>> I am very interested in this from the licence
> >>>>>
> >>>>> "It is Digium’s interpretation that because the Asterisk SCF APIs, by
> >>>>> definition, expose direct, and indirect, complex remote, and
> >>>>> non-remote, function calls on objects provided by Asterisk SCF’s
> >>>>> programs, that usage of these APIs between the program hosting the
> >>>>> object(s) and the program accessing the object(s) creates a
> derivative
> >>>>> work that must be covered wholly by GPLv2, even if the mechanism used
> >>>>> to invoke the function calls employs a cross-process or network
> >>>>> connection. As a result, any program that employs the Asterisk SCF
> >>>>> APIs to perform its intended functions, and would not be able to
> >>>>> perform those intended functions without using these APIs to
> >>>>> communicate with Asterisk SCF programs, or derivatives of Asterisk
> SCF
> >>>>> programs, is subject to the terms of the GPLv2 when it is
> distributed,
> >>>>> unless the distributor of the program has obtained explicit written
> >>>>> permission from Digium to distribute it under a different license."
> >>>>>
> >>>>> Does this mean if you use the SCF version of the Asterisk AMI, your
> >>>>> system then becones GPLv2 ?
> >>>>>
> >>>>> I don't think so. Guess this adopter won't be adopting ;)
> >>>>>
> >>>>> Unless, of course, (quite easiliy) I have the wrong end of the stick.
> >>>>> Please be it so.
> >>>>>
> >>>>> Julian
> >>>>>
> >>>>> --
> >>>>> Follow "Ode To Politics" by HB Tasker at http://twitter.com/HBTasker
> >>>>>
> >>>>> --
> >>>>> _____________________________________________________________________
> >>>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com--
> >>>>>
> >>>>> asterisk-dev mailing list
> >>>>> To UNSUBSCRIBE or update options visit:
> >>>>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> =========
> >>> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
> >>> Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
> >>> DTN news service: http://reeves.viagenie.ca
> >>> NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
> >>>
> >>>
> >>> --
> >>> _____________________________________________________________________
> >>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>>
> >>> asterisk-dev mailing list
> >>> To UNSUBSCRIBE or update options visit:
> >>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
> >>>
> >>
> >> --
> >> _____________________________________________________________________
> >> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >>
> >> asterisk-dev mailing list
> >> To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-dev
> >
> >
> > --
> > _____________________________________________________________________
> > -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> >
> > asterisk-dev mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-dev
> >
>
>
>
> --
> Follow "Ode To Politics" by HB Tasker at http://twitter.com/HBTasker
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20101028/5d2f18ae/attachment-0001.htm 