Re: [Openpbx-dev] New to OpenPBX development
Thank you everyone for replying me about the GPL stuffs :) GPL it is not very easy to understand in some situations :) Well, how can we start contributing to OpenPBX development? Antonio ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
What is said here is correct in regards to linkage. If something is executed though a TGI (or asterisk's later AGI/OpenPBX OGI) process, forked and exec'd from, and but tethered purely by I/O to the original server, there is no GNU GPL licensing issue whatsoever involved from that. If the application is linked to a GPL licensed (Not LGPL) library or includes GPL licensed code in it, then and only then, of course it is also subject to the GPL. As to how much one can charge for an application, or it's commercial viability, there is no such issue or limitation on what one may charge for an application distributed under GNU GPL so long as one lives by the license requirements. In fact, Dewar, who founded ADA Pro (now AdaCore), demonstrated this successfully selling GNU ADA at literally around $1million dollars for each GNU GPL licensed copy, along with support. RedHat is a growing public company successfully selling GNU GPL licensed software. Roy Sigurd Karlsbakk wrote: >>> Last but not least i've a license question. If my company develops an >>> AGI that work with OpenPBX, can we sell it in binary only form or >>> we're >>> forced to provide source code? I hope OpenPBX GPL will apply only >>> to the >>> OpenPBX source code and not also to external code (AGI, EAGI, FAGI, >>> extensions, etc.) >>> >> GPL state that any code linked with GPL becomes GPL - and has to be >> open >> source etc. The exception is if it is a binary, separated project >> witch >> functions also without OpenPBX. The rules are set out in the GPL text. >> GPL is written like a virus license, so you need to take care if you >> combine it with proprietary, non-open source. > > AGI/OGI is not touched by GPL unless you link (as in ld) against > libraries that are GPL. Using AGI/OGI over TCP or by fork/exec will > not invalidate GPL, and is indeed legal, no matter how much you > charge for the app :P > > roy > > ___ > Openpbx-dev mailing list > Openpbx-dev@openpbx.org > http://lists.openpbx.org/mailman/listinfo/openpbx-dev begin:vcard fn:David Sugar n:Sugar;David org:GNU Telephony email;internet:[EMAIL PROTECTED] tel;work:+1 201 215 2609 url:http://www.gnutelephony.org version:2.1 end:vcard ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
Legalities aside. If you are happy to use GPL'd code why would you not want your code to be GPL'd? While you are not obligated you might think about what others would think. Some companies make money out of writing software, and specialised software may be worth paying for. (I just bought Adobe Lightroom :P) roy___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
>> Last but not least i've a license question. If my company develops an >> AGI that work with OpenPBX, can we sell it in binary only form or >> we're >> forced to provide source code? I hope OpenPBX GPL will apply only >> to the >> OpenPBX source code and not also to external code (AGI, EAGI, FAGI, >> extensions, etc.) >> > GPL state that any code linked with GPL becomes GPL - and has to be > open > source etc. The exception is if it is a binary, separated project > witch > functions also without OpenPBX. The rules are set out in the GPL text. > GPL is written like a virus license, so you need to take care if you > combine it with proprietary, non-open source. AGI/OGI is not touched by GPL unless you link (as in ld) against libraries that are GPL. Using AGI/OGI over TCP or by fork/exec will not invalidate GPL, and is indeed legal, no matter how much you charge for the app :P roy ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
--- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > hi > > Last but not least i've a license question. If my company develops > an > > AGI that work with OpenPBX, can we sell it in binary only form or > we're > > forced to provide source code? I hope OpenPBX GPL will apply only > to the > > OpenPBX source code and not also to external code (AGI, EAGI, FAGI, > > > extensions, etc.) Have you read the text of the GPL? If gives a test. I'm prety sure that your AGI code would pass. You are not expanding or adding to OpenPBX but simply using it. Legalities aside. If you are happy to use GPL'd code why would you not want your code to be GPL'd? While you are not obligated you might think about what others would think. Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Office: 310-336-5189 [EMAIL PROTECTED] No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
hi > Last but not least i've a license question. If my company develops an > AGI that work with OpenPBX, can we sell it in binary only form or we're > forced to provide source code? I hope OpenPBX GPL will apply only to the > OpenPBX source code and not also to external code (AGI, EAGI, FAGI, > extensions, etc.) > GPL state that any code linked with GPL becomes GPL - and has to be open source etc. The exception is if it is a binary, separated project witch functions also without OpenPBX. The rules are set out in the GPL text. GPL is written like a virus license, so you need to take care if you combine it with proprietary, non-open source. Jan ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
Re: [Openpbx-dev] New to OpenPBX development
The free version of Asterisk was already GPL, so generally the licenses will be about the same... As to your AGI (OGI), it is executed as an external process and talks over pipes. It can be any license you like, as long as all the code it links to is that license or compatible with it. If you were to link to some openpbx libraries in your OGI, then it would need to be GPL. Of course you may want to have a lawyer go over it if you want to be really safe, but heh... Sam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Antonio Gallo Sent: Friday, March 23, 2007 3:49 AM To: Openpbx-dev@openpbx.org Subject: [Openpbx-dev] New to OpenPBX development Hello, i'm working for a company that produce Asterisk PBX hardware. We recognizie Digium's fault in providing a stable PBX platform. We're very interested in OpenPBX development. How to start contributing? I can put one of my guy spare time on some developer code, we can give a small money bounty for certain features, we can do some T38 testing (i've ordered every kind of ATA adapter they are incoming), we can do also extensive testing on phone VoIP and lines: - we are full of Snom 300,320,360 - we are full of BT200 and GXP2000 - we have some Thomson ST2030, ST2020 - we have BRI (we use Beronet chan_misdn) - we have 2 FXO (we usually use TDM400P) Hope we can switch to OpenPBX soon. Last but not least i've a license question. If my company develops an AGI that work with OpenPBX, can we sell it in binary only form or we're forced to provide source code? I hope OpenPBX GPL will apply only to the OpenPBX source code and not also to external code (AGI, EAGI, FAGI, extensions, etc.) Antonio ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
[Openpbx-dev] New to OpenPBX development
Hello, i'm working for a company that produce Asterisk PBX hardware. We recognizie Digium's fault in providing a stable PBX platform. We're very interested in OpenPBX development. How to start contributing? I can put one of my guy spare time on some developer code, we can give a small money bounty for certain features, we can do some T38 testing (i've ordered every kind of ATA adapter they are incoming), we can do also extensive testing on phone VoIP and lines: - we are full of Snom 300,320,360 - we are full of BT200 and GXP2000 - we have some Thomson ST2030, ST2020 - we have BRI (we use Beronet chan_misdn) - we have 2 FXO (we usually use TDM400P) Hope we can switch to OpenPBX soon. Last but not least i've a license question. If my company develops an AGI that work with OpenPBX, can we sell it in binary only form or we're forced to provide source code? I hope OpenPBX GPL will apply only to the OpenPBX source code and not also to external code (AGI, EAGI, FAGI, extensions, etc.) Antonio ___ Openpbx-dev mailing list Openpbx-dev@openpbx.org http://lists.openpbx.org/mailman/listinfo/openpbx-dev
