So there are no closed source cura versions for customer companies who bought and modified it?Edited by Daniel26
There are companies that take the open source, make changes and give these modified Cura versions to their clients, forgetting to share the changes. This does not make Cura any less open source, but it does make those companies arses.
But doesn't this biolate the GPL?
Atm. I have a Slicer with compiled pyc. I decompiled it, took the code I needed an made a PostProcessScript of it.
But I'm a little concerned of there reaction.
Those companies that "forget" to share their changes violate the LGPL license.
The LGPL license that Cura is licensed under fully allows you, as an enduser, to make changes to the program. Because "the company" used Cura which is licensed under LGPL, they cannot forbid you to make changes to their version of Cura. You are not obligated to share these changes, unless you distribute the changed program. If "the company" distributed their version of Cura to you, you would be in your right to demand the source of the changes.
Do note that this is my reading of just part of the rules of the LGPL, and I am not a lawyer (so what do I know?).Edited by ahoeben
18 hours ago, ahoeben said:
so what do I know?
Possibly more than those companies you mentioned 😉
I've written a postProcessScript which add a preview and the time infos for the chitu boards.
How is the best way to get it ino cura? Is is in my private git repo.
All third party contributions start as a pull request on github
Yes it is, you can find the source code on Github, fork it and build your own version if you want.
Link to post
Share on other sites