2013/10/19 Matthew Jordan <mjordan at digium.com>: > > There's a number of licensing issues - both with ARI and with PJSIP - that I > have as an action from AstriDevCon to get concrete answers on. I should have > the answers to this and other questions in the next week or two. > > As a "non-official, off the cuff, take this with a grain of salt" statement, > I'd at least make sure that if you don't want your library released as GPL, > don't have any aspect of the resource JSON reproduced verbatim in your > library. > I see this could be an issue with ARI - not much for what I'm doing now, because we could always add a second GPLv2 repo, keep all files from Asterisk there under the GPLv2 and downloading them when someone wants to build the library, that I guess ill not be made very often bu the general public - but if you use a dynamically typed language and want the interfaces build at runtime (like Javascript Swagger does) you need to include the definitions in your software/library, and so this end up affecting the licensing you can use. Basically anything you do will have to be GPL then. Tonight, I noticed that the Asterisk license specifies: "In addition, Asterisk implements two management/control protocols: the Asterisk Manager Interface (AMI) and the Asterisk Gateway Interface (AGI). It is our belief that applications using these protocols to manage or control an Asterisk instance do not have to be licensed under the GPL or a compatible license...." Maybe the ARI and and its definition files should fall under these provisions. Just my two cents l. (ari4java update: As of tonight, all objects deserialize okay, including messages that are deserialized with their correct Java type and interfaces) :) -- Loway - home of QueueMetrics - http://queuemetrics.com Try the WombatDialer auto-dialer @ http://wombatdialer.com
