软件授权常见问题
一般问题
Joint Copyright Assignment (JCA)
一、 | Joint Copyright Assignment (JCA) 与旧的 Copyright Assignment 有何分别? |
二、 | 我是否必须填写 JCA? |
三、 | 若我已签了旧合约,但却较喜欢新合约,我该怎么做? |
四、 | 我如何以填写了的 JCA 完成申请程序? |
五、 | 我已用 JCA 申请成功了,但我现在不再想签署这些表格。我可否取消这些签署了的表格? |
六、 | 我已签署了 JCA,且已贡献了一些原始程序码,但我的原始程序码没被接纳。那现在谁是我的原始程序码的拥有者? |
七、 | 我已签署了版权合约,且已贡献了一些原始程序码。你们可否在版权布告中把我的姓名列出来? |
八、 | 我并非升阳员工,但我贡献了一些 OpenOffice.org 网站内容。为何网页底部的版权布告只列出升阳? |
九、 | JCA 中给予我道义上的权力,然而我的国家并不容许国民拥有这种权力。那该怎么办? |
十、 | 我有 GPL 软件,或其他我想贡献给 OpenOffice.org 的程序。然而,因为我不拥有这些软件的版权,所以我不能让这些程序在 JCA 或 PDL 授权声明下贡献出来。我该怎样做? |
Public Documentation License (PDL)
一、 | PDL 是什么? |
二、 | 我该怎样用 PDL? |
三、 | 若我想以 PDL 来授权某一份文件,我是否需要将一份 PDL 放在文件中? |
四、 | 我什么时侯才该用 PDL 而不用 JCA? |
使用规定
一、 | 为何 OpenOffice.org 网站会有使用规定声明? |
二、 | 使用规定声明的效力是否包括了所有我贡献了给 OpenOffice.org 的文件和原始程序码? |
一般问题:解答
一、 |
- OpenOffice.org 计划用哪些授权声明?
-
OpenOffice.org 原始程序码用的是双重授权声明策略。这两个授权声明就是 GNU 次通用公共授权 (LGPL) 及 Sun Industry Standards Source License (SISSL)。另外,OpenOffice.org 以 Public Documentation License (PDL) 作为为用户而设,且并非 OpenOffice.org 软件一部分的文件的授权声明。详情请看下面相关的部分。
回一般问题
|
二、 |
- 我该采用哪种授权声明呢?
-
这要看您想做什么。若您想将您的原始程序码包括在 OpenOffice.org 软件内,那您就必须用其中一个原始程序码授权声明。否则,如放在网站上的常见问题集等不包括在 OpenOffice.org 软件内的原始程序码,都可以用 PDL 为授权声明。若您想用原始程序码授权声明,您必须签署 Joint Copyright Assignment (JCA)。若您想用 PDL 的话,就只需将 PDL 放在您的文件内。详情请看下面 JCA 与 PDL 的部分。
回一般问题
|
三、 |
- 我可以在哪里找到更多关于授权声明的资料呢?
- 您可以到这网站中的授权声明一页中找到更多关于 GNU 次通用公共授权 (LGPL),Sun Industry Standards Source License (SISSL),与 Public Documentation License (PDL) 的资料。这网页中也有相关的资料可供参考。
回一般问题
|
四、 |
- OpenOffice.org 的原始程序码为何用双重授权法?
- 双重授权法给予开发者很大的自由度,让自由软件社区与其他不愿或不能使用 GNU 通用公共许可证 (GPL) 的开发者与公司都可以自由取用 OpenOffice.org 的原始程序码。双重授权法于自由软件社区中颇为普遍,其中较出名的有 Mozilla 及 Perl 等计划。
回一般问题
|
五、 |
- 若我贡献原始程序码给 OpenOffice.org 的话,我需要在原始程序码授权方面做什么呢?
- 您若将原始程序码贡献给 OpenOffice.org,LGPL 与 SISSL 会自动对您的原始程序码产生效力。为了统一版权,所有开发者都需要填写 Joint Copyright Assignment (JCA)。若您只是想贡献一些并不会包括在 OpenOffice.org 软件内的文件,则可以使用 Public Documentation Licence (PDL)。
回一般问题
|
六、 |
- 为何 OpenOffice.org 用 LGPL 授权声明?
- OpenOffice.org 原始程序码的授权声明是 GNU 通用公共授权 (GPL) 系列中的 GNU 次通用公共授权 (LGPL)。LGPL 基本上与 GPL 完全一样。它们唯一的不同之处就是 LGPL 准许您自由使用 OpenOffice.org 的原始程序码,且不需以 GNU 通用公共授权 (GPL) 来公开自己的原始程序码。详情请看升阳的白皮书
回一般问题
|
七、 |
- Sun Industry Standards Source License (SISSL) 是什么?
- Sun Industry Standards Source License (SISSL) 是 OpenOffice.org 原始程序码的授权声明,与 GNU 次通用公共授权 (LGPL) 一同生效。这授权声明让用户可以自由运用、修改、及延伸 OpenOffice.org 的原始程序码。不过开发者一定要保持 OpenOffice.org 语言中立的 API 及以 XML 为基础的文件格式。
回一般问题
|
The second license under which the sources will be made available is the SISSL. This license allows the user to do what they like with the source base, modify it, extend it, etc., but s/he must maintain compatibility. Attachment A of the SISSL defines the standards that must be met to comply with the license. For OpenOffice.org, the standards identified will be the LGPL versions of the OpenOffice.org technology language-independent APIs and XML-based file formats. If these standards are broken, the licensee must provide a reference implementation of sources which constitute the modification, thereby opening the details of any incompatibility/modification which has been introduced.
Back to main question page
Back to top
8. May I take portions of the OpenOffice.org code and use it to extend and improve another application?
Yes. You may freely modify, extend, and improve the OpenOffice.org source code. The only question is whether or not you must publish the source code and contribute modifications to the community. The GPL and the Sun Industry Standards Source License (SISSL) allow different ranges of flexibility in this regard but, in the end, regardless of the license used, any and all incompatible changes must be provided openly.
Back to main question page
Back to top
9. How did this licensing architecture come about?
Since the nature of OpenOffice.org technology is to provide re-usable and embedable office productivity components as well as the common applications services, the source code of the OpenOffice.org is dual licensed under a member of the GPL family of licenses, the Lesser GNU Public License (LGPL) and the Sun Industry Standards Source License (SISSL). Both of these are officially recognized free and open licenses. This licensing structure provides the necessary flexibility for combination of OpenOffice.org technologies with projects using other licenses (e.g. MPL, Apache, Artistic, etc.). It also provides the means through which commercial entities can participate with the OpenOffice.org community.
Back to main question page
Back to top
10. Are OpenOffice.org binaries legal for commercial use?
Yes, you may use OpenOffice.org binaries (the usable application) for commercial use. Please go to our download page to find the latest releases.
Back to main question page
Back to top
11. 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? For example, can I undertake and ship a current version StarOffice 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 assignment 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 of StarOffice, starting with StarOffice 6.0. StarOffice 5.2 code is not part of the OpenOffice.org project.
Back to main question page
Back to top
12. 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.
Back to main question page
Back to top
13. 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.
Back to main question page
Back to top
Contributing Works
The Joint Copyright Assignment: Answers
1. How is the Joint Copyright Assignment (JCA) different from the old Copyright Assignment form?
Under the Joint Copyright Assignment, both Sun and the contributor retain full rights to use, modify, and redistribute the copyrighted work. Under the Copyright Agreement form, the contributor’s rights were transferred to Sun and not shared with the contributor.
Back to main question page
Back to top
2. Do I have to fill out a JCA?
Yes, if you intend to contribute source code or other materials which are intended to be compiled or otherwise integrated with the OpenOffice.org product, regardless of the size of the contribution (e.g., including contributions of 10 lines or less). However we encourage all contributors to the OpenOffice.org website to fill out the JCA, as it makes accounting for contributions easier.
Back to main question page
Back to top
3. What do I do if I already signed the old form, but I like this one better and want to change?
Signing the JCA supersedes the Copyright Assignment form.
Back to main question page
Back to top
4. How do I file a completed JCA?
The process will be the same as for the old Copyright Assignment form. Please consult our Contributing page. We must have FAX or hard copy on file before we will assign an SSH key and update the list of accepted Copyright Assignments.
Back to main question page
Back to top
5.
I already have a form on file, but I’ve changed my mind and now I don’t want to sign either form. Can I cancel?
There is no process to cancel an assignment once made for previously contributed technology. This is to protect the code base so everyone who uses it can depend on its continued functionality. However, you are never obligated to make further contributions.
Back to main question page
Back to top
6. I tried to make a contribution to OpenOffice.org and signed a Copyright Assignment form, but my contribution wasn’t accepted. Who “owns” my code now?
For all unaccepted contributions, ownership simply reverts to the contributor.
Back to main question page
Back to top
7. I have a copyright assignment on file and I’ve made a code contribution to OpenOffice.org. Can I get listed on the copyright notice?
It is impractical to include all contributors’ names in the copyright notice and its not legally necessary. Instead, we credit all contributors to the OpenOffice.org product on the Credits page. If you are not listed and should be you can of course request that your Project Lead add your name.
Back to main question page
Back to top
8. I’m not a Sun employee but I’ve contributed content to the OpenOffice.org website. Why does the website copyright notice at the bottom of each web page only list Sun?
It is impractical to include all contributors’ names in the copyright notice and its not legally necessary. Instead, each project is responsible for honoring all contributors to that project's website; a list of contributors to the general OpenOffice.org website is maintained by the Website project. If you are not listed and should be you can of course request that your Project Lead add your name.
Back to main question page
Back to top
9. The JCA appears to address a grant of moral rights, but my country does not allow the grant of moral rights in any way.
Yes, the JCA accommodates for local differences in the treatment of moral rights. Depending on local law, the part of the JCA related to moral rights may be not applicable in some European countries.
Back to main question page
Back to top
10. I have GPL software, or other contributions which I would like to contribute to OpenOffice.org, but I cannot put them under the JCA or the PDL as I do not control the copyright of these items. What should I do?
If you are certain that you have been granted the right to post the contribution (either because you wrote it or because it is licensed in a way that allows you to redistribute), there are a number of community websites that focus on OpenOffice.org related materials which may be willing to post such materials. Among them are:
OOoDocs;
OO Extras; and
Evolved OpenOffice
Back to main question page
Back to top
The Public Documentation License: Answers
1. What is the Public Documentation License (PDL)?
The PDL (Public Documentation License) PDF | HTML | RTF (text) is a new license authored by Sun to address the need for a license that allows Open Source communities to collaborate on documentation which isn’t intended for inclusion or integration in the project code base or in packaged distributions (e.g., “product”).
Back to main question page
Back to top
2. How do I use the PDL?
The PDL is designed to be attached as a copy to a specific document, completing the information identifying the document and original author. The last page of the PDL is a log of changes to the document. All donors of edits must append a description of their contribution(s) to this page. For this reason the PDL is posted in an editable form (HTML | RTF [text]), however modifications other than to complete information to specify the document under license and to list contributors is prohibited as it is a standard legal contract.
Back to main question page
Back to top
3. Do I have to attach a physical copy of the PDL to a document I wish covered by it?
No. You may attach a link to the PDL in that document. But because every contributor to the document must log their changes on the license, it is actually more practical to just append it to the document as an editable file.
Back to main question page
Back to top
4. When would I use the PDL instead of the JCA?
The PDL was designed for Open Source documentation which isn’t intended for inclusion in the OpenOffice.org product. Before a document donated under the PDL can be included in the OpenOffice.org product, it must be converted to a JCA contribution. For this reason it is generally preferable to make all contributions to OpenOffice.org under the JCA.
Back to main question page
Back to top
The Terms of Use: Answers
1. Why does the OpenOffice.org website have a Terms of Use license?
It is common practice to host a Terms of Use statement for corporate sponsored websites to catch any content that isn’t already covered by either a copyright assignment or a license so that the sponsor can legally police the site if undesirable content appears (if for instance someone posts content that is defamatory or content which the donor has no right to donate).
Back to main question page
Back to top
2. Are all my contributions covered by the Terms of Use?
The Terms of Use is superceded by all the licenses under which a donor can contribute (on OpenOffice.org this includes the JCA and PDL). The Terms of Use is intended as a catch all for contributions which are not specifically covered by the JCA or PDL, such as comments on a mail list or in a bug report.
Back to main question page
Back to top
|