Juan Manuel Acosta wrote:
A ver ayer me dieron un susto "del carajo", claro que era un dueño de
una tienda de informática.
Este caballero me dijo que leyera bien la licencia de OpenOffice por
que no es LEGAl su uso por empresas sino solo para PARTICULARES.
¿¿Es cierto esto??
Me parece que desayunó con grapa. Extraído de
http://www.openoffice.org/license.html
Licenses
Last updated: 2004-10
OpenOffice.org uses a dual license strategy for the source code and a
separate documentation license for most documents published on the
website without the intention of being included in the product. The
source-code licenses are the GNU General Public License and the Sun
Industry Standards Source License. The document license is the Public
Document License.
When the GPL license is used, the libraries and component functionality
of the OpenOffice.org source code will be licensed under the GNU Lesser
General Public License (LGPL), which is completely compatible with the
GPL license. We encourage users to use the GPL/LGPL licenses and
participate fully in the OpenOffice.org community.
Copies of the licenses are available. The PDL is in a static and
editable form, so that it can be used as designed:
* Public Document License (PDL) PDF
<http://www.openoffice.org/licenses/pdl.pdf> | HTML
<http://www.openoffice.org/licenses/PDL.html> | RTF (text)
<http://www.openoffice.org/licenses/PDL.rtf>
* GNU General Public License
<http://www.openoffice.org/licenses/gpl_license.html> (GPL)
* GNU Lesser General Public License
<http://www.openoffice.org/licenses/lgpl_license.html> (LGPL)
* Sun Industry Standards Source License
<http://www.openoffice.org/licenses/sissl_license.html> (SISSL)
Dual licensing of the OpenOffice.org source code provides open and free
access to the technology both for the GPL community and for other
developers or companies that cannot use the GPL. Dual license is common
practice in open source projects like Perl and Mozilla. Through the
combined use of GPL/LGPL and SISSL, developers will have a high degree
of freedom yet compatibility and interoperability will be preserved.
You can freely modify, extend, and improve the OpenOffice.org source
code. The only question is whether or not you must provide the source
code and contribute modifications to the community. The GPL and SISSL
licenses allow different ranges of flexibility in this regard, but in
the end, regardless of the license used, any and all incompatible
changes must be published openly.
In order to contribute code to the project, you must submit the Joint
Copyright Assignment form. This form jointly assigns copyright over your
work to yourself and to Sun Microsystems. Details are available on the
"Contributing
<http://www.openoffice.org/contributing/programming.html#jca>" page. If
you have questions on its operation, the FAQ: Licensing
<http://www.openoffice.org/FAQs/faq-questions.html#licensing> section
should answer them. The page also has guidelines on the use of the
licenses. If these don't help, send a note to the Community Manage
<mailto:[EMAIL PROTECTED]>r.
For more information on the GPL and LGPL, please also visit the Free
Software Foundation's FAQs: http://www.gnu.org/copyleft/gpl-faq.htm
<http://www.gnu.org/copyleft/gpl-faq.html>.
Están los enlaces a todas las licencias.
--
Héctor Andrés Rompato Carricart <[EMAIL PROTECTED]>
COVIARES S.A.
Departamento de equipos de peaje
Av. Iriarte y Autopista, Quilmes (1878)
Buenos Aires, Argentina
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
