You are not logged in. Please login or register.
SoliForum - 3D Printing Community → Solidoodle Discussion → If Solidoodle is closed source why are they running Marlin?
It specifically says in the download page for Marlin not to use it for closed source machines. Am I missing something here?
You're not missing anything. Put simply, Solidoodle is blatantly disregarding the request of a hardworking developer.
The only thing legally enforceable is the GPL license, which Solidoodle was in violation of for quite a while before they finally came into compliance. The issue was actually one of only two postings here in the forum by the CEO:
It specifically says in the download page for Marlin not to use it for closed source machines. Am I missing something here?
Yes, it's a frustrating situation. Compliance, and developer wishes are something to be taken seriously.
I think a BSD licensed firmware might be a bit more apropriate for Solidoodle (not that they have a choice). I'm not sure there is 3D printer firmware that has that right now. Maybe someday, many years from now, I'll attempt to write my own firmware for 3D printers - I usually don't mind working with the BSD license myself.
Aside:
I really do think the Marlin firmware could use a major refactor / rewrite. Of course marlin represents a wonderful community effort, and certainly works well. It is very servicible right now, but I don't think it's the most legible, or consistant code. It is sort of the joining of a couple disparate firmwares, and it shows. If I were to rewrite it, I'd apply lots of testing, and process. Set up a nice QEMU environment, mock up some static analysis scripts to help with 3D printing related issues. Optimize for a single board / chipset.
But I wouldn't attempt this for several years. I'm glad to get a little space from 3D printing. Who know's where we are going mother board wise in the next few years?
Could be that firmware for these things will for little linux machines like the rasberry pi soon. Or maybe something realtime like QNX.
Possibiltiies are endless.
Former Solidoodle employee comes in here and craps on the open source firmware that they've been basically stealing for years now, and continue to do so against the developer's wishes.
If you guys thought Marlin was so bad, the least you/Solidoodle could have done was contribute some improvements, since you were using/profiting off it against Erik's wishes.
I don't think he was saying it sucks, he was just saying it is a bit of a mish-mash of code... I've looked at a bit of it by now and I would tend to agree. I have a lot of experience working on larger projects and Marlin could certainly use a more reliable test bed and a significant amount of refactoring. Such is life with software projects. Sometimes I feel like more time is spent refactoring and testing than writing the original code 
Nonetheless, I was reading the thread Tim linked to and solidoodle's response to their lack of compliance with the GPL is absolutely shameful. Empty words from "fantastic Sam," which shouldn't really surprise anybody. It's too bad, really, because they ultimately steal Marlin because they can't afford and can't attract developers with the skills to write new firmware. I've done that too, in other applications. Not easy. Fun when stuff works though.
So, speaking of re-written firmware, I see the RepetierHost folks also have repetier firmware now. Anyone know anything about it? Can it work on a solidoodle? Advantages? Disadvantages?
Pretty much any firmware will work on a Solidoodle. I don't have the answers you're looking for but I intend to try it out soon. Setup shouldn't be difficult, the only thing I anticipate any trouble with is the NC endstops on the Solidoodle. How I handle that depends on how RepFirmware detects them with default configuration.
So, speaking of re-written firmware, I see the RepetierHost folks also have repetier firmware now. Anyone know anything about it? Can it work on a solidoodle? Advantages? Disadvantages?
That's been around for quite a while now. I don't think they've attracted much of a fan base for it.
Former Solidoodle employee comes in here and craps on the open source firmware that they've been basically stealing for years now, and continue to do so against the developer's wishes.
If you guys thought Marlin was so bad, the least you/Solidoodle could have done was contribute some improvements, since you were using/profiting off it (against Erik's wishes).
I wasn't meaning to speak ill of it. Software ends up being a ball of mud over time, unless there are plenty of hands on deck. I would have liked to have contributed to the firmware, had I been given the chance.
Anyway, if SD had a BSD licensed firmware, this would be less an issue. Given the closed source nature of the machine, it would be easier for SD to respect the license that way.
As for Erik, I don't think anyone ever meant to offend him. During my time at SD, I spoke to him a few times over IRC/E-mail. He didn't seem to take any offense to our existance or use of the firmware at that point (this around the SD2 days.) I think the Marlin firmware was created just to get a job done - it's development was quite collaborative, and I bet the original developers were pleasantly surprised that it was so widely used.
But maybe we did offend them, and I just didn't know about it. It seems the "Marlin" crowd is most concerned with Repraps. That's just my experience with it.
As for Erik, I don't think anyone ever meant to offend him. During my time at SD, I spoke to him a few times over IRC/E-mail. He didn't seem to take any offense to our existance or use of the firmware at that point (this around the SD2 days.
Did you tell Erik the SD2 was completely closed source, and that you weren't providing the source or the GPL license with your printers at that that time? If you did, and he was fine with that, then I don't understand why he would post this on his github:
Marlin has a GPL license because I believe in open development. Please do not use this code in products (3D printers, CNC etc) that are closed source or are crippled by a patent.
solijohn wrote:As for Erik, I don't think anyone ever meant to offend him. During my time at SD, I spoke to him a few times over IRC/E-mail. He didn't seem to take any offense to our existance or use of the firmware at that point (this around the SD2 days.
Did you tell Erik the SD2 was completely closed source, and that you weren't providing the source or the GPL license with your printers at that that time? If you did, and he was fine with that, then I don't understand why he would post this on his github:
marlin firmware wrote:Marlin has a GPL license because I believe in open development. Please do not use this code in products (3D printers, CNC etc) that are closed source or are crippled by a patent.
He was aware that it was closed source. I don't know about the GPL license thing. As I recall his attitude was more on the level of "whatever, yet another rep rap clone." I also remember the attitude of the wider RepRap community being something on the level of "Closed source. Stamped metal. Whatever." Had anyone formally asked us to stop using it, I imagine we would have had to look into using an alternative. It was never, ever, a secret that the Solidoodle was closed source.
The original thread about the compliance issue tells the story of the license issues very well. In my opinion, the important part is that there were in fact corrections to the process. I will also state my opinion that there wasn't any harm meant, nor any over arching plan of license violation. I don't believe SD had anything to gain from making the origin of the firmware or its license vague. Nor do I have anything to gain from reiterating that point now.
At any rate, to reiterate my original point: Had Solidoodle had acess to a BSD licensed firmware, they would have avoided a lot of those problems.
SoliForum - 3D Printing Community → Solidoodle Discussion → If Solidoodle is closed source why are they running Marlin?
Powered by PunBB, supported by Informer Technologies, Inc.
