4.If I contribute code to OpenOffice.org what am I going to be asked to do as far as
licenses are concerned?
All contributions to the source code will require that the code is automatically available
under both the LGPL and the Sun Industry Standards Source License (SISSL). Sun asks that
developers assign the copyright to Sun so that the copyright is unified; see the copyright
assignment page for full details. The assignation of copyright also ensures that Sun can
defend license violations if necessary. Sun is absolutely committed to the dual license
mechanism of LGPL + SISSL and will remain so committed.
Does the OpenOffice.org open source license give me the right to modify and
distribute any version of StarOffice, for example, the currently shipping StarOffice
5.2? For example, can I undertake and ship a StarOffice 5.2 for Catalan?
No. The OpenOffice.org source license does not allow anyone to modify, repackage, or
redistribute any version of StarOffice, or any other commercial version of the OpenOffice.org
source code without an agreement from the vendor. For StarOffice the vendor is Sun
Microsystems. Additionally, the source code in the OpenOffice.org project is the development
project for future releases, starting with StarOffice 6.0. StarOffice 5.2 code is not part of the
OpenOffice.org project.
11.Can Sun ever take away the code?
The simple answer to this is NO. Once code is released under the LGPL, it can never be taken
away. Once LGPL, always LGPL. Sun has no plans to return to a closed development model.
Sun is subject to the same rules as the rest of the community, including giving back
modifications under the LGPL (or a specification and reference implementation under the
terms of the SISSL). Thus, Sun can never take away the code and the community's
contributions to it. This code belongs to the community as guaranteed by the LGPL and the
SISSL.
12.What is the essential difference between the GPL and the LGPL?
When code licensed under the GPL is combined or linked with any other code, that code must
also then be licensed under the GPL. In effect, this license demands that any code combined
with GPL'd code falls under the GPL itself.
Code licensed under the LGPL can be dynamically or statically linked to any other code,
regardless of its license, as long as users are allowed to run debuggers on the combined
program. In effect, this license recognizes kind of a boundary between the LGPL'd code and
the code that is linked to it.
La license GPL est compatible avec la LGPL(on est heureux de le savoir),
les modifications du code de openoffice doivent etre sous license SISSL, et doivent etre sous la license LGPL (si on utilise des librairies libres)
pour que Sun puisse apposé un copyright (qui défend ces licenses).
C'est clairement fait pour décourager ceux qui voudrait distribuer des versions de openoffice sous GPL...
Et carrement fait pour encourager les mecs à modifier le code source sous license LGPL et (non pas ou) et SISSL
pour poouvoir redistribuer le code en passant par Sun.
Et si tu comprends pas, je lache l'affaire. En tout cas Open Office est loin d'être libre.
[^] # Re: petite rectification...
Posté par Code34 . En réponse à la dépêche Fin de Star Office 5.2. Évalué à -5.
4.If I contribute code to OpenOffice.org what am I going to be asked to do as far as
licenses are concerned?
All contributions to the source code will require that the code is automatically available
under both the LGPL and the Sun Industry Standards Source License (SISSL). Sun asks that
developers assign the copyright to Sun so that the copyright is unified; see the copyright
assignment page for full details. The assignation of copyright also ensures that Sun can
defend license violations if necessary. Sun is absolutely committed to the dual license
mechanism of LGPL + SISSL and will remain so committed.
Does the OpenOffice.org open source license give me the right to modify and
distribute any version of StarOffice, for example, the currently shipping StarOffice
5.2? For example, can I undertake and ship a StarOffice 5.2 for Catalan?
No. The OpenOffice.org source license does not allow anyone to modify, repackage, or
redistribute any version of StarOffice, or any other commercial version of the OpenOffice.org
source code without an agreement from the vendor. For StarOffice the vendor is Sun
Microsystems. Additionally, the source code in the OpenOffice.org project is the development
project for future releases, starting with StarOffice 6.0. StarOffice 5.2 code is not part of the
OpenOffice.org project.
11.Can Sun ever take away the code?
The simple answer to this is NO. Once code is released under the LGPL, it can never be taken
away. Once LGPL, always LGPL. Sun has no plans to return to a closed development model.
Sun is subject to the same rules as the rest of the community, including giving back
modifications under the LGPL (or a specification and reference implementation under the
terms of the SISSL). Thus, Sun can never take away the code and the community's
contributions to it. This code belongs to the community as guaranteed by the LGPL and the
SISSL.
12.What is the essential difference between the GPL and the LGPL?
When code licensed under the GPL is combined or linked with any other code, that code must
also then be licensed under the GPL. In effect, this license demands that any code combined
with GPL'd code falls under the GPL itself.
Code licensed under the LGPL can be dynamically or statically linked to any other code,
regardless of its license, as long as users are allowed to run debuggers on the combined
program. In effect, this license recognizes kind of a boundary between the LGPL'd code and
the code that is linked to it.
La license GPL est compatible avec la LGPL(on est heureux de le savoir),
les modifications du code de openoffice doivent etre sous license SISSL, et doivent etre sous la license LGPL (si on utilise des librairies libres)
pour que Sun puisse apposé un copyright (qui défend ces licenses).
C'est clairement fait pour décourager ceux qui voudrait distribuer des versions de openoffice sous GPL...
Et carrement fait pour encourager les mecs à modifier le code source sous license LGPL et (non pas ou) et SISSL
pour poouvoir redistribuer le code en passant par Sun.
Et si tu comprends pas, je lache l'affaire. En tout cas Open Office est loin d'être libre.
@+
Code34