FAQs
 |
|
Overview  Source & 科学（工学）技術 問題／発行する Tracker Licensing Community Mirrors Asian FAQs Other |
| These faq have been 収集するd over the （期間が）わたる of OpenOffice's lifetime. Most of the （警察などへの）密告，告訴（状） is now out of date. See the OpenOffice FAQ page on our 公式の／役人 wiki for up-to-date （警察などへの）密告，告訴（状）. If you find instances that need updating, let us know by sending a 公式文書，認める to dev@openoffice.apache.org. |
Licensing 
General Questions
- Which licenses does the OpenOffice.org 事業／計画（する） use?
- Why is OpenOffice.org 可決する・採択するing the LGPL v. 3 license?
- Which license should I use?
- Where can I get more （警察などへの）密告，告訴（状） on the OpenOffice.org licenses?
- OpenOffice.org used to be 二重の licensed. What happened?
- If I 与える／捧げる code to OpenOffice.org what am I going to be asked to do as far as licenses are 関心d?
- Why is the LGPL license 存在 used?
- May I take 部分s of the OpenOffice.org code and use it to 延長する and 改善する another 使用／適用?
- Are OpenOffice.org binaries 合法的な for 商業の use?
- Does the OpenOffice.org open source give me the 権利 to 修正する and 分配する any 見解／翻訳／版 of StarOffice?
- Can Sun ever take away the code?
- What is the 必須の difference between the GPL and the LGPL?
与える／捧げるing 作品
The Oracle Contributor 協定
- Why does Oracle 要求する copyright assignment for OpenOffice.org?
- How does the Oracle Contributor 協定 異なる from 事前の ones?
- Do I have to fill out a OCA?
- I 調印するd the JCA or SCA; do I need now to 服従させる／提出する the OCA?
- What do I do if I already 調印するd the old form, but I like this one better and want to change?
- How do I とじ込み／提出する a 完全にするd OCA?
- I already have a form on とじ込み／提出する, but I’ve changed my mind. Can I 取り消す?
- I tried to make a 出資／貢献 to OpenOffice.org and 割り当てるd copyright, but my 出資／貢献 wasn’t 受託するd. Who “owns” my code now?
- I have a copyright assignment or OCA on とじ込み／提出する and I’ve made a code 出資／貢献 to OpenOffice.org. Can I get 名簿（に載せる）／表（にあげる）d on the copyright notice?
- I’m not a Oracle 従業員 but I’ve 与える／捧げるd content to the OpenOffice.org website. Why does the website copyright notice at the 底（に届く） of each web page only 名簿（に載せる）／表（にあげる） Oracle?
- The OCA appears to 演説（する）／住所 a 認める of moral 権利s, but my country does not 許す the 認める of moral 権利s in any way.
- I have GPL ソフトウェア, or other 出資／貢献s which I would like to 与える／捧げる to OpenOffice.org, but I cannot put them under the OCA or the PDL as I do not 支配（する）／統制する the copyright of these items. What should I do?
- How are 拡張s 影響する／感情d by the new 協定 and license?
- What is the 衝撃 of the contributor 協定 to contributors?
The Public Documentation License (PDL)
- What is the PDL?
- How do I use the PDL?
- Do I have to attach a physical copy of the PDL to a 文書 I wish covered by it?
- When would I use the PDL instead of the OCA?
The 条件 of Use
- Why does the OpenOffice.org website have a 条件 of Use license?
- Are all my 出資／貢献s covered by the 条件 of Use?
Licensing
General Questions: Answers
- Which licenses does the OpenOffice.org 事業／計画（する） use?
効果的な OpenOffice.org 3.0 Beta, OpenOffice.org will use the GNU Lesser General Public License v.3 (LGPL). 事前の 見解／翻訳／版s use v. 2.1. For the 1.x codeline, OpenOffice.org used 同様に the Sun 産業 基準 Source License (SISSL). OpenOffice.org also uses the Public Documentation License (PDL) for modifiable documentation that will not be 含むd in any final 製品 but will be of service to 使用者s, and the Creative ありふれたs NoDerivs 2.5 license for 非，不，無-modfiable 文書s, such as PDFs. Please see the section below on the PDL for more （警察などへの）密告，告訴（状）.
- Why is OpenOffice.org 可決する・採択するing the LGPL v.3?
The switch to LGPL v3 was discussed by the OpenOffice.org 事業／計画（する） leads and was identified as a good step by the 大多数 of the 事業／計画（する） leads. By switching to the LGPL v3, OpenOffice.org and Sun show a strong かかわり合い to the LGPL and GPL 見解／翻訳／版 and open source in general. 見解／翻訳／版 3 has the advantage of 存在 clearer in different 面s and 申し込む／申し出ing better 特許 保護.
- Which license should I use?
That depends on what you want to do. If you wish for your code submissions to be 含むd in the 製品, you must 調印する the Oracle Contributor 協定 (OCA) (see below); the license in 影響 is the LGPL for code. If you wish for your work to be used outside of any 製品 (say, as website FAQ), then you may use the PDL. The usage of the source license 異なるs from that of the PDL. To 適用する a source license, you must fill out and 調印する a Oracle Contributor 協定 (OCA). You only need to do this once. To 適用する the PDL, on the other 手渡す, you must attach a copy of the license to each modifiable 文書 covered by that license. Please see the section below on the use of the PDL.
- Where can I get more （警察などへの）密告，告訴（状） on the OpenOffice.org licenses?
Visit our license page for 付加 （警察などへの）密告，告訴（状） on the LGPL and PDL. We also have a section below that discusses the PDL in 詳細（に述べる）. For more （警察などへの）密告，告訴（状） on the LGPL and GPL, 含むing （警察などへの）密告，告訴（状） about the v3 that OpenOffice.org will use 効果的な the Beta of OpenOffice.org 3.0, please also visit the 解放する／自由な ソフトウェア 創立／基礎's FAQs on the license: http://www.gnu.org/licenses/gpl-faq.html.
- OpenOffice.org used to be 二重の licensed. What happened?
OpenOffice.org was 開始する，打ち上げるd under the LGPL v. 2.1 and Sun 産業 基準 Source License (SISSL), an Open Source 率先 (OSI)-認可するd license. Over the summer of 2005, the OSI decided to 限界 license 増殖 and 簡単にする the 選択 of licenses. In 協定 with this 客観的な, Sun retired the SISSL and encouraged the 事業／計画（する）s using it to do the same. OpenOffice.org will retire the SISSL. OpenOffice.org 2.x source code from this point 今後 (from the 解放（する） after 2.0 Beta 2) will be licensed only under the LGPL. (Source for the 1.x codeline will remain 二重の-licensed.) This change is not retroactive and code licensed 事前の to the 告示 is still licensed under the LGPL and SISSL. 使用者s are not 影響する／感情d. For more （警察などへの）密告，告訴（状） on the simplification, see our FAQ on the 事柄. 効果的な OpenOffice.org 3.0 Beta, OpenOffice.org will use the LGPL v3.
- If I 与える／捧げる code to OpenOffice.org, what am I going to be asked to do as far as licenses are 関心d?
All 出資／貢献s to the source code will 要求する that the code is automatically 利用できる under the LGPL. Oracle asks that developers fill out the Oracle Contributor 協定 (OCA) so that the copyright is 統一するd. The OCA 確実にするs that Oracle can defend license 違反s if necessary.
If you are 利益／興味d in only committing modifiable documentation which isn't ーするつもりであるd for 傾向 or 統合，差別撤廃 in the OpenOffice.org 製品, the Public Documentation License may be 関連した. Please see the section below on the license.
- Why is the LGPL license 存在 used?
As a member of the GPL license family, the GNU LGPL or "Lesser General Public License" will be used for the OpenOffice.org source code. The LGPL has all of the 制限s of the GPL except that you may use the code at 収集する time without the derivative work becoming a GPL work. This 許すs the use of the code in proprietary 作品. The LGPL license is 完全に 両立できる with the GPL license.
- May I take 部分s of the OpenOffice.org code and use it to 延長する and 改善する another 使用／適用?
Yes. You may 自由に 修正する, 延長する, and 改善する the OpenOffice.org source code. Modifications to the source must be published.
- Are OpenOffice.org binaries 合法的な for 商業の use?
Yes, you may use OpenOffice.org binaries (the usable 使用／適用) for 商業の use. You may 自由に 分配する it to any 使用者. Please go to our download page to find the 最新の 解放（する）s.
- Does the OpenOffice.org open source license give me the 権利 to 修正する and 分配する any 見解／翻訳／版 of StarOffice?
No. The OpenOffice.org source license does not 許す anyone to 修正する, repackage, or redistribute any 見解／翻訳／版 of StarOffice, or any other 商業の 見解／翻訳／版 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 事業／計画（する） is the 開発 事業／計画（する） for 未来 解放（する）s of StarOffice, starting with StarOffice 6.0. StarOffice 5.2 code is not part of the OpenOffice.org 事業／計画（する）.
- Can Sun ever take away the code?
The simple answer to this is NO. Once code is 解放（する）d under the LGPL, it can never be taken away. Sun has no 計画（する）s to return to a の近くにd 開発 model. Sun continues to 与える／捧げる modifications under the LGPL. Thus, Sun can never take away the code and the community's 出資／貢献s to it. This code belongs to the community as 保証（人）d by the LGPL.
- What is the 必須の difference between the GPL and the LGPL?
When code licensed under the GPL is 連合させるd or linked with any other code, that code must also then be licensed under the GPL. In 影響, this license 需要・要求するs that any code 連合させるd with GPL'd code 落ちるs under the GPL itself.
Code licensed under the LGPL can be dynamically or statically linked to any other code, 関わりなく its license, as long as 使用者s are 許すd to run debuggers on the 連合させるd program. In 影響, this license 認めるs 肉親，親類d of a 境界 between the LGPL'd code and the code that is linked to it.
与える／捧げるing 作品
The Oracle Contributor 協定: Answers
- Why does Oracle 要求する copyright assignment for OpenOffice.org?
Many open source 事業／計画（する）s 要求する a copyright assignment so that the code base can be 合法的に 保護するd as a whole by one （独立の）存在 without having to worry about the copyrights for different pieces. Other 目だつ examples of 事業／計画（する）s 要求するing copyright assignment are the Mono 事業／計画（する） and the 進化 事業／計画（する）, which both 要求する 割り当てるing the copyright to Novell. The Red Hat Directory Server 事業／計画（する） 要求するs 割り当てるing the copyright to Red Hat. The Oracle Contributor 協定 is very 自由主義の, as it 要求するs 株ing the copyright instead of fully transferring it and also 保証（人）s that published 出資／貢献s will remain under an open source license forever.
- How does the Oracle Contributor 協定 異なる from 事前の ones?
The Oracle Contributor 協定 is 同一の to the Sun Contributor 協定. The Sun Microsystems Inc. Contributor 協定 for OpenOffice.org introduced an addendum that 除外するs 非，不，無-核心 出資／貢献s, like 拡張s and documentation, from the 共同の copyright assignment, 供給するd that these 構成要素s are not ーするつもりであるd to be 含むd in the OpenOffice.org 製品 that can be downloaded from OpenOffice.org. The new 協定 also 保護するs against 特許 misuse and 乱用 and thus 作品 with the LGPL v3 to 確実にする a more stable open source community.
The OCA/SCA その上の 供給するs for stronger 特許 保護 and 含むs an exception for 拡張s and documentation not 現在の in 事前の 協定s.
- Do I have to fill out a OCA?
Yes, if you ーするつもりである to 与える／捧げる source code or other 構成要素s which are ーするつもりであるd to be 収集するd or さもなければ 統合するd with the OpenOffice.org 製品, 関わりなく the size of the 出資／貢献 (e.g., 含むing 出資／貢献s of 10 lines or いっそう少なく). However we encourage all contributors to the OpenOffice.org website domain, 含むing the wiki, to fill out the OCA, as it 簡素化するs the 過程 for all.
- I 調印するd the JCA or SCA; do I need now to 服従させる／提出する the OCA?
No: You do not have 調印する and 服従させる／提出する the OCA if you have already submitted the SCA, JCA or earlier Copyright Assignment (CA).
- What do I do if I already 調印するd the old form, but I like this one better and want to change?
調印 the OCA supersedes the JCA and 早期に Copyright Assignment form (CA).
- How do I とじ込み／提出する a 完全にするd OCA?
The 過程 will be the same as for the old SCA, JCA. Please 協議する our 与える／捧げるing page. We must have received the 調印するd and scanned form before we will 割り当てる an SSH 重要な and update the 名簿（に載せる）／表（にあげる） of 受託するd Copyright Assignments.
-
I already have a form on とじ込み／提出する, but I’ve changed my mind. Can I 取り消す?
There is no 過程 to 取り消す an assignment once made for 以前 与える／捧げるd 科学（工学）技術. This is to 保護する the code base so everyone who uses it can depend on its continued functionality. However, you are never obligated to make その上の 出資／貢献s.
- I tried to make a 出資／貢献 to OpenOffice.org and 割り当てるd copyright with the old Copyright Assignment form, but my 出資／貢献 wasn’t 受託するd. Who “owns” my code now?
For all unaccepted 出資／貢献s, 所有権 簡単に 逆戻りするs to the contributor. For more 最近の 出資／貢献s where the JCA or the 現在の OCA have been submitted, you, as the author, 持つ／拘留する copyright 共同で with Oracle over the 出資／貢献.
- I have a copyright assignment or OCA on とじ込み／提出する and I’ve made a code 出資／貢献 to OpenOffice.org. Can I get 名簿（に載せる）／表（にあげる）d on the copyright notice?
It is impractical to 含む all contributors’ 指名するs in the copyright notice and its not 合法的に necessary. Instead, we credit all contributors to the OpenOffice.org 製品 on the Credits page. If you are not 名簿（に載せる）／表（にあげる）d and should be you can of course request that your 事業／計画（する） Lead 追加する your 指名する.
- I’m not a Oracle 従業員 but I’ve 与える／捧げるd content to the OpenOffice.org website. Why does the website copyright notice at the 底（に届く） of each web page only 名簿（に載せる）／表（にあげる） Oracle?
It is impractical to 含む all contributors’ 指名するs in the copyright notice and its not 合法的に necessary. Instead, each 事業／計画（する） is 責任がある 栄誉（を受ける）ing all contributors to that 事業／計画（する）'s website; a 名簿（に載せる）／表（にあげる） of contributors to the general OpenOffice.org website is 持続するd by the Website 事業／計画（する）. If you are not 名簿（に載せる）／表（にあげる）d and should be you can request that your 事業／計画（する） Lead 追加する your 指名する.
- The OCA appears to 演説（する）／住所 a 認める of moral 権利s, but my country does not 許す the 認める of moral 権利s in any way.
Yes, the OCA 融通するs for 地元の differences in the 治療 of moral 権利s. Depending on 地元の 法律, the part of the OCA 関係のある to moral 権利s may not be applicable in some European countries.
- I have GPL ソフトウェア, or other 出資／貢献s which I would like to 与える／捧げる to OpenOffice.org, but I cannot put them under the OCA or the PDL as I do not 支配（する）／統制する the copyright of these items. What should I do?
If you are 確かな that you have been 認めるd the 権利 to 地位，任命する the 出資／貢献 (either because you wrote it or because it is licensed in a way that 許すs you to redistribute), there are a number of community websites that 焦点（を合わせる） on OpenOffice.org 関係のある 構成要素s which may be willing to 地位，任命する such 構成要素s. We used to 名簿（に載せる）／表（にあげる） them and are 利益／興味d in continuing to do so, but the number has 増加するd 速く. A Google search is probably more efficient.
- How are 拡張s 影響する／感情d by the new 協定 and license?
The OCA's 控除 for 非，不，無-核心 出資／貢献s, inclding 拡張s, means that contributors can create and 地位，任命する 拡張s to the 事業／計画（する） 場所／位置 as they do now without having to 割り当てる copyright unless those 拡張s are to be 含むd in the 製品.
The LGPL v3 operates as earlier 見解／翻訳／版s and unless the 拡張 関係 into the 製品's libraries, it is not 影響する／感情d by the actual license; aggregation, bundling, and other such 一括ing do not 影響する／感情 an 拡張's own license.
- What is the 衝撃 of the OCA on contributors?
The OCA 減ずるs the 障壁s to 入ること／参加（者）. With the OCA, new developers can first make 出資／貢献s in the form of 拡張s and documentation without having to decide if they want to 株 the copyright for the code or not.
The Public Documentation License: Answers
- What is the Public Documentation License (PDL)?
The PDL (Public Documentation License) PDF | HTML | RTF (text) is a new license authored by Sun to 演説（する）／住所 the need for a license that 許すs Open Source communities to 共同製作する on documentation which isn’t ーするつもりであるd for 傾向 or 統合，差別撤廃 in the 事業／計画（する） code base or in 一括d 配当s (e.g., “製品”).
- How do I use the PDL?
The PDL is designed to be 大（公）使館員d as a copy to a 明確な／細部 文書, 完全にするing the （警察などへの）密告，告訴（状） identifying the 文書 and 初めの author. The last page of the PDL is a スピードを出す／記録につける of changes to the 文書. All 寄贈者s of edits must append a description of their 出資／貢献(s) to this page. For this 推論する／理由 the PDL is 地位，任命するd in an editable form (HTML | RTF [text]), however modifications other than to 完全にする （警察などへの）密告，告訴（状） to 明示する the 文書 under license and to 名簿（に載せる）／表（にあげる） contributors is 禁じるd as it is a 基準 合法的な 契約.
- Do I have to attach a physical copy of the PDL to a 文書 I wish covered by it?
No. You may attach a link to the PDL in that 文書. But because every contributor to the 文書 must スピードを出す／記録につける their changes on the license, it is 現実に more practical to just append it to the 文書 as an editable とじ込み／提出する.
- When would I use the PDL instead of the OCA?
The PDL was designed for Open Source documentation which isn’t ーするつもりであるd for 傾向 in the OpenOffice.org 製品. Before a 文書 寄付するd under the PDL can be 含むd in the OpenOffice.org 製品, it must be 変えるd to a OCA 出資／貢献. For this 推論する／理由 it is 一般に より望ましい to make all 出資／貢献s to OpenOffice.org under the OCA.
The 条件 of Use: Answers
- Why does the OpenOffice.org website have a 条件 of Use license?
It is ありふれた practice to host a 条件 of Use 声明 for 法人組織の／企業の sponsored websites to catch any content that isn’t already covered by either a copyright assignment or a license so that the sponsor can 合法的に police the 場所／位置 if 望ましくない content appears (if for instance someone 地位，任命するs content that is defamatory or content which the 寄贈者 has no 権利 to 寄付する).
- Are all my 出資／貢献s covered by the 条件 of Use?
The 条件 of Use is superseded by all the licenses under which a 寄贈者 can 与える／捧げる (on OpenOffice.org this 含むs the OCA and PDL). The 条件 of Use is ーするつもりであるd as a catch all for 出資／貢献s which are not 特に covered by the OCA or PDL, such as comments on a mail 名簿（に載せる）／表（にあげる） or in a bug 報告（する）／憶測.
