License/de: Difference between revisions

Revision as of 21:46, 5 November 2014

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 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.

Used Licences

Here the two licences under which FreeCAD is published:

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 modules in src/Mod and for the executable as stated in the .h and .cpp files in src/main. The icons and other graphic parts are also LGPL.
Open Publication Licence: For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author

See FreeCAD's debian copyright file for more details about the licenses used in FreeCAD

License side effects

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 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 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 OpenCasCade forum itself. I will link here some articles for the biggest problems.

GPL2/GPL3/OCTLP incompatibility

We first discovered the problem by a discussion on the FSF high priority project 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 OCTPL is considered GPL incompatible. This Libre Graphics World article "LibreDWG drama: the end or the new beginning?" shows up the drama of LibreDWG project not acceptably in FreeCAD or LibreCAD.

Debian

The incompatibility of the OCTPL was discussed on the debian legal list and lead to a 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.

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:

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!

Impact of the licences

Private users

Private users can use FreeCAD free of charge and can do basically whatever they want to do with it....

Professional users

Can use FreeCAD freely, for any kind of private or professional work. They can customize the application as they wish. They can write open or closed source extensions to FreeCAD. They are always master of their data, they are not forced to update FreeCAD, change their usage of FreeCAD. Using FreeCAD doesn't bind them to any kind of contract or obligation.

Open Source developers

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.

Commercial developers

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.

Dialog creation

Tracker

Index

Other languages:

@@ Line 1: / Line 1: @@
 === 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 [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.
+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.
 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.
@@ Line 9: / Line 8: @@
 Nevertheless this decision is made only for the core system of FreeCAD. Every writer of an application module may make his own decision.
-=== Angewendete Lizenzen ===
+=== Used Licences ===
+Here the two licences under which FreeCAD is published:
+;[[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 [[Workbenches|modules]] in src/Mod and for the executable as stated in the .h and .cpp files in src/main. The icons and other graphic parts are also LGPL.
-Hier die zwei Lizenzen, unter welchen FreeCAD veröffentlicht ist:
+;[[wikipedia:Open Publication License|Open Publication Licence]]: For the documentation on http://free-cad.sourceforge.net/ as not marked differently by the author
-;[[wikipedia:LGPL|Lesser General Public Licence (LGPL2+)]]: Für die Kern-Bibliotheken, wie angegeben in den .h and .cpp-Dateien in: src/App src/Gui src/Base und die meisten [[Workbenches/de|modules]] in src/Mod und für die ausführbaren, wie angegeben in den .h und .cpp-Dateien in src/main. Die Icons und andere grafische Anteile sind ebenfalls LGPL.
-;[[wikipedia:Open Publication License|Open Publication Licence]]: Für die Dokumentation auf http://free-cad.sourceforge.net/ , solange durch den Author nicht anders angegeben.
-Lesen Sie FreeCAD's [http://free-cad.git.sourceforge.net/git/gitweb.cgi?p=free-cad/free-cad;a=blob;f=package/debian/copyright;h=a97cf019d020edba596f2d0f614c9b09ce546b0f;hb=HEAD debian copyright file] für mehr Details über die in FreeCAD angewendeten Lizenzen
+See FreeCAD's [http://free-cad.git.sourceforge.net/git/gitweb.cgi?p=free-cad/free-cad;a=blob;f=package/debian/copyright;h=a97cf019d020edba596f2d0f614c9b09ce546b0f;hb=HEAD debian copyright file] for more details about the licenses used in FreeCAD
-=== Lizenzen und deren Nebenwirkungen ===
+=== License side effects ===
-Bis zur Version 0.13, wird FreeCAD unter GPL2+ ausgeliefert, obgleich der Quellcode unter LGPL2+ steht. Dies ist wegen der Bindung an Coin3D(GPL2) und PyQt(GPL). Ab Version 0.14 werden wir vollständig GPL-frei. PyQt wird ersetzt durch PySide, und Coin3D wurde erneut Lizensiert unter BSD. Mit einem Problem; Lizenbezogen; sind wir noch konfrontiert: Die [http://www.opencascade.org/getocc/license/ OCTPL (Open CASCADE Technology Public License)]. Es ist eine Lizenz meist LGPL ähnlich, mit einigen Änderungen. Einer der Urheber, Roman Lygin, erarbeitete diese Lizenz auf seinem [http://opencascade.blogspot.de/2008/12/license-to-kill-license-to-use.html Blog]. Die Hausgemachte OCTPL Lizenz führt zu vielen Arten von Nebenwirkungen für FreeCAD, die bereits weiträumig auf verschiedenen Foren und Mailinglisten diskutiert wurden, z.B. auf [http://www.opencascade.org/org/forum/thread_15859/?forum=3 OpenCasCade forum]. Hier werden einige Artikel mit den wichtigsten Problemen aufgeführt.
+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.
+==== GPL2/GPL3/OCTLP incompatibility ====
-==== GPL2/GPL3/OCTLP Inkompatibilität ====
+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
+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.
-Wir haben dies Problem zuerst wahrgenommen bei einer Diskussion über das [http://www.fsf.org/ FSF] hoch priorisierte Projekt [https://groups.google.com/forum/#!topic/polignu/XRergtwsm80 discussion list]. Es geht um eine Bibliothek die wir beobachten, welche mit GPL3 lizenziert war. Da wir wieder verbunden sind mit Coin3D, die nur GPL2 hat, waren wir nicht in der Lage, diese lib anzunehmen.
-Trotz der Tatsache, dass OCTPL als [http://www.opencascade.org/occt/faq/ GPL incompatible] gilt. Dieser Libre Graphics World Artikel [http://libregraphicsworld.org/blog/entry/libredwg-drama-the-end-or-the-new-beginning "LibreDWG drama: the end or the new beginning?"] zeigt die Dramatik des LibreDWG Projekt, die es inakzeptabel für FreeCAD oder LibreCAD macht.
+==== 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.
-==== Debian ====
-Die Inkompatibilität der OCTPL [http://lists.debian.org/debian-legal/2009/10/msg00000.html wurde diskutiert auf der Debian legal list] und führte zu einem [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617613 bug report am FreeCAD package]; dieser verhindert (Ignor-tag) den Übergang von debian-testing dem Hauptverteiler. Aber es ist auch erwähnt, das ist ein FreeCAD, welches frei von GPL-Code und Bibliotheken ist, akzeptabel wäre. Mit einem Re-lizenzierten Coin3D V4 und einem substituierten PyQt, werden wir hoffentlich den GPL-free-Zustand mit dem 0,14-release erreichen.
 ==== Fedora/RedHat non-free ====
-In the Fedora project OpenCasCade is listed "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:
-Im Fedora-Projekt ist opencascade aufgeführt als "non-free". Dies bedeutet im Grunde ist es wird nicht eingefügt in Fedora oder RedHat. Dies bedeutet auch, FreeCAD wird es nicht in Fedora/RedHat schaffen, bis OCC seine Lizenz ändert. Hier die Links zu den Lizenz-Auswertung:
 * [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!
-Das Hauptproblem ist, soweit wir sehen, dass die OCC-Lizenz nicht diskriminierend Support-Gebühren verlangt, wenn Sie bezahlt Unterstützung leisten wollen. Es hat nichts mit "frei" oder OpenSource tun, das ist das reine RedHat Geschäftsmodell!
-=== Auswirkungen der Lizenzen ===
+=== Impact of the licences ===
-==== Private Nutzer ====
+==== Private users ====
-Private Nutzer können FreeCAD völlig gratis verwenden und generell alles damit machen was sie wollen....
+Private users can use FreeCAD free of charge and can do basically whatever they want to do with it....
-==== Professionelle Nutzer ====
+==== Professional users ====
+Can use FreeCAD freely, for any kind of private or professional work. They can customize the application as they wish. They can write open or closed source extensions to FreeCAD. They are always master of their data, they are not forced to update FreeCAD, change their usage of FreeCAD. Using FreeCAD doesn't bind them to any kind of contract or obligation.
-Können FreeCAD frei einsetzen, für jede Art privater oder professioneller Arbeit. Sie können die Anwendung nach eigenen Wünschen anpassen. Sie können open- oder closed-source-Erweiterungen für FreeCAD erstellen. Sie bleiben immer Herr ihrer Daten, sie werden nicht gezwungen FreeCAD zu aktualisieren oder die Art und Weise ihrer FreeCAD-Nutzung zu ändern. Die Nutzung von FreeCAD hat in keiner Weise vertragliche oder verpflichtende Bindungen zur Folge.
-==== Open Source Entwickler ====
+==== Open Source developers ====
+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.
-können FreeCAD als Grundlage für eigene Erweiterungs-module für spezielle Einsätze verwenden. Sie können wählen, entweder die GPL oder die LGPL anzuwenden, die Verwendung ihrer Arbeit auch in proprietärer Software zu erlauben oder auch nicht.
-==== Professionelle Entwickler ====
+==== Commercial developers ====
+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.
-Professionelle Entwickler können FreeCAD als Grundstein für ihre eigenen Erweiterungsmodule für spezielle Zwecke nutzen und sind nicht gezwungen, ihre Entwicklung als Open-Source zu behandeln. Sie können alle Module verwenden, die unter LGPL stehen. Sie dürfen FreeCAD zusammen mit ihrer proprietären Software verteilen. Sie erhalten die Unterstützung der Autor(en), solange es sich nicht um eine Einbahnstraße handelt.
-{{docnav/de|Dialog creation/de|Tracker/de}}
+{{docnav|Dialog creation|Tracker}}
+[[Category:Developer Documentation]]
-{{languages/de | {{en|Licence}} {{es|Licence/es}} {{fr|Licence/fr}} {{jp|Licence/jp}} {{ru|Licence/ru}} {{se|Licence/se}} }}
+{{clear}}
-[[Category:Developer Documentation/de]]
+<languages/>