軟件授權常見問題
一般問題
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 |
