Reviewing the K1 Max and also reviewing the K1 again! https://youtu.be/VCzsSCN95Tg
Introducing The Creality K1 Max! (And how is the K1 after 100+ hours?)

YouTube

@lostintech So, Creality still violating open source licenses.

Qidi didn't do a perfect job of how they released the sources but at least they appear to have done so on a timely basis.

I ordered the Qidi X-Max3 instead of the K1 Max, and Qidi honoring the open source license terms was a major factor in this decision. Ordering the Creality would be a slap in the face to everyone who has contributed to all the software Creality are currently using in violation of license terms.

@mcdanlj @lostintech I was critical of qidi and their lack of source nor root on the SBC, but I understand those are resolved?

The K1 Max is appealing, but I’d yeah, that OSS compliance is a no-go. I’m actually curious if -any- 3d printing manufacturer has an OSPO (or really anyone looking after open source concerns). I kind of doubt it.

@linux_mclinuxface @lostintech As far as I can tell, Qidi has released full source. They didn't do it in the best way, by forking; they just uploaded a bundle of files. But it would be possible to work out what they changed, and they did at least release the files. And I thought they did it before or contemporaneously with selling the printer?

Given that they sent a new emmc to one reviewer who updated Klipper (don't remember who) it must be possible (though, without merging, a temporarily bad idea).

I'll find out more when my Qidi arrives...

Creality doubling down on their license violation and calling their changes to open source their own proprietary work is appalling and immoral as well as illegal. Making a mistake is one thing, everyone does that. But defending it and refusing to fix it? That's just not OK.

@mcdanlj @linux_mclinuxface I don't think qidi has released cura source, have they released prusaslicer source since they recently adopted that too?

@lostintech @linux_mclinuxface https://github.com/QIDITECH/QIDISlicer (based on prusa-slicer) has been out there for a few months.

https://github.com/QIDITECH/Qidi-Print (based on Cura) has been there at least since last year.

I haven't tested building either; I just see both there.

Qidi very annoyingly don't preserve history, they just upload copies of source code to fairly minimally comply. That's annoying and bad practice and they should be encouraged to do it right.

But at least they are following the license terms as far as I can tell.

GitHub - QIDITECH/QIDISlicer: QIDISlicer gets your 3D printing easier and faster.

QIDISlicer gets your 3D printing easier and faster. - GitHub - QIDITECH/QIDISlicer: QIDISlicer gets your 3D printing easier and faster.

GitHub
@mcdanlj @linux_mclinuxface I guess maybe there's mimimal evidence out there of how much effort it took for all of us (the cura team and many content creators, self included) to get qidi to publish the cura source, a lot happened behind the scenes. Glad to see they eventually did, but this is a perfect example of how we can work with manufacturers constructively to solve these problems.

@lostintech @linux_mclinuxface Thank you, then, for that work! ❤️

Creality seems to do this over and over, though. Isn't that disheartening?

@mcdanlj @linux_mclinuxface I've had extended discussions on discord about why creality do the things they do, and honestly, none of it makes sense. But personally? No, not really. I make content, if they wish that content to be about how they've hidden klipper, that's their prerogative 😅

@lostintech @mcdanlj Humm. Never looked into Cura before. It’s LGPL-3 (… that’s a choice). So it depends how qudi uses the source. I suspect they would need to release it (but I’m not a lawyer)

https://fossa.com/blog/open-source-software-licenses-101-lgpl-license/amp/

Open Source Software Licenses 101: The LGPL License - FOSSA

The LGPL open source software license is a member of the GPL family, but with some significant differences from its stronger copyleft counterparts.

Dependency Heaven