License/zh-cn: Difference between revisions

From FreeCAD Documentation
(Created page with "=== 开源开发者 == 可以使用 FreeCAD 作为自己的扩展模块的基础, 为特殊目的。他们可以选择 GPL 或 LGPL, 允许他们在专有软件中使用他们...")
(Updating to match new version of source page)
 
(46 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<languages/>
== 主要开发人员的声明 ==
我知道关于''"正确"''的开源许可证的讨论占据了互联网带宽的很大一部分, 所以这里的原因是, 我认为, FreeCAD 应该有这一个。

我选择 [http://en.wikipedia.org/wiki/LGPL LGPL] 作为这个项目的许可证并且我知道关于 LGPL 的利与弊和将会给你一些关于该决定的原因。


{{Docnav
FreeCAD 是一个库和一个应用程序的混合物, 所以 GPL 显得有点过于强大。它将阻止为 FreeCAD 编写商业模块, 因为它会阻止与 FreeCAD 基础库的链接。你可能会问为什么是所有的商业模块?因此, Linux 是一个很好的例子。如果 GNU C 库是 GPL, 从而防止与非 GPL 应用程序的链接, Linux 会如此成功吗?虽然我喜欢 Linux 的自由, 我也希望能够使用非常好的 NVIDIA 3D 图形驱动程序。我理解并接受 NVIDIA 不希望放弃驱动程序代码的原因。我们都为公司工作, 需要至少为食物付款。所以对我来说, 开放源码和封闭式源码软件的共存并不是一件坏事, 当它遵循 LGPL 的规则时。我想看到有人写一个 FreeCAD 的导入/导出处理器, 并免费分发或需要支持一些钱。我不喜欢强迫他放弃他想要的。这对他和 FreeCAD 都不好。
|[[Dialog_creation|Dialog creation]]
|[[Compile_on_Windows|Compiling on Windows]]
}}


{{TOCright}}
然而这个决定仅为 FreeCAD 的核心系统做出。每个应用模块的作者都可以自己做出决定。


<span id="Licenses_used_in_FreeCAD"></span>
<div class="mw-translate-fuzzy">
== FreeCAD 中使用的许可证 ==
== FreeCAD 中使用的许可证 ==
</div>


FreeCAD 使用两种不同的许可, 一个用于应用程序本身, 另一个用于文档:
FreeCAD两种不同的许可, 一个用于应用程序本身, 另一个用于文档


<div class="mw-translate-fuzzy">
;[[wikipedia:LGPL|Lesser General Public Licence, version 2 or superior (LGPL2+)]]: 对于 src/App src/Gui src/Base 中的 .h 和 .cpp 文件中所述的核心库, 以及 src/Mod 中的所有 [[Workbenches/zh-cn|模块]], 以及在 src/main 中的 .h 和 .cpp 文件中所述的可执行程序。图标和其他图形部件也遵循 LGPL。
'''[[wikipedia:LGPL|Lesser General Public Licence, version 2 or superior (LGPL2+)]]'''用于所有FreeCAD的源代码。所谓源代码,即包含于[https://github.com/FreeCAD/FreeCAD 官方Git仓库]里的那些。
;[[wikipedia:Open Publication License|Open Publication Licence]]: 关于在 http://www.freecadweb.org 的文件, 当作者没有标记不同时。
</div>


<div class="mw-translate-fuzzy">
'''[http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0 License (CC-BY-3.0)]'''用于http://www.freecadweb.org上的文档。
</div>


有关在 FreeCAD 中的不同组件使用的许可证的详细信息, 请参阅 FreeCAD [http://sourceforge.net/p/free-cad/code/ci/master/tree/package/debian/copyright debian 版权文件]
FreeCAD中的不同组件可以使用不同的许可,有关其详细信息, 请参阅FreeCAD的[https://github.com/FreeCAD/FreeCAD/blob/master/package/debian/copyright debian版权文件]


<span id="Impact_of_the_licenses"></span>
== 许可证的影响 ==
<div class="mw-translate-fuzzy">
==许可证的影响==
</div>


下面,用更友好更容易懂的话,解释LGPL对你意味着什么:
=== 个人用户 ==
个人用户可以免费使用 FreeCAD, 基本上可以做任何他们想做的事情: 使用它, 复制它, 修改它, 重新分发它。
他们总是掌握自己的数据, 他们不被迫更新 FreeCAD, 改变他们对 FreeCAD 的使用。使用 FreeCAD 不约束他们任何形式的合同或义务。


=== 专业用户 ==
==== All users ====
可以自由使用 FreeCAD, 任何形式的私人或专业工作。他们可以根据自己的意愿自定义应用程序。它们可以向 FreeCAD 写入打开或关闭的源扩展。他们总是掌握自己的数据, 他们不被迫更新 FreeCAD, 改变他们对 FreeCAD 的使用。使用 FreeCAD 不约束他们任何形式的合同或义务。


<div class="mw-translate-fuzzy">
=== 开源开发者 ==
==== 所有用户 ====
可以使用 FreeCAD 作为自己的扩展模块的基础, 为特殊目的。他们可以选择 GPL 或 LGPL, 允许他们在专有软件中使用他们的作品。
任何人都可以下载它,使用它,重新分发它,完全免费,没有任何限制。你的那一份FreeCAD真的是你的,就像你用FreeCAD生产的文件一样。你不会隔一阵就被要求更新FreeCAD,也不用改变你对FreeCAD的用法。使用FreeCAD没有绑定,不会把你绑定在任何形式的合同或义务上。FreeCAD的源代码公开,可供检查,这就可以保证它不会发走你的私人数据,保证它不做此类你并不知情的事情。
</div>


==== Commercial developers ====
==== Professional users ====
Commercial developers can use FreeCAD as the groundwork for their own extension modules for special purposes and are not forced to make their modules open source. They can use all modules which use the LGPL. They are allowed to distribute FreeCAD along with their proprietary software. They will get the support of the author(s) as long as it is not a one way street.


<div class="mw-translate-fuzzy">
== OpenCasCade License side effects (for FreeCAD version 0.13 and older) ==
==== 专业用户 ====
自由使用FreeCAD吧,不管是私人、商业还是机构,FreeCAD可以用于任何目的。任何版本的FreeCAD,都可以在任何地方,无限次地部署和安装。你也可以修改和调整FreeCAD,来满足你自己的目的,没有任何限制。然而,你却不能让FreeCAD的开发者受到非难。使用FreeCAD过程中,可能造成损害或业务损失。开发者并不对此承担责任。
</div>


==== Open-source software developers ====
The following is no more applicable since version 0.14, since both FreeCAD and OpenCasCade are now fully LGPL.


<div class="mw-translate-fuzzy">
==== 开源软件开发者 ====
你可以把FreeCAD作为基础,开发你自己的应用,或者你可以简单地扩展它,为它创建新的模块。如果你将FreeCAD嵌入到你自己的应用里,你可以选择GPL或LGPL许可,或者与LGPL兼容的其他许可,使你的工作归为所有权软件,或者不归。如果你开发了一个模块,将用作FreeCAD的一个扩展,单丝它里面并不包含FreeCAD的任何代码,那么你就能选择你想要的任何许可。然而,如果你希望你的模块使用者众,最好还是保持与FreeCAD一致,使用LGPL许可。这样你的代码就更容易被将来的模块引用,甚至被FreeCAD本身吸纳。
</div>


==== Closed-source software developers ====
Up to Version 0.13 FreeCAD is delivered as GPL2+, although the source itself is under LGPL2+. Thats because of linkage of Coin3D (GPL2) and PyQt(GPL). Starting with 0.14 we will be completely GPL free. PyQt will be replaced by PySide, and Coin3D was re-licensed under BSD. One problem, we still have to face, license-wise, the [http://www.opencascade.org/getocc/license/ OCTPL (Open CASCADE Technology Public License)]. Its a License mostly LGPL similar, with certain changes. On of the originators, Roman Lygin, elaborated on the License on his [http://opencascade.blogspot.de/2008/12/license-to-kill-license-to-use.html Blog]. The home-brew OCTPL license leads to all kind of side effects for FreeCAD, which where widely discussed on different forums and mailing lists, e.g. on [http://www.opencascade.org/org/forum/thread_15859/?forum=3 OpenCasCade forum itself]. I will link here some articles for the biggest problems.


<div class="mw-translate-fuzzy">
==== GPL2/GPL3/OCTLP incompatibility ====
==== 不开源的开发者 ====
We first discovered the problem by a discussion on the [http://www.fsf.org/ FSF] high priority project [https://groups.google.com/forum/#!topic/polignu/XRergtwsm80 discussion list]. It was about a library we look at, which was licensed with GPL3. Since we linked back then with Coin3D, with GPL2 only, we was not able to adopt that lib. Also the
你可以把FreeCAD作为你的应用的基础,并不强迫开源你的应用。LGPL许可其实只要求两件简单的事情:1) 清楚地告知你的用户,你的应用里包含FreeCAD,声明FreeCAD使用LGPL许可;2) 清晰地将你自己的应用与FreeCAD组件区分开。这通常有两种实现形式。或者你动态地链接到FreeCAD组件,这样用户就被允许修改它;或者把FreeCAD源代码,还有你带来的修改,让你的用户可以获得。你将从FreeCAD开发者那里得到帮助,只要不是单向索取就好。
OCTPL is considered [http://www.opencascade.org/occt/faq/ GPL incompatible]. This Libre Graphics World article [http://libregraphicsworld.org/blog/entry/libredwg-drama-the-end-or-the-new-beginning "LibreDWG drama: the end or the new beginning?"] shows up the drama of LibreDWG project not acceptably in FreeCAD or LibreCAD.
</div>


1) You must clearly '''inform your users that your application is using FreeCAD''' and that FreeCAD is LGPL.
==== Debian ====
The incompatibility of the OCTPL [http://lists.debian.org/debian-legal/2009/10/msg00000.html was discussed on the debian legal list] and lead to a [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617613 bug report on the FreeCAD package] which prevent (ignor-tag) the transition from debian-testing to the main distribution. But its also mentioned thats a FreeCAD, which is free of GPL code and libs, would be acceptably. With a re-licensed Coin3D V4 and a substituted PyQt we will hopefully reach GPL free with the 0.14 release.


2) The LGPL license also stipulate your users must be able to swap your modified FreeCAD component with the original FreeCAD equivalent. That is would be done by dynamically linking to the FreeCAD components, so users are allowed to change it. However, this is often hard to achieve by today's requirements. At FreeCAD, we understand that the important point here is to not restrict the freedom given to FreeCAD users by the LGPL license. So an equivalent to dynamic linking is to offer the choice to your users, by '''making your users aware of the possibility to use FreeCAD for free'''. This can be done in a number of ways.
==== Fedora/RedHat non-free ====
In the Fedora project OpenCasCade is listed "non-free". This means basically it won't make it into Fedora or RedHat. This means also FreeCAD won't make it into Fedora/RedHat until OCC is changing its license. Here the links to the license evaluation:
* [http://lists.fedoraproject.org/pipermail/legal/2011-September/001713.html Discussion on the Fedora-legal-list]
* [https://bugzilla.redhat.com/show_bug.cgi?id=458974#c10 License review entry in the RedHat bug tracker]
The main problem they have AFIK is that the OCC license demand non discriminatory support fees if you want to do paid support. It has nothing to do with "free" or OpenSource, its all about RedHat's business model!


If any of the two conditions above are unacceptable to you or cannot be implemented, then you must make your FreeCAD component LGPL too and release the source code with all the modifications you made to it.
{{docnav|Dialog creation|Tracker}}


There is a special case called '''derivatives''', which is when you publish basically a "rebranded" version of FreeCAD. Derivatives which are not open-source are prohibited by the LGPL license. The FreeCAD community is active and efficient in finding rebranded versions, reporting them to the platforms where they were found and exposing them until they are taken down.
[[Category:Developer Documentation]]


==== Files ====
{{clear}}

<languages/>
<div class="mw-translate-fuzzy">
====文件====
上面提到的任何许可,都不针对你用FreeCAD制作的模型和文件。后者不受任何约束,不绑定于任何所有权。你的文件就是你的。你可以在FreeCAD里,通过"File -> Project Information",为你的文件设置所有者,指定你自己的许可协议。
</div>

== Logo ==

The FreeCAD logo is a [https://fpa.freecad.org/documents/Trademark.pdf trademark owned by the FPA (FreeCAD project association)]. This means the [https://fpa.freecad.org FPA] is the sole body authorized to say who has the right to use the FreeCAD logo or not. The logo files, which are part of the FreeCAD source code or available elsewhere, for example on this wiki, are still all under the same licenses as the rest of FreeCAD (LGPL for the source code and Creative Commons for this wiki). You are still free to use the FreeCAD logo anywhere, on the same terms as the rest of FreeCAD, which means, basically, that you must use it to reference FreeCAD, and not use it, for example, for your own product, or any other way that is not referencing FreeCAD.

== Statement of the main developer ==

<div class="mw-translate-fuzzy">
== 主开发者的声明 ==
我知道,网上讨论''"正确"''的开源协议,占用了互联网带宽的很大部分。所以这里我觉得,FreeCAD应该有这个协议。
</div>

<div class="mw-translate-fuzzy">
我选择了[http://en.wikipedia.org/wiki/LGPL LGPL]作为这个项目的许可协议,我知道LGPL的利与弊,我将给你解释一下做这个决定的原因。
</div>

FreeCAD是一个库和一个应用的混合体,所以要求GPL协议就显得太强人所难了。它将阻碍给FreeCAD写商用模块的努力,因为它不允许与FreeCAD的基础库建立链接。你可能会问,为什么要提商用模型?那我们看看Linux,它是个好例子。如果GNU C库采用GPL协议,那它就会阻止链接到非GPL的应用,Linux还会那么成功吗?还有,虽然我热爱Linux的自由,我也想使用非常优秀的NVIDIA 3D图形驱动。NVIDIA不想给出这些驱动的代码,我能理解也能接受这一点。我们都需要为公司工作,需要报酬,或者至少是食物。所以当遵守LGPL的规则,让开源软件和非开源软件和谐共处,对我来说并不是什么不好的事情。我希望看到的是,有个人为FreeCAD写了一个Catia的导入/导出处理器,然后把它免费分发,或者是赚一点钱。我不喜欢强迫他给出太多,超出他想给的。那不好,对他和对FreeCAD来说,都不好。

然而这个决定仅为 FreeCAD 的核心系统做出。每个应用模块的作者都可以做出自己的决定。

{{Quote|Jürgen Riegel|15 October 2006}}


{{Docnav
|[[Dialog_creation|Dialog creation]]
|[[Compile_on_Windows|Compiling on Windows]]
}}

{{Userdocnavi{{#translation:}}}}
[[Category:Developer Documentation{{#translation:}}]]

Latest revision as of 16:21, 4 April 2024

FreeCAD 中使用的许可证

FreeCAD有两种不同的许可, 一个用于应用程序本身, 另一个用于文档:

Lesser General Public Licence, version 2 or superior (LGPL2+)用于所有FreeCAD的源代码。所谓源代码,即包含于官方Git仓库里的那些。

Creative Commons Attribution 3.0 License (CC-BY-3.0)用于http://www.freecadweb.org上的文档。

FreeCAD中的不同组件可以使用不同的许可,有关其详细信息, 请参阅FreeCAD的debian版权文件

许可证的影响

下面,用更友好更容易懂的话,解释LGPL对你意味着什么:

All users

所有用户

任何人都可以下载它,使用它,重新分发它,完全免费,没有任何限制。你的那一份FreeCAD真的是你的,就像你用FreeCAD生产的文件一样。你不会隔一阵就被要求更新FreeCAD,也不用改变你对FreeCAD的用法。使用FreeCAD没有绑定,不会把你绑定在任何形式的合同或义务上。FreeCAD的源代码公开,可供检查,这就可以保证它不会发走你的私人数据,保证它不做此类你并不知情的事情。

Professional users

专业用户

自由使用FreeCAD吧,不管是私人、商业还是机构,FreeCAD可以用于任何目的。任何版本的FreeCAD,都可以在任何地方,无限次地部署和安装。你也可以修改和调整FreeCAD,来满足你自己的目的,没有任何限制。然而,你却不能让FreeCAD的开发者受到非难。使用FreeCAD过程中,可能造成损害或业务损失。开发者并不对此承担责任。

Open-source software developers

开源软件开发者

你可以把FreeCAD作为基础,开发你自己的应用,或者你可以简单地扩展它,为它创建新的模块。如果你将FreeCAD嵌入到你自己的应用里,你可以选择GPL或LGPL许可,或者与LGPL兼容的其他许可,使你的工作归为所有权软件,或者不归。如果你开发了一个模块,将用作FreeCAD的一个扩展,单丝它里面并不包含FreeCAD的任何代码,那么你就能选择你想要的任何许可。然而,如果你希望你的模块使用者众,最好还是保持与FreeCAD一致,使用LGPL许可。这样你的代码就更容易被将来的模块引用,甚至被FreeCAD本身吸纳。

Closed-source software developers

不开源的开发者

你可以把FreeCAD作为你的应用的基础,并不强迫开源你的应用。LGPL许可其实只要求两件简单的事情:1) 清楚地告知你的用户,你的应用里包含FreeCAD,声明FreeCAD使用LGPL许可;2) 清晰地将你自己的应用与FreeCAD组件区分开。这通常有两种实现形式。或者你动态地链接到FreeCAD组件,这样用户就被允许修改它;或者把FreeCAD源代码,还有你带来的修改,让你的用户可以获得。你将从FreeCAD开发者那里得到帮助,只要不是单向索取就好。

1) You must clearly inform your users that your application is using FreeCAD and that FreeCAD is LGPL.

2) The LGPL license also stipulate your users must be able to swap your modified FreeCAD component with the original FreeCAD equivalent. That is would be done by dynamically linking to the FreeCAD components, so users are allowed to change it. However, this is often hard to achieve by today's requirements. At FreeCAD, we understand that the important point here is to not restrict the freedom given to FreeCAD users by the LGPL license. So an equivalent to dynamic linking is to offer the choice to your users, by making your users aware of the possibility to use FreeCAD for free. This can be done in a number of ways.

If any of the two conditions above are unacceptable to you or cannot be implemented, then you must make your FreeCAD component LGPL too and release the source code with all the modifications you made to it.

There is a special case called derivatives, which is when you publish basically a "rebranded" version of FreeCAD. Derivatives which are not open-source are prohibited by the LGPL license. The FreeCAD community is active and efficient in finding rebranded versions, reporting them to the platforms where they were found and exposing them until they are taken down.

Files

文件

上面提到的任何许可,都不针对你用FreeCAD制作的模型和文件。后者不受任何约束,不绑定于任何所有权。你的文件就是你的。你可以在FreeCAD里,通过"File -> Project Information",为你的文件设置所有者,指定你自己的许可协议。

The FreeCAD logo is a trademark owned by the FPA (FreeCAD project association). This means the FPA is the sole body authorized to say who has the right to use the FreeCAD logo or not. The logo files, which are part of the FreeCAD source code or available elsewhere, for example on this wiki, are still all under the same licenses as the rest of FreeCAD (LGPL for the source code and Creative Commons for this wiki). You are still free to use the FreeCAD logo anywhere, on the same terms as the rest of FreeCAD, which means, basically, that you must use it to reference FreeCAD, and not use it, for example, for your own product, or any other way that is not referencing FreeCAD.

Statement of the main developer

主开发者的声明

我知道,网上讨论"正确"的开源协议,占用了互联网带宽的很大部分。所以这里我觉得,FreeCAD应该有这个协议。

我选择了LGPL作为这个项目的许可协议,我知道LGPL的利与弊,我将给你解释一下做这个决定的原因。

FreeCAD是一个库和一个应用的混合体,所以要求GPL协议就显得太强人所难了。它将阻碍给FreeCAD写商用模块的努力,因为它不允许与FreeCAD的基础库建立链接。你可能会问,为什么要提商用模型?那我们看看Linux,它是个好例子。如果GNU C库采用GPL协议,那它就会阻止链接到非GPL的应用,Linux还会那么成功吗?还有,虽然我热爱Linux的自由,我也想使用非常优秀的NVIDIA 3D图形驱动。NVIDIA不想给出这些驱动的代码,我能理解也能接受这一点。我们都需要为公司工作,需要报酬,或者至少是食物。所以当遵守LGPL的规则,让开源软件和非开源软件和谐共处,对我来说并不是什么不好的事情。我希望看到的是,有个人为FreeCAD写了一个Catia的导入/导出处理器,然后把它免费分发,或者是赚一点钱。我不喜欢强迫他给出太多,超出他想给的。那不好,对他和对FreeCAD来说,都不好。

然而这个决定仅为 FreeCAD 的核心系统做出。每个应用模块的作者都可以做出自己的决定。

Jürgen Riegel

—15 October 2006