Re: [Ovillo] (OT) Sobre licencia en librerías, L GPL y EPL
A ver si ayudo en algo... GPL es una licencia de distribución, no de uso. Si un proyecto quiere usar tu software licenciado con GPL y distribuirlo con el suyo, tiene que licenciar su software bajo los términos de la GPL y poner a disposición el código fuente al momento de hacerlo. El LGPL quita esa condición, pudiendo distribuirlo dentro de software con cualquier otra licencia (sea o no privativa). Es permitido hacer modificaciones privadas a un software GPL sin necesidad de divulgarlas siempre y cuando no lo redistribuyas. Ahora, ya que el javascript no se compila, supongo que de todos modos estas distribuyendo el código fuente por internet... pero siempre puede otros usos donde no se distribuya como dentro de un swf o fuera de internet como en un programa XUL, el Script Host del Windows, o el Rhino JavaScript Compiler... Saludos 2008/1/17 Almorca [EMAIL PROTECTED]: La licencia LGPL es un licencia que permite aunar software libre con software privativo. Si tú creas un software y usas librerías bajo la LGPL puedes licenciar tu software bajo una licencia privativa pero debes indicar que parte de tu software está bajo licencia LGPL y debes poner esa parte del software a disposición de la gente que obtenga tu software. En este caso lo que poner el software a disposición del público es una tontería porque las librerías se pueden descargar desde su página, pero si las modificases y que deberías entregar las librerías a los clientes que te las pidiesen. No sé si me he explicado correctamente ya que es un poco difícil de explicar por email. 2008/1/16, Hari Seldon [EMAIL PROTECTED]: Buenas tardes: Hace algunos días que comentamos varias personas, acerca del uso de librerías y sus licencias; en concreto, hablamos de librerías javascript (o frameworks, aunque creo que no lo son a pesar de que en algunos sitios se les llame así); en concreto, son las librerías Ext JS y qooxdoo http://qooxdoo.org/license http://extjs.com/license En la primera, leemos: One important aspect of both licenses (so called weak copyleft licenses) is that if you make any modification or addition to the qooxdoo code itself, you MUST put your modification under the same license, the LGPL or EPL. Note that it is explicitely NOT NEEDED to put any application that is just using qooxdoo as intended by the framework under the LGPL or EPL (this is where the weak part comes into play - contrast this with the GPL, which would only allow using qooxdoo to create an application that is itselft governed by the GPL). Sin embargo, en la segunda, leemos: Open Source License Ext is also licensed under the terms of the Open Source LGPL 3.0 license. You may use our open source license if you: * Want to use Ext in an open source project that precludes using non-open source software * Plan to use Ext in a personal, educational or non-profit manner * Are using Ext in a commercial application that is not a software development library or toolkit, you will meet LGPL requirements and you do not wish to support the Project Lo cual parece una contradicción; sin embargo, leyendo los términos de la LGPL 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: * a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. * b) Accompany the Combined Work with a copy of the GNU GPL and this license document. * c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. * d) Do one of the following: o 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. o 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. * e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the
Re: [Ovillo] (OT) Sobre licencia en librerías, L GPL y EPL
La licencia LGPL es un licencia que permite aunar software libre con software privativo. Si tú creas un software y usas librerías bajo la LGPL puedes licenciar tu software bajo una licencia privativa pero debes indicar que parte de tu software está bajo licencia LGPL y debes poner esa parte del software a disposición de la gente que obtenga tu software. En este caso lo que poner el software a disposición del público es una tontería porque las librerías se pueden descargar desde su página, pero si las modificases y que deberías entregar las librerías a los clientes que te las pidiesen. No sé si me he explicado correctamente ya que es un poco difícil de explicar por email. 2008/1/16, Hari Seldon [EMAIL PROTECTED]: Buenas tardes: Hace algunos días que comentamos varias personas, acerca del uso de librerías y sus licencias; en concreto, hablamos de librerías javascript (o frameworks, aunque creo que no lo son a pesar de que en algunos sitios se les llame así); en concreto, son las librerías Ext JS y qooxdoo http://qooxdoo.org/license http://extjs.com/license En la primera, leemos: One important aspect of both licenses (so called weak copyleft licenses) is that if you make any modification or addition to the qooxdoo code itself, you MUST put your modification under the same license, the LGPL or EPL. Note that it is explicitely NOT NEEDED to put any application that is just using qooxdoo as intended by the framework under the LGPL or EPL (this is where the weak part comes into play - contrast this with the GPL, which would only allow using qooxdoo to create an application that is itselft governed by the GPL). Sin embargo, en la segunda, leemos: Open Source License Ext is also licensed under the terms of the Open Source LGPL 3.0 license. You may use our open source license if you: * Want to use Ext in an open source project that precludes using non-open source software * Plan to use Ext in a personal, educational or non-profit manner * Are using Ext in a commercial application that is not a software development library or toolkit, you will meet LGPL requirements and you do not wish to support the Project Lo cual parece una contradicción; sin embargo, leyendo los términos de la LGPL 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: * a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. * b) Accompany the Combined Work with a copy of the GNU GPL and this license document. * c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. * d) Do one of the following: o 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. o 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. * e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) Parece que dan la razón a la primera de las librerías. Con lo cual, planteemos el supuesto que planteábamos estas personas y yo; supongamos que desarrollo una aplicación de gestión (sobre PHP + Symfony + MySQL/PostgreSQL para ser concretos), para llevar una emisión de facturas; y supongamos que para el front-end, en vez de utilizar unas librerías más genéricas (o bien Javascript escrito desde 0), utilizo las librerías Ext JS; hago
