Difference between revisions of "Licence"

From FreeCAD Documentation
Jump to: navigation, search
m (→)
 
(37 intermediate revisions by 12 users not shown)
Line 1: Line 1:
=== Statement of the maintainer ===
+
<languages/>
 +
<translate>
 +
<!--T:25-->
 +
{{docnav|Dialog creation|Tracker}}
  
I know that the discussion on the ''"right"'' licence for open source occupied a significant portion of internet bandwidth and so is here the reason why, in my opinion, FreeCAD should have this one.
+
== Licences used in FreeCAD == <!--T:5-->
 +
 
 +
<!--T:19-->
 +
FreeCAD uses two different licenses, one for the application itself, and one for the documentation:
 +
 
 +
<!--T:6-->
 +
'''[[wikipedia:LGPL|Lesser General Public Licence, version 2 or superior (LGPL2+)]]''' For all of the FreeCAD source code found in the [https://github.com/FreeCAD/FreeCAD official Git repository]
 +
 
 +
<!--T:22-->
 +
'''[http://creativecommons.org/licenses/by/3.0/ Creative Commons Attribution 3.0 License (CC-BY-3.0)]''' For the documentation on http://www.freecadweb.org
 +
 
 +
<!--T:7-->
 +
See FreeCAD's [https://github.com/FreeCAD/FreeCAD/blob/master/package/debian/copyright debian copyright file] for more details about the licenses used by the different open-source components used in FreeCAD
 +
 
 +
== Impact of the licences == <!--T:12-->
 +
 
 +
<!--T:23-->
 +
Below is a friendlier explanation of what the LGPL license means for you:
  
I chose the [http://en.wikipedia.org/wiki/LGPL LGPL] and the [http://en.wikipedia.org/wiki/GPL GPL] for the project and I know the pro and cons about the LGPL and will give you some reasons for that decision.
+
==== All users ==== <!--T:13-->
 +
Anybody can download, use and redistribute FreeCAD free of charge, without any restriction. Your copy of FreeCAD is truly yours, as are the files you produce with FreeCAD. You will not be forced to update FreeCAD after a certain time, nor change your usage of FreeCAD. Using FreeCAD doesn't bind you to any kind of contract or obligation. The FreeCAD source code is public and can be inspected, so it is possible to verify that it doesn't do things without your knowledge such as sending your private data somewhere.
  
FreeCAD is a mixture of a library and an application, so the GPL would be a little bit strong for that. It would prevent writing commercial modules for FreeCAD because it would prevent linking with the FreeCAD base libs. You may ask why commercial modules at all? Therefore Linux is good example. Would Linux be so successful when the GNU C Library would be GPL and therefore prevent linking against non-GPL applications? And although I love the freedom of Linux, I also want to be able to use the very good NVIDIA 3D graphic driver. I understand and accept the reason NVIDIA does not wish to give away driver code. We all work for companies and need payment or at least food. So for me, a coexistence of open source and closed source software is not a bad thing, when it obeys the rules of the LGPL. I would like to see someone writing a Catia import/export processor for FreeCAD and distribute it for free or for some money. I don't like to force him to give away more than he wants to. That wouldn't be good neither for him nor for FreeCAD.
+
==== Professional users ==== <!--T:14-->
 +
FreeCAD can be used freely for any kind of purpose, being private, commercial or institutional. Any version of FreeCAD can be deployed and installed anywhere, any number of times. You can also modify and adapt FreeCAD for your own purposes without any restriction. However, you cannot make the FreeCAD developers liable for possible damage or business loss that could occur from using FreeCAD.
  
Nevertheless this decision is made only for the core system of FreeCAD. Every writer of an application module may make his own decision.
+
==== Open-source software developers ==== <!--T:15-->
 +
You can use FreeCAD as a base to develop your own application, or simply extend it by creating new modules for it. If FreeCAD is embedded into your own application, you can choose either the GPL or the LGPL license, or any other license that is compatible with LGPL, to allow the use of your work in proprietary software or not. If you are developing a module to be used as an extension, and don't include any of the FreeCAD code in it, then you can choose any license you want. However, if you wish to see your module used as much as possible, it is a good idea to use the same LGPL license as FreeCAD itself, so parts of your code can be more easily reused in other future modules or even in FreeCAD itself.
  
=== Used Licences ===
+
==== Closed-source software developers ==== <!--T:16-->
 +
You can use FreeCAD as a base for your own application, and are not forced to make your application open source. The LGPL license, however, ask for two basic things: 1) that you clearly inform your users that your application is using FreeCAD and that FreeCAD is LGPL-licensed, and 2) that you clearly separate your own application form the FreeCAD components. That is usually done by either dynamically linking to the FreeCAD components, so users are allowed to change it, or making the FreeCAD source code, along with the modifications you brought to it, available to your users. You will get support from the FreeCAD developers as long as it is not a one way street.
  
Here the three licences under which FreeCAD is published:
+
==== Files ==== <!--T:24-->
 +
The models and other files produced with FreeCAD are not subject to any license stated above, nor bound to any kind of restriction or ownership. Your files are truly yours. You can set the owner of the file and specify your own license terms for the files you produce inside FreeCAD, via menu File → Project Information.
  
;[[wikipedia:GPL|General Public Licence (GPL2+)]]: For the Python scripts to build the binaries as stated in the .py files in src/Tools
+
== Statement of the main developer == <!--T:1-->
;[[wikipedia:LGPL|Lesser General Public Licence (LGPL2+)]]: For the core libs as stated in the .h and .cpp files in src/App src/Gui src/Base and most [[Module|modules]] in src/Mod and for the executable as stated in the .h and .cpp files in src/main
+
I know that the discussion on the ''"right"'' licence for open source occupied a significant portion of internet bandwidth and so is here the reason why, in my opinion, FreeCAD should have this one.
;[[wikipedia:Open Publication License|Open Publication Licence]]: For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author
 
  
We try to use only LGPL type licences for the core system linked libraries (see [[Third Party Libraries]]) with one exception:
+
<!--T:2-->
* the Coin3D licence ([http://www.coin3d.org/licensing/ www.coin3d.org]).
+
I chose the [http://en.wikipedia.org/wiki/LGPL LGPL] for the project and I know the pro and cons about the LGPL and will give you some reasons for that decision.
  
See FreeCAD's [http://free-cad.svn.sourceforge.net/viewvc/free-cad/trunk/debian/copyright?view=markup debian copyright file] for more details about the licenses used in FreeCAD
+
<!--T:3-->
 +
FreeCAD is a mixture of a library and an application, so the GPL would be a little bit strong for that. It would prevent writing commercial modules for FreeCAD because it would prevent linking with the FreeCAD base libs. You may ask why commercial modules at all? Therefore Linux is good example. Would Linux be so successful when the GNU C Library would be GPL and therefore prevent linking against non-GPL applications? And although I love the freedom of Linux, I also want to be able to use the very good NVIDIA 3D graphic driver. I understand and accept the reason NVIDIA does not wish to give away driver code. We all work for companies and need payment or at least food. So for me, a coexistence of open source and closed source software is not a bad thing, when it obeys the rules of the LGPL. I would like to see someone writing a Catia import/export processor for FreeCAD and distribute it for free or for some money. I don't like to force him to give away more than he wants to. That wouldn't be good neither for him nor for FreeCAD.
  
=== Impact of the licences ===
+
<!--T:4-->
 +
Nevertheless this decision is made only for the core system of FreeCAD. Every writer of an application module may make his own decision.
  
==== Private users ====
+
<!--T:27-->
Private users can use FreeCAD free of charge and can do basically whatever they want to do with it....
+
{{Quote|Jürgen Riegel|15 October 2006}}
  
==== Professional users ====
+
<!--T:17-->
Can use FreeCAD for all kind of professional work without fee, they can customize the application as they wish. They can write or have written open or closed source extensions to FreeCAD. They are always master of their data and yet not forced to update FreeCAD or change the usage of FreeCAD.
+
{{docnav|Dialog creation|Tracker}}
  
==== Open Source developers ====
+
<!--T:26-->
Can use FreeCAD as the groundwork for own extension modules for special purposes. They can choose either the GPL or the LGPL to allow the use of their work in proprietary software or not.
+
{{Userdocnavi}}
  
==== Professional developers ====
+
<!--T:18-->
Professional 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. If you want to sell your module you need a QT licence and a Coin3D licence, otherwise you are forced by these libraries to make it open source.
+
[[Category:Developer Documentation]]
  
[[Category:Developer]]
+
</translate>
 +
{{clear}}

Latest revision as of 10:12, 18 May 2019

Other languages:
čeština • ‎Deutsch • ‎English • ‎español • ‎français • ‎italiano • ‎polski • ‎română • ‎русский • ‎svenska • ‎Türkçe • ‎中文(中国大陆)‎ • ‎中文(台灣)‎

Licences used in FreeCAD

FreeCAD uses two different licenses, one for the application itself, and one for the documentation:

Lesser General Public Licence, version 2 or superior (LGPL2+) For all of the FreeCAD source code found in the official Git repository

Creative Commons Attribution 3.0 License (CC-BY-3.0) For the documentation on http://www.freecadweb.org

See FreeCAD's debian copyright file for more details about the licenses used by the different open-source components used in FreeCAD

Impact of the licences

Below is a friendlier explanation of what the LGPL license means for you:

All users

Anybody can download, use and redistribute FreeCAD free of charge, without any restriction. Your copy of FreeCAD is truly yours, as are the files you produce with FreeCAD. You will not be forced to update FreeCAD after a certain time, nor change your usage of FreeCAD. Using FreeCAD doesn't bind you to any kind of contract or obligation. The FreeCAD source code is public and can be inspected, so it is possible to verify that it doesn't do things without your knowledge such as sending your private data somewhere.

Professional users

FreeCAD can be used freely for any kind of purpose, being private, commercial or institutional. Any version of FreeCAD can be deployed and installed anywhere, any number of times. You can also modify and adapt FreeCAD for your own purposes without any restriction. However, you cannot make the FreeCAD developers liable for possible damage or business loss that could occur from using FreeCAD.

Open-source software developers

You can use FreeCAD as a base to develop your own application, or simply extend it by creating new modules for it. If FreeCAD is embedded into your own application, you can choose either the GPL or the LGPL license, or any other license that is compatible with LGPL, to allow the use of your work in proprietary software or not. If you are developing a module to be used as an extension, and don't include any of the FreeCAD code in it, then you can choose any license you want. However, if you wish to see your module used as much as possible, it is a good idea to use the same LGPL license as FreeCAD itself, so parts of your code can be more easily reused in other future modules or even in FreeCAD itself.

Closed-source software developers

You can use FreeCAD as a base for your own application, and are not forced to make your application open source. The LGPL license, however, ask for two basic things: 1) that you clearly inform your users that your application is using FreeCAD and that FreeCAD is LGPL-licensed, and 2) that you clearly separate your own application form the FreeCAD components. That is usually done by either dynamically linking to the FreeCAD components, so users are allowed to change it, or making the FreeCAD source code, along with the modifications you brought to it, available to your users. You will get support from the FreeCAD developers as long as it is not a one way street.

Files

The models and other files produced with FreeCAD are not subject to any license stated above, nor bound to any kind of restriction or ownership. Your files are truly yours. You can set the owner of the file and specify your own license terms for the files you produce inside FreeCAD, via menu File → Project Information.

Statement of the main developer

I know that the discussion on the "right" licence for open source occupied a significant portion of internet bandwidth and so is here the reason why, in my opinion, FreeCAD should have this one.

I chose the LGPL for the project and I know the pro and cons about the LGPL and will give you some reasons for that decision.

FreeCAD is a mixture of a library and an application, so the GPL would be a little bit strong for that. It would prevent writing commercial modules for FreeCAD because it would prevent linking with the FreeCAD base libs. You may ask why commercial modules at all? Therefore Linux is good example. Would Linux be so successful when the GNU C Library would be GPL and therefore prevent linking against non-GPL applications? And although I love the freedom of Linux, I also want to be able to use the very good NVIDIA 3D graphic driver. I understand and accept the reason NVIDIA does not wish to give away driver code. We all work for companies and need payment or at least food. So for me, a coexistence of open source and closed source software is not a bad thing, when it obeys the rules of the LGPL. I would like to see someone writing a Catia import/export processor for FreeCAD and distribute it for free or for some money. I don't like to force him to give away more than he wants to. That wouldn't be good neither for him nor for FreeCAD.

Nevertheless this decision is made only for the core system of FreeCAD. Every writer of an application module may make his own decision.

Jürgen Riegel
—15 October 2006