Licence: Difference between revisions

From FreeCAD Documentation
No edit summary
No edit summary
Line 3: Line 3:
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 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 [[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.
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.


FreeCAD is a mixture of a Library and an Application, so the GPL would be a little bit strong for that. It would prevent write 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 write 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 would be good neither for him, nor for FreeCAD.
FreeCAD is a mixture of a Library and an Application, so the GPL would be a little bit strong for that. It would prevent write 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 write 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 would be good neither for him, nor for FreeCAD.
Line 14: Line 14:


* General Public License ([[http://en.wikipedia.org/wiki/GPL|GPL]])
* General Public License ([[http://en.wikipedia.org/wiki/GPL|GPL]])
For the executable as stated in the .h and .cpp files in src/main
For the executable as stated in the .h and .cpp files in src/main
* Lesser General Public License ([[http://en.wikipedia.org/wiki/LGPL|LGPL]])
* Lesser General Public License ([[http://en.wikipedia.org/wiki/LGPL|LGPL]])
For the core DLLs as stated in the .h and .cpp files in src/App src/Gui src/Base and most modules in src/Mod
For the core DLLs as stated in the .h and .cpp files in src/App src/Gui src/Base and most modules in src/Mod
* Open Publication License (OPL)
* Open Publication License (OPL)
For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author
For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author


We try to use for the core system linked libraries (see Third Party Libraries) only LGPL type licences with two exception, the QT license (http://www.trolltech.com/products/licensing.html) and the Coin3D license (http://www.coin3d.org/licensing/).
We try to use for the core system linked libraries (see Third Party Libraries) only LGPL type licences with two exception, the QT license (http://www.trolltech.com/products/licensing.html) and the Coin3D license (http://www.coin3d.org/licensing/).

Revision as of 13:25, 15 October 2006

Statement of the maintainer

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 and the GPL 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 write 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 write 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 would 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.

Used Licences

Here the three licences under which FreeCAD is published:

  • General Public License ([[1]])

For the executable as stated in the .h and .cpp files in src/main

  • Lesser General Public License ([[2]])

For the core DLLs as stated in the .h and .cpp files in src/App src/Gui src/Base and most modules in src/Mod

  • Open Publication License (OPL)

For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author

We try to use for the core system linked libraries (see Third Party Libraries) only LGPL type licences with two exception, the QT license (http://www.trolltech.com/products/licensing.html) and the Coin3D license (http://www.coin3d.org/licensing/).


Impact of the licenses

Private users

Private users can use FreeCAD free of charge and can do basically what ever he wants to do with it....

Profesional users

Can use FreeCAD for all kind of profesional work without fee. Can customize the application as he wishes. He can write or have writen open or closed source extensions to FreeCAD. He is always master of his data and yet not forced to update FreeCAD or change the usage of FreeCAD.

OSS Developers

Can use FreeCAD as the ground work for own extension modules for special purposes. He can choose either the GPL or the LGPL to allow the use of his work in proprietary software or not.

Profesional Developers

Can use FreeCAD as the ground work for his own extension modules for special purposes and is not forced to make his modules open source. He can use all modules which use the LGPL. He is allowed to distribute FreeCAD along with his proprietary software. He will get the support of the author(s) as long its not a one way street. If you whant to sell your module you need a QT licence and a Coin3D licence, other whise you are forced by this libraries to make open source.