Durante años yo siempre crei que solamente existia una licensia de Softwarelibre la GNU/GPL. Pero vaya que la vida da sorpresas. El otro dia agregue un proyecto al Sourceforge.net el sitio web con mas Software Open Source que jamas haya visto, y al agregar el proyecto me pidio que eligiera entre mas de 30 licensias tipo GNU (wow). Algo consternado decidi investigar y aqui les dejo los resultados de esta investigacion, es algo largo y en ingles, asi que no se desesperen:
Por principio de cuentas, para que una licensia sea considerada Open Source se analizan los siguientes 4 puntos:
- En donde califica como licensia de Software Libre
- Que sea un Copyleft (Copyleft es un juego de palabras en ingles que quiere decir lo contrario a copyright, esta palabra esta asociada a Richard Stallman y el movimiento GNU)
- Que la licensia sea compatible con los principios del GNU/GPL (GNU = GNU is not Unix and GPL = General Public Licenses) version GPLv2 y GPLv3
- Si puede llegar a causar problemas practicos.
Ahora veremos solamente algunas de las licensias, ya que el trabajo de explicarlas todas es demasiado y en mi empleo en softtek me exigen tambien trabajar (ellos pagan) pues solamente pondre las primeras 7, las demas les dejare los links y la documentacion completa. Todas estas licensias siguen el conceptop de GNU y el SoftwareLibre.
Cabe aclarar que el software libre no solo abarca la seccion de Software, sino tambien la seccion creativa o de entretenimiento (video, dibujos, graficos, fotografia, etc), la seccion educativa y la seccion de documentacion entre otras cosas:
- GNU General Public License (GPL) version 3
- Esta es la última versión de la GNU GPL: una licencia de software libre, y una licencia copyleft. Se recomienda que para la mayoría de paquetes de software.Tenga en cuenta que la GPLv3 no es compatible con GPLv2 por sí mismo. Sin embargo, la mayoría del software publicado bajo GPLv2 le permite utilizar los términos de las versiones posteriores de la GPL también. Cuando este es el caso, puede utilizar el código bajo GPLv3 a hacer la combinación deseada.
GNU Lesser General Public License (LGPL) version 3
- Esta es la última versión de la GNU GPL: una licencia de software libre, pero no una licensia fuerte de copyleft, por que esta permite el uso de modulos que no son libres. Esta licensia es compatible con la GPLv3. Recomendamos el uso de esta licensia solamente en circunstancias especiales.Tenga en cuenta que la GPLv3 no es compatible con GPLv2 por sí mismo. Sin embargo, la mayoría del software publicado bajo GPLv2 le permite utilizar los términos de las versiones posteriores de la GPL también. Cuando este es el caso, puede utilizar el código bajo GPLv3 a hacer la combinación deseada.
- Apple’s Common Documentation License, Version 1.0
- Esta es una licencia de documentación libre que es incompatible con la GNU FDL. Es incompatible porque la sección (2c) dice: «Usted no debe añadir otros términos o condiciones a los de esta licencia», y la GNU FDL tiene términos adicionales no contabilizados en común de la Licencia de Documentación.
- Modified BSD license
- (Nota: en el hiperenlace precedente, la licencia BSD esta modificada en la lista de la sección General.)Esta es la licencia BSD original, modificada por la eliminación de la cláusula de publicidad. Es un simple y permisiva sin copyleft licencia de software libre, compatible con la GNU GPL.
Si quieres un simple y permisiva sin licencia de software libre, copyleft, la licencia BSD modificada es una opción razonable. Sin embargo, es arriesgado recomendar el uso de la «licencia BSD», porque la confusión puede ocurrir fácilmente y llevar a la utilización de la licencia BSD original defectuosa. Para evitar este riesgo, se puede sugerir la licencia X11 lugar. La licencia X11 y la revisión de licencia BSD son más o menos equivalentes.
Esta licensia esta algunas veces referidas a la clausula-3 BSD.
- Creative Commons Attribution-Sharealike 2.0 license (a.k.a. CC-BY-SA)
- Esta es una licencia copyleft libre que es bueno para las obras artísticas y de entretenimiento, y de las obras educativas. Por favor, no la utilice para el software o la documentación, puesto que es incompatible con la GNU GPL y con la GNU FDL.Por favor, véase el comentario adicional acerca de las licencias Creative Commons justo encima.
- GNU Free Documentation License
- La GNU FDL se recomienda para los libros de texto y materiales de enseñanza para todos los temas. ( «Documentación» significa simplemente los libros de texto y otros materiales didácticos para la utilización de equipos o programas informáticos.) Recomendamos también la GNU FDL para diccionarios, enciclopedias, y cualquier otra información que proporcionan las obras de uso práctico.
- Apache License, Version 2.0
-
Esta es una licencia de software libre, compatible con la versión 3 de la GPL.Tenga en cuenta que esta licencia no es compatible con la GPL versión 2, ya que tiene algunos requisitos que no están en la versión anterior. Entre ellos figuran algunos de terminación de patente y disposiciones de indemnización.
Como pueden ver las licensias son multiples y muy variadas, despues del salto de pagina podran ver el resto de las licensias GNU y las que son GNU en parte, estos links son en ingles y las documentaciones tambien. Tambien les dejo las descripciones de mas licensias para que las analizen.
Las siguientes licensias han sido aprobadas por la OSI por medio de la License Review Process.
- Academic Free License
- Adaptive Public License
- Apache Software License
- Apache License, 2.0
- Apple Public Source License
- Artistic license
- Artistic license 2.0
- Attribution Assurance Licenses
- New and Simplified BSD licenses
- Boost Software License (BSL1.0)
- Computer Associates Trusted Open Source License 1.1
- Common Development and Distribution License
- Common Public Attribution License 1.0 (CPAL)
- Common Public License 1.0
- CUA Office Public License Version 1.0
- EU DataGrid Software License
- Eclipse Public License
- Educational Community License, Version 2.0
- Eiffel Forum License
- Eiffel Forum License V2.0
- Entessa Public License
- Fair License
- Frameworx License
- GNU General Public License (GPL)
- GNU General Public License version 3.0 (GPLv3)
- GNU Library or «Lesser» General Public License (LGPL)
- GNU Library or «Lesser» General Public License version 3.0 (LGPLv3)
- Historical Permission Notice and Disclaimer
- IBM Public License
- Intel Open Source License
- Jabber Open Source License
- Lucent Public License (Plan9)
- Lucent Public License Version 1.02
- Microsoft Public License (Ms-PL)
- Microsoft Reciprocal License (Ms-RL)
- MIT license
- MITRE Collaborative Virtual Workspace License (CVW License)
- Motosoto License
- Mozilla Public License 1.0 (MPL)
- Mozilla Public License 1.1 (MPL)
- Multics License
- NASA Open Source Agreement 1.3
- Naumen Public License
- Nethack General Public License
- Nokia Open Source License
- OCLC Research Public License 2.0
- Open Group Test Suite License
- Open Software License
- PHP License
- Python license (CNRI Python License)
- Python Software Foundation License
- Qt Public License (QPL)
- RealNetworks Public Source License V1.0
- Reciprocal Public License
- Reciprocal Public License 1.5 (RPL1.5)
- Ricoh Source Code Public License
- Simple Public License 2.0
- Sleepycat License
- Sun Industry Standards Source License (SISSL)
- Sun Public License
- Sybase Open Watcom Public License 1.0
- University of Illinois/NCSA Open Source License
- Vovida Software License v. 1.0
- W3C License
- wxWindows Library License
- X.Net License
- Zope Public License
- zlib/libpng license
Aqui esta la lista completa de la descripcion de cada licensia, esta version no esta traducida y es la fuente en donde me base para crear las traducciones:
Software Licenses
GPL-Compatible Free Software Licenses
The following licenses qualify as free software licenses, and are compatible with the GNU GPL.
- GNU General Public License (GPL) version 3
- This is the latest version of the GNU GPL: a free software license, and a copyleft license. We recommend it for most software packages.Please note that GPLv3 is not compatible with GPLv2 by itself. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination.
- GNU General Public License (GPL) version 2
- This is the previous version of the GNU GPL: a free software license, and a copyleft license. We recommend the latest version for most software.Please note that GPLv2 is, by itself, not compatible with GPLv3. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination.
- GNU Lesser General Public License (LGPL) version 3
- This is the latest version of the LGPL: a free software license, but not a strong copyleft license, because it permits linking with non-free modules. It is compatible with GPLv3. We recommend it for special circumstances only.Please note that LGPLv3 is not compatible with GPLv2 by itself. However, most software released under GPLv2 allows you to use the terms of later versions of the GPL as well. When this is the case, you can use the code under GPLv3 to make the desired combination.
- GNU Lesser General Public License (LGPL) version 2.1
- This is the previous version of the LGPL: a free software license, but not a strong copyleft license, because it permits linking with non-free modules. It is compatible with GPLv2 and GPLv3. We generally recommend the latest version of the LGPL, for special circumstances only.
- GNU Affero General Public License (AGPL) version 3
- This is a free software, copyleft license. Its terms effectively consist of the terms of GPLv3, with an additional paragraph in section 13 to allow users who interact with the licensed software over a network to receive the source for that program. We recommend that developers consider using the GNU AGPL for any software which will commonly be run over a network.Please note that the GNU AGPL is not compatible with GPLv2. It is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and use it under the terms of GPLv3, or vice versa. However, you are allowed to combine separate modules or source files released under both of those licenses in a single project, which will provide many programmers with all the permission they need to make the programs they want. See section 13 of both licenses for details.
- Apache License, Version 2.0
- This is a free software license, compatible with version 3 of the GPL.Please note that this license is not compatible with GPL version 2, because it has some requirements that are not in the older version. These include certain patent termination and indemnification provisions.
- Artistic License 2.0
- This license is a free software license, compatible with the GPL thanks to the relicensing option in section 4(c)(ii).
- Clarified Artistic License
- This license is a free software license, compatible with the GPL. It is the minimal set of changes needed to correct the vagueness of the Artistic License 1.0.
- Berkeley Database License (aka the Sleepycat Software Product License)
- This is a free software license, compatible with the GNU GPL.
- Boost Software License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.
- Modified BSD license
- (Note: on the preceding link, the modified BSD license is listed in the General section.)This is the original BSD license, modified by removal of the advertising clause. It is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.
If you want a simple, permissive non-copyleft free software license, the modified BSD license is a reasonable choice. However, it is risky to recommend use of “the BSD license”, because confusion could easily occur and lead to use of the flawed original BSD license. To avoid this risk, you can suggest the X11 license instead. The X11 license and the revised BSD license are more or less equivalent.
This license is sometimes referred to as the 3-clause BSD license.
- CeCILL version 2
- The CeCILL is a free software license, explicitly compatible with the GNU GPL.The text of the CeCILL uses a couple of biased terms that ought to be avoided: “intellectual property” (see this article) and “protection” (see this article); this decision was unfortunate, because reading the license tends to spread the presuppositions of those terms. However, this does not cause any particular problem for the programs released under the CeCILL.
Section 9.4 of the CeCILL commits the program’s developers to certain forms of cooperation with the users, if someone attacks the program with a patent. You might look at that as a problem for the developer; however, if you are sure you would want to cooperate with the users in those ways anyway, then it isn’t a problem for you.
- Cryptix General License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL. It is very similar to the X11 license.
- eCos license version 2.0
- The eCos license version 2.0 is a GPL-compatible free software license. It consists of the GPL, plus an exception allowing linking to software not under the GPL. This license has the same disadvantages as the LGPL.
- Eiffel Forum License, version 2
- This is a free software license, compatible with the GNU GPL. Previous releases of the Eiffel license are not compatible with the GPL.
- EU DataGrid Software License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.
- Expat License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL. It is sometimes ambiguously referred to as the MIT License.
- FreeBSD license
- This is the original BSD license with the advertising clause and another clause removed. (It is also sometimes called the “2-clause BSD license”.) It is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.If you want a simple, permissive non-copyleft free software license, the FreeBSD license is a reasonable choice. However, please don’t call it a “BSD” or “BSD-style” license, because that is likely to cause confusion which could lead to use of the flawed original BSD license.
- License of the iMatix Standard Function Library
- This is a free software license and is GPL compatible.
- Intel Open Source License
- This is a Free Software license, compatible with the GNU GPL.
- Microsoft Public License (Ms-PL)
- This is a free software license, compatible with version 3 of the GNU GPL. It is incompatible with version 2 of the GNU GPL because of the conditions in sections 3(B) and 3(C).Please do not use this license for anything you write; there are already well-known free software licenses that serve the same purpose, such as the Apache License version 2.0, and we must all stand together to combat license proliferation. However, there is no reason to avoid using software released under this license.
- NCSA/University of Illinois Open Source License
- This license is based on the terms of the Expat and modified BSD licenses. It is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.
- License of Netscape Javascript
- This is the disjunction of the Netscape Public License and the GNU GPL. Because of that, it is a free software license, compatible with the GNU GPL, but not a strong copyleft.This disjunctive license is a good choice if you want to make your package GPL-compatible and MPL-compatible. However, you can also accomplish that by using the LGPL or the Guile license.
Such a disjunctive license might be a good choice if you have been using the MPL, and want to change to a GPL-compatible license without subtracting any permission you have given for previous versions.
- OpenLDAP License, Version 2.7
- This is a permissive non-copyleft free software license that is compatible with the GNU GPL.
- License of Perl 5 and below
- This license is the disjunction of the Artistic License 1.0 and the GNU GPL—in other words, you can choose either of those two licenses. It qualifies as a free software license, but it may not be a real copyleft. It is compatible with the GNU GPL because the GNU GPL is one of the alternatives.We recommend you use this license for any Perl 4 or Perl 5 package you write, to promote coherence and uniformity in Perl programming. Outside of Perl, we urge you not to use this license; it is better to use just the GNU GPL.
- Public Domain
- Being in the public domain is not a license; rather, it means the material is not copyrighted and no license is needed. Practically speaking, though, if a work is in the public domain, it might as well have an all-permissive non-copyleft free software license. Public domain material is compatible with the GNU GPL.
- License of Python 2.0.1, 2.1.1, and newer versions
- This is a free software license and is compatible with the GNU GPL. Please note, however, that intermediate versions of Python (1.6b1, through 2.0 and 2.1) are under a different license (see below).
- License of Python 1.6a2 and earlier versions
- This is a free software license and is compatible with the GNU GPL. Please note, however, that newer versions of Python are under other licenses (see above and below).
- License of Ruby
- This is a free software license, compatible with the GPL via an explicit dual-licensing clause.
- Standard ML of New Jersey Copyright License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL.
- License of Vim, Version 6.1 or later
- This is a free software license, partially copyleft but not really. It is compatible with the GPL, by an explicit conversion clause.
- W3C Software Notice and License
- This is a free software license and is GPL compatible.
- X11 License
- This is a simple, permissive non-copyleft free software license, compatible with the GNU GPL. Older versions of XFree86 used the same license, and some of the current variants of XFree86 also do. Later versions of XFree86 are distributed under the XFree86 1.1 license.This license is sometimes called the MIT license, but that term is misleading, since MIT has used many licenses for software.
- XFree86 1.1 License
- This is a simple, permissive non-copyleft free software license, compatible with version 3 of the GPL.Please note that this license is incompatible with version 2 of the GPL, because of its requirements that apply to all documentation in the distribution that contain acknowledgements.
There are currently several variants of XFree86, and only some of them use this license. Some continue to use the X11 license.
- License of ZLib
- This is a free software license, and compatible with the GPL.
- Zope Public License version 2.0
- This is a simple, permissive non-copyleft free software license which is compatible with the GNU GPL.
GPL-Incompatible Free Software Licenses
The following licenses are free software licenses, but are not compatible with the GNU GPL.
- Affero General Public License version 1
- The Affero General Public License is a free software license, copyleft, and incompatible with the GNU GPL. It consists of the GNU GPL version 2, with one additional section that Affero added with FSF approval. The new section, 2(d), covers the distribution of application programs through web services or computer networks.This license has been succeeded by the GNU Affero General Public License version 3; please use that instead.
- Academic Free License, all versions through 3.0
- The Academic Free License is a free software license, not copyleft, and incompatible with the GNU GPL. Recent versions contain contract clauses similar to the Open Software License, and should be avoided for the same reasons.
- Apache License, Version 1.1
- This is a permissive non-copyleft free software license. It has a few requirements that render it incompatible with the GNU GPL, such as strong prohibitions on the use of Apache-related names.
- Apache License, Version 1.0
- This is a simple, permissive non-copyleft free software license with an advertising clause. This creates practical problems like those of the original BSD license, including incompatibility with the GNU GPL.
- Apple Public Source License (APSL), version 2
- This is a free software license, incompatible with the GNU GPL. We recommend that you not use this license for new software that you write, but it is ok to use and improve the software released under this license. More explanation.
- Original BSD license
- (Note: on the preceding link, the original BSD license is listed in the UCB/LBL section. This license is also sometimes called the “4-clause BSD license”.)This is a simple, permissive non-copyleft free software license with a serious flaw: the “obnoxious BSD advertising clause”. The flaw is not fatal; that is, it does not render the software non-free. But it does cause practical problems, including incompatibility with the GNU GPL.
We urge you not to use the original BSD license for software you write. If you want to use a simple, permissive non-copyleft free software license, it is much better to use the modified BSD license or the X11 license. However, there is no reason not to use programs that have been released under the original BSD license.
- Common Development and Distribution License (CDDL)
- This is a free software license. It has a copyleft with a scope that’s similar to the one in the Mozilla Public License, which makes it incompatible with the GNU GPL. This means a module covered by the GPL and a module covered by the CDDL cannot legally be linked together. We urge you not to use the CDDL for this reason.Also unfortunate in the CDDL is its use of the term «intellectual property».
- Common Public License Version 1.0
- This is a free software license. Unfortunately, it has a choice of law clause which makes it incompatible with the GNU GPL.
- Condor Public License
- This is a free software license. It has a couple of requirements that make it incompatible with the GNU GPL, including strong restrictions on the use of Condor-related names, and a condition that you must comply with United States export laws.
- Eclipse Public License Version 1.0
- The Eclipse Public License is similar to the Common Public License, and our comments on the CPL apply equally to the EPL. The only change is that the EPL removes the broader patent retaliation language regarding patent infringement suits specifically against Contributors to the EPL’d program.
- IBM Public License, Version 1.0
- This is a free software license. Unfortunately, it has a choice of law clause which makes it incompatible with the GNU GPL.
- Interbase Public License, Version 1.0
- This is a free software license that is essentially the same as the Mozilla Public License, Version 1.1. Like the MPL, the IPL has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the IPL cannot legally be linked together. We urge you not to use the IPL for this reason.
- Jabber Open Source License, Version 1.0
- The license is a free software license, incompatible with the GPL. It permits relicensing under a certain class of licenses, those which include all the requirements of the Jabber license. The GPL is not a member of that class, so the Jabber license does not permit relicensing under the GPL. Therefore, it is not compatible.
- LaTeX Project Public License 1.3a
- We have not written a full analysis of this license, but it is a free software license, with less stringent requirements on distribution than LPPL 1.2 (described next). It is still incompatible with the GPL because some modified versions must include a copy of or pointer to an unmodified version.
- LaTeX Project Public License 1.2
- This license is an incomplete statement of the distribution terms for LaTeX. As far as it goes, it is a free software license, but incompatible with the GPL because it has many requirements that are not in the GPL.This license contains complex and annoying restrictions on how to publish a modified version, including one requirement that falls just barely on the good side of the line of what is acceptable: that any modified file must have a new name.
The reason this requirement is acceptable for LaTeX is that TeX has a facility to allow you to map file names, to specify “use file bar when file foo is requested”. With this facility, the requirement is merely annoying; without the facility, the same requirement would be a serious obstacle, and we would have to conclude it makes the program non-free.
The LPPL says that some files, in certain versions of LaTeX, may have additional restrictions, which could render them non-free. For this reason, it may take some careful checking to produce a version of LaTeX that is free software.
The LPPL makes the controversial claim that simply having files on a machine where a few other people could log in and access them in itself constitutes distribution. We believe courts would not uphold this claim, but it is not good for people to start making the claim.
Please do not use this license for any other project.
Note: These comments are for version 1.2 (3 Sep 1999) of the LPPL.
- Lucent Public License Version 1.02 (Plan 9 license)
- This is a free software license, but it is incompatible with the GNU GPL because of its choice of law clause. We recommend that you not use this license for new software that you write, but it is ok to use and improve Plan 9 under this license.
- Microsoft Reciprocal License (Ms-RL)
- This is a free software license; it has a copyleft that is not strong, but incompatible with the GNU GPL. We urge you not to use the Ms-RL for this reason.
- Mozilla Public License (MPL)
- This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason.However, MPL 1.1 has a provision (section 13) that allows a program (or parts of it) to offer a choice of another license as well. If part of a program allows the GNU GPL as an alternate choice, or any other GPL-compatible license as an alternate choice, that part of the program has a GPL-compatible license.
- Netizen Open Source License (NOSL), Version 1.0
- This is a free software license that is essentially the same as the Mozilla Public License, Version 1.1. Like the MPL, the NOSL has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the NOSL cannot legally be linked together. We urge you not to use the NOSL for this reason.
- Netscape Public License (NPL), versions 1.0 and 1.1
- This is a free software license, not a strong copyleft, and incompatible with the GNU GPL. It consists of the Mozilla Public License with an added clause that permits Netscape to use your added code even in their proprietary versions of the program. Of course, they do not give you permission to use their code in the analogous way. We urge you not to use the NPL.
- Nokia Open Source License
- This is similar to the Mozilla Public License: a free software license incompatible with the GNU GPL.
- Old OpenLDAP License, Version 2.3
- This is a permissive non-copyleft free software license with a few requirements (in sections 4 and 5) that render it incompatible with the GNU GPL. Note that the latest version of OpenLDAP has a different license that is compatible with the GNU GPL.We urge you not to use the older OpenLDAP license for software you write. However, there is no reason to avoid running programs that have been released under this license.
- Open Software License, all versions through 3.0
- The Open Software License is a free software license. It is incompatible with the GNU GPL in several ways.Recent versions of the Open Software License have a term which requires distributors to try to obtain explicit assent to the license. This means that distributing OSL software on ordinary FTP sites, sending patches to ordinary mailing lists, or storing the software in an ordinary version control system, is arguably a violation of the license and would subject you to possible termination of the license. Thus, the Open Software License makes it very difficult to develop software using the ordinary tools of free software development. For this reason, and because it is incompatible with the GPL, we recommend that no version of the OSL be used for any software.
We urge you not to use the Open Software License for software you write. However, there is no reason to avoid running programs that have been released under this license.
- OpenSSL license
- The license of OpenSSL is a conjunction of two licenses, one of them being the license of SSLeay. You must follow both. The combination results in a copyleft free software license that is incompatible with the GNU GPL. It also has an advertising clause like the original BSD license and the Apache license.We recommend using GNUTLS instead of OpenSSL in software you write. However, there is no reason not to use OpenSSL and applications that work with OpenSSL.
- Phorum License, Version 2.0
- This is a free software license but it is incompatible with the GPL. Section 5 makes the license incompatible with the GPL.
- PHP License, Version 3.01
- This license is used by most of PHP4. It is a non-copyleft free software license. It is incompatible with the GNU GPL because it includes strong restrictions on the use of «PHP» in the name of derived products.We recommend that you not use this license for anything except PHP add-ons.
- License of Python 1.6b1 through 2.0 and 2.1
- This is a free software license but is incompatible with the GNU GPL. The primary incompatibility is that this Python license is governed by the laws of the State of Virginia, in the USA, and the GPL does not permit this.
- Q Public License (QPL), Version 1.0
- This is a non-copyleft free software license which is incompatible with the GNU GPL. It also causes major practical inconvenience, because modified sources can only be distributed as patches.We recommend that you avoid using the QPL for anything that you write, and use QPL-covered software packages only when absolutely necessary. However, this avoidance no longer applies to Qt itself, since Qt is now also released under the GNU GPL.
Since the QPL is incompatible with the GNU GPL, you cannot take a GPL-covered program and QPL-covered program and link them together, no matter how.
However, if you have written a program that uses QPL-covered library (called FOO), and you want to release your program under the GNU GPL, you can easily do that. You can resolve the conflict for your program by adding a notice like this to it:
As a special exception, you have permission to link this program with the FOO library and distribute executables, as long as you follow the requirements of the GNU GPL in regard to all of the software in the executable aside from FOO.
You can do this, legally, if you are the copyright holder for the program. Add it in the source files, after the notice that says the program is covered by the GNU GPL.
- RealNetworks Public Source License (RPSL), Version 1.0
- The RPSL is a free software license that is GPL-incompatible for a number of reasons: it requires that derivative works be licensed under the terms of the RPSL, and mandates that any litigation take place in Seattle, Washington.
- Sun Industry Standards Source License 1.0
- This is a free software license, not a strong copyleft, which is incompatible with the GNU GPL because of details rather than any major policy.
- Sun Public License
- This is essentially the same as the Mozilla Public License: a free software license incompatible with the GNU GPL. Please do not confuse this with the Sun Community Source License which is not a free software license.
- License of xinetd
- This is a copyleft free software license, incompatible with the GPL. It is incompatible because it places extra restrictions on redistribution of modified versions that contradict the redistribution requirements in the GPL.
- Zend License, Version 2.0
- This license is used by one part of PHP4. It is a non-copyleft free software license which is incompatible with the GNU GPL, and has practical problems like those of the original BSD license.We recommend that you not use this license for anything you write.
- Zope Public License version 1
- This is a simple, fairly permissive non-copyleft free software license with practical problems like those of the original BSD license, including incompatibility with the GNU GPL.We urge you not to use the ZPL version 1 for software you write. However, there is no reason to avoid running programs that have been released under this license, such as previous versions of Zope.
Version 2.0 of the Zope Public License is GPL-compatible.
Non-Free Software Licenses
The following licenses do not qualify as free software licenses. A non-free license is automatically incompatible with the GNU GPL.
Of course, we urge you to avoid using non-free software licenses, and to avoid non-free software in general.
There is no way we could list all the known non-free software licenses here; after all, every proprietary software company has its own. We focus here on licenses that are often mistaken for free software licenses but are, in fact, not free software licenses.
We have provided links to these licenses when we can do so without violating our general policy: that we do not make links to sites that promote, encourage or facilitate the use of non-free software packages. The last thing we want to do is give any non-free program some gratis publicity that might encourage more people to use it. For the same reason, we have avoided naming the programs for which a license is used, unless we think that for specific reasons it won’t backfire.
- Aladdin Free Public License
- Despite its name, this is not a free software license because it does not allow charging for distribution, and largely prohibits simply packaging software licensed under it with anything for which a charge is made.
- Apple Public Source License (APSL), version 1.x
- Versions 1.0, 1.1 and 1.2 are not free software licenses (follow the link for more explanation). Please don’t use these licenses, and we urge you to avoid any software that has been released under them. Version 2.0 of the APSL is a free software license.
- Artistic License 1.0
- We cannot say that this is a free software license because it is too vague; some passages are too clever for their own good, and their meaning is not clear. We urge you to avoid using it, except as part of the disjunctive license of Perl.
- AT&T Public License
- The AT&T Public License is a non-free license. It has several serious problems:
- The patent license is voided by any modification, no matter how small, of the pertinent code.
- You must demand a written agreement when you distribute the sources or patches.
- It requires notifying AT&T if you distribute a patch.
- Your license can be terminated through no fault of yours, under section 8/3.
- It makes compliance with export control laws a condition of the license.
- Some versions of the license require you to provide support.
- Some versions of the license say you cannot sell a copy of the software for more than the expense of distribution.
The license has two other obnoxious features:
- It has a very broad reverse license to AT&T, which goes far beyond the use of your code, even your code modified.
- It asserts one needs a license from AT&T to make a link to their web site. This is not an immediate practical problem, since the license says it gives permission to make such a link. (Anyway, people shouldn’t make links to sites about non-free software.) But such a claim should not be made or propagated.
- eCos Public License, version 1.1
- This was the old license of eCos. It is not a free software license, because it requires sending every published modified version to a specific initial developer. There are also some other words in this license whose meaning we’re not sure of that might also be problematic.Today eCos is available under the GNU GPL with additional permission for linking with non-free programs.
- GPL for Computer Programs of the Public Administration
- The GPL-PA (whose original name in Portuguese is «Licença Pública Geral para Administração Pública») is non-free for several reasons:
- It permits use only in “normal circumstances”.
- It does not allow distribution of source code without binaries.
- Its permissions lapse after 50 years.
- Hacktivismo Enhanced-Source Software License Agreement (HESSLA)
- This is not a free software license, because it restricts what jobs people can use the software for, and restricts in substantive ways what jobs modified versions of the program can do.
- Jahia Community Source License
- The Jahia Community Source License is not a free software license. Use of the source code is limited to research purposes.
- Old license of ksh93
- ksh93 used to be shipped with an original license that was not a free software license. One reason for this is that it required that all changes be sent to the developer.ksh93 is now released under the Common Public License.
- License of Lha
- The lha license must be considered non-free because it is so vague that you cannot be sure what permissions you have.
- Microsoft Limited Public License (Ms-LPL)
- This license is non-free because of section 3(F), which requires that any modified software you make from the original code must run on Windows. The Microsoft Public License does not have this restriction.
- Microsoft Limited Reciprocal License (Ms-LRL)
- This license is non-free because of section 3(G), which requires that any modified software you make from the original code must run on Windows. The Microsoft Reciprocal License does not have this restriction.
- Microsoft Reference License
- This is a non-free license: you are not allowed to modify the software at all, and you are only allowed to share it under very particular circumstances.
- Microsoft’s Shared Source CLI, C#, and Jscript License
- This license does not permit commercial distribution, and only allows commercial use under certain circumstances.Microsoft has other licenses which it describes as “Shared Source”, some of which have different restrictions.
- Microsoft Windows Embedded CE 6.0 Shared Source License
- This license is non-free because it places various limitations on the kinds of modifications you can make. For example, your modified software must run on Wince, and you are required to provide end user support for your software.
- NASA Open Source Agreement
- The NASA Open Source Agreement, version 1.3, is not a free software license because it includes a provision requiring changes to be your “original creation”. Free software development depends on combining code from third parties, and the NASA license doesn’t permit this.We urge you not to use this license. In addition, if you are a United States citizen, please write to NASA and call for the use of a truly free software license.
- Open Public License
- This is not a free software license, because it requires sending every published modified version to a specific initial developer. There are also some other words in this license whose meaning we’re not sure of that might also be problematic.
- License of PINE
- The license of PINE is not a free software license because it mostly prohibits the distribution of modified versions. It also restricts the media that can be used for selling copies.Please note that a successor to Pine, Alpine, is released under the Apache License, version 2.0.
- Old Plan 9 license
- This is not a free software license; it lacks essential freedoms such as the right to make and use private changes. Of course you should not use this license, and we urge you to avoid any software that has been released under it. A detailed discussion of this license is also available.In September 2002 it was observed that the published license for Plan 9 had been modified, adding more restrictions to it, although its date still said 09/20/00. However, a further license change in 2003 made Plan 9 free software.
- License of Qmail
- The license of Qmail is not a free software license because it mostly prohibits the distribution of modified versions.
- Reciprocal Public License
- The Reciprocal Public License is a non-free license because of three problems. 1. It puts limits on prices charged for an initial copy. 2. It requires notification of the original developer for publication of a modified version. 3. It requires publication of any modified version that an organization uses, even privately.
- Scilab license
- This is not a free software license because it does not allow commercial distribution of a modified version.
- SGI Free Software License B, version 1.1
- The SGI Free Software License B, although its name says «free», is not a free software License. It has three major problems. 1. It restricts its patent license to unmodified versions of the software. 2. It terminates if your use of the software infringes copyrights or patents which are not SGI’s. This is problematic because it gives SGI grounds to sue you even when you have done nothing to them. 3. The license requires you to inform SGI of legal problems with the software. This violates your privacy rights, and can conflict with professional confidentiality requirements, such as attorney-client privilege.
- Squeak license
- As applied to software, this is not a free software license because it requires all users in whatever country to obey US export control laws. As applied to fonts, it also does not permit modification.In addition, it has a requirement for users to indemnify the developer, which is enough to make many users think twice about using it at all.
- Sun Community Source License
- This is not a free software license; it lacks essential freedoms such as publication of modified versions. Please don’t use this license, and we urge you to avoid any software that has been released under it.
- Sun Solaris Source Code (Foundation Release) License, Version 1.1
- This is not a free software license. The license prohibits redistribution, prohibits commercial use of the software, and can be revoked.
- University of Utah Public License
- The University of Utah Public License is a non-free license because it does not allow commercial redistribution. It also purports to restrict commercially running the software and even commercially giving consultation about it. Those restrictions are probably not legally enforceable under US copyright law, but they might be in some countries; even asserting them is outrageous.The use of this license by the University of Utah exemplifies a dangerous trend for universities to restrict knowledge rather than contributing it to the public.
If a university tries to impose a license like this on the software you are writing, don’t give up hope. With persistence and firmness, and some forethought, it is possible to prevail over money-grabbing university administrators.
The earlier you raise the issue, the better.
- YaST License
- This is not a free software license. The license prohibits distribution for a fee, and that makes it impossible for the software to be included in the many CD-ROM free software collections that are sold by companies and by organizations such as the FSF.There may be another problem in section 2a, but a word seems to be missing there, so it is hard to be sure what meaning is really intended.
(The YaST software itself no longer uses this non-free YaST license; happily, it is now free software, released under the GNU GPL.)
Licenses For Documentation
Free Documentation Licenses
The following licenses qualify as free documentation licenses.
- GNU Free Documentation License
- This is a license intended for use on copylefted free documentation. We plan to adopt it for all GNU manuals. It is also suitable for other kinds of useful works (such as textbooks and dictionaries, for instance). Its applicability is not limited to textual works (“books”).
- Apple’s Common Documentation License, Version 1.0
- This is a Free Documentation license that is incompatible with the GNU FDL. It is incompatible because Section (2c) says “You add no other terms or conditions to those of this License”, and the GNU FDL has additional terms not accounted for in the Common Documentation License.
- FreeBSD Documentation License
- This is a permissive non-copyleft free documentation license that is compatible with the GNU FDL.
- Open Publication License, Version 1.0
- This license can be used as a free documentation license. It is a copyleft free documentation license provided the copyright holder does not exercise any of the “LICENSE OPTIONS” listed in Section VI of the license. But if either of the options is invoked, the license becomes non-free. In any case, it is incompatible with the GNU FDL.This creates a practical pitfall in using or recommending this license: if you recommend “Use the Open Publication License, Version 1.0 but don’t enable the options”, it would be easy for the second half of that recommendation to get forgotten; someone might use the license with the options, making a manual non-free, and yet think he or she is following your advice.
Likewise, if you use this license without either of the options to make your manual free, someone else might decide to imitate you, then change his or her mind about the options thinking that that is just a detail; the result would be that his or her manual is non-free.
Thus, while manuals published under this license do qualify as free documentation if neither license option was used, it is better to use the GNU Free Documentation License and avoid the risk of leading someone else astray.
Please note that this license is not the same as the Open Content License. These two licenses are frequently confused, as the Open Content License is often referred to as the “OPL”. For clarity, it is better not to use the abbreviation “OPL” for either license. It is worth spelling their names in full to make sure people understand what you say.
Non-Free Documentation Licenses
The following licenses do not qualify as free documentation licenses:
- Open Content License, Version 1.0
- This license does not qualify as free, because there are restrictions on charging money for copies. We recommend you do not use this license.Please note that this license is not the same as the Open Publication License. The practice of abbreviating “Open Content License” as “OPL” leads to confusion between them. For clarity, it is better not to use the abbreviation “OPL” for either license. It is worth spelling their names in full to make sure people understand what you say.
- Open Directory License (aka dmoz.org License)
- This is not a free documentation license. The primary problems are that your right to redistribute any given version is not permanent and that it requires the user to keep checking back at that site, which is too restrictive of the user’s freedom.
Licenses for Works Besides Software and Documentation
- GNU General Public License
- The GNU GPL can be used for general data which is not software, as long as one can determine what the definition of “source code” refers to in the particular case. As it turns out, the DSL (see below) also requires that you determine what the “source code” is, using approximately the same definition that the GPL uses.
- GNU Free Documentation License
- The GNU FDL is recommended for textbooks and teaching materials for all topics. (“Documentation” simply means textbooks and other teaching materials for using equipment or software.) We also recommend the GNU FDL for dictionaries, encyclopedias, and any other works that provide information for practical use.
- Creative Commons Attribution 2.0 license (a.k.a. CC-BY)
- This is a non-copyleft free license that is good for art and entertainment works, and educational works. Please don’t use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL.Creative Commons publishes many licenses which are very different. Therefore, to say that a work “uses a Creative Commons license” is to leave the principal questions about the work’s licensing unanswered. When you see such a statement in a work, please ask the author to highlight the substance of the license choices. And if someone proposes to “use a Creative Commons license” for a certain work, it is vital to ask immediately, “Which one?”
- Creative Commons Attribution-Sharealike 2.0 license (a.k.a. CC-BY-SA)
- This is a copyleft free license that is good for artistic and entertainment works, and educational works. Please don’t use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL.Please see additional comments about Creative Commons licenses just above.
- Design Science License (DSL)
- This is a free and copyleft license meant for general data. Please don’t use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL; however, it is fine to use for other kinds of data.
- Free Art License
- This is a free and copyleft license meant for artistic works. It permits commercial distribution, but any larger work including the copylefted work must be free. Please don’t use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL.
Licenses for Fonts
The licenses below apply to an instantation of a design in a computer file, not the artistic design. As far as we know, an implementation of a design is always copyrightable. The legal status of the artistic design is complex, and varies by jurisdiction.
- GNU General Public License
- The GNU GPL can be used for fonts. However, note that it does not permit embedding the font in a document unless that document is also licensed under the GPL. If you want to allow this, use the font exception. See also this explanatory essay about the GPL Font Exception.
- Arphic Public License
- This is a copyleft free software license, incompatible with the GPL. Its normal use is for fonts, and in that use, the incompatibility does not cause a problem.
- SIL Open Font License 1.1
- The Open Font License (including its original release, version 1.0) is a free copyleft license for fonts. Its only unusual requirement is that fonts be distributed with some computer program, rather than alone. Since a simple Hello World program will satisfy the requirement, it is harmless. Neither we nor SIL recommend the use of this license for anything other than fonts.
Espero hayan disfrutado de este post, y les quede aclarado un poco mas las dudas que pudieran surgir de acuerdo a las licensias GNU y no GNU.
Fuentes utilizadas en este post:
———————
Desde los profundos abismos de mi propia curiosidad adnhack
Entre geeks te veas 
17 Comments
mpwbnhj ,
generic hydrocodone, adipex online, ambien cr, ativan cheap, purchase ephedra, order xanax, alprazolam xanax,
Thanks a bunch for sharing this with all of us you really realize what you are talking about!
Bookmarked. Please additionally discuss with my site =).
We could have a hyperlink trade contract among us
I know this web page gives quality depending content and
other data, is there any other site which gives these things in quality?
Hi! I could have sworn I’ve been to this site before but after going through some of the articles I realized it’s new to me.
Anyways, I’m certainly happy I came across it and I’ll be book-marking it and checking back regularly!
Today, while I was at work, my cousin stole my iphone and tested to see if it can survive a forty foot
drop, just so she can be a youtube sensation. My iPad is now destroyed and she has 83 views.
I know this is entirely off topic but I
had to share it with someone!
I think that is among the most significant info for me.
And i’m glad studying your article. However want to observation on few normal things, The site taste is perfect, the articles is really great : D. Excellent job, cheers
I think what you published was actually very reasonable.
But, what about this? what if you were to create a killer post title?
I ain’t saying your content isn’t good., however what if you added something to maybe grab a person’s attention? I mean Tipos de Licensias Open Source Entre geeks te veas is kinda plain. You should glance at Yahoo’s front page and note how they write news headlines to
grab viewers interested. You might add a related video or a related pic or two to grab
readers excited about what you’ve written. Just my opinion, it might bring your posts a little bit more interesting.
I’m really loving the theme/design of your website. Do you ever run into any browser compatibility issues? A small number of my blog readers have complained about my blog not operating correctly in Explorer but looks great in Safari. Do you have any solutions to help fix this problem?
They make more cash that way, instead of selling everything at once or selling
each item individually. Looking on the internet
to buy plants online offers a selection that a garden nursery would find impossible to fit into their land space.
Since Nairobi is a very busy city, many of its residents who would like to own cars don’t have
the time to import cars or visit car dealerships in
Nairobi looking for cars.
Aw, this was a very good post. Taking the time and actual effort to produce
a really good article… but what can I say… I put things off a whole lot and don’t seem to get anything done.
It’s genuinely very complicated in this active life to listen news on Television, therefore I only use web for that purpose, and obtain the hottest news.
When someone writes an post he/she keeps the idea of a user in his/her mind that
how a user can understand it. Therefore that’s why this paragraph is outstdanding. Thanks!
Your own write-up offers confirmed necessary to me personally.
It’s quite educational and you are certainly quite well-informed in
this area. You have got opened my personal sight in order to
different opinion of this particular subject along with intriguing, notable and strong content material.
Pleasant write-up. I just now located ones site and planned to claim that I have got really experienced checking your blog page discussions. In the end My business is opt-in for ones rss with this particular intending you’re once more before long!
Hey, purely turned into alert to your web site into Yahoo and google, and located it’s really useful. I am about to look out for brussels. I’ll enjoy if you ever carry on this particular later on. Many other men and women could be taken advantage of ones producing. Best wishes!
An individual effectively assist in making seriously content I would declare. Which is the very first time We frequented your site webpage therefore much? We amazed while using the research you’ve made to build that submit wonderful.. medicare advantage in maryland Amazing pastime!
5 Trackbacks/Pingbacks
[…] el primer codigo de Mozilla se hizo disponible al publico bajo los terminos de la licencia “Open Source” y un cuerpo de gobierno para el proyect, La Mozilla Organization comenzo su trabajo publico. […]
[…] mismo Ingenieros chinos leyendo los tipos de licencias open […]
[…] https://entregeeks.wordpress.com/2008/03/03/tipos-de-licensias-open-source/ Share This Trackback Address Tags: Copyleft, GNU, licencias, licencias Open Source, Opne Source […]
[…] y developers han desarrollado un sistema Open Source (En tu cara Microsoft) para rastrear una lap top perdida de manera gratuita, este servicio se llama […]
[…] Despues de que RadioHead a inovado en la industria de la musica creando un nuevo concepto con su album pay what you like en donde tu pagabas lo que tu quisieras por bajar su album completo, ahora vuelve a la revancha con el video de su single “House of Cards“. El video ha sido creado usando avanzadas tecnicas de visualizacion y varios renders, creando una teammate con Google, RadioHead a liberado este video y su Codigo bajo la licensia Creative Commons license. […]