Maple Leaf Makers

JABBERWOCKY Github is alive now! github.com/kinematicdigit…

@clemmygames We're still figuring things out but finally got our trailer together this week for steam! youtube.com/watch?v=h7TuKI…

It's #TrailerTuesday! Show me your indie games! 👀

It's been so cold, and we've gotten so much snow this winter that we've had to abandon getting into the workshop until spring. To pass the time, we've been making a game about racing drones!

Let’s start turtle hunting! Tightening the community with turtles. 😎

@Mobile_Dom "isn't ready" impllies that's the goal, and I'm not sure it is. Klipper's advantage is in flexibility and configurability, but those aren't advantages in a consumer machine (not for the "normal consumer" anyway). it's the "X is the year of desktop linux" thing all over again.

i'mma go ahead and say it, Klipper isnt ready for normal consumer machines. a properly configured and tuned Marlin build, with a decent webUI (I'm looking at you ESP32 webUI, you're on blast) is more than enough. i thought printers were sold before they were finished before,

@M3NT8L Ooh, so close. should have been shredded iceberg lettuce. romaine on a burger is a crime. 8/10 would eat

Ketchup and Miracle Whip on one bun, BBQ sauce and mustard on the other half, onions, tomatoes, Famous Dave’s Devils Spit Pickles and lettuce.

This is how burgers are supposed to be made. Fight me @loyalmoses

@MandicReally Its frustrating because this isn't a grey area. it's spelled out clearly in the license. source code, or written offer for source needs to be included with the object code.

@MapleLeafMakers They aren't the only company that interprets "Must release Source Code" as, "Must release source code, eventually" sadly.

I make NO CLAIMS that Creality Print is just a reskin w/ some added features. What I can note is, on Github it is under a GPL-3 Open Source license, but the Source isn't available. If you d/l the Source file from the Github it's empty. They say it is coming yet this year. Sigh

@MandicReally Dot matrix nostalgia

Hitting just the right resonance to be AWFUL on the SV08.

@MattStultz legends!

This, all this, I could not be happier right now. Thank you Chicago for this unexpected treat.

@GregoireSaunier @Sovol3d the fusion file in the repo is not the native cad. open it up, there's no timeline, no sketches, no parameters. its just the final assembly. the work wasn't done there.

We don't have an SV-08, so I can't speak to the quality of the machine, but @Sovol3d did a bang-up job on the Github repository. This is how you do an open source printer without upsetting the community that made it. github.com/Sovol3d/SV08/

@GregoireSaunier @Sovol3d no doubt they'd be useful, if they existed. they don't. you have access to everything in that repository that the Voron Engineers do. when its time for a new rev, they'll be working with those same files. that's source by any definition that actually matters.

@GregoireSaunier @Sovol3d I guess I could take a photo of the whiteboard, but that lossy jpeg compression technically obfuscates the original work. at some point you call good enough good enough and get some work done.

@GregoireSaunier @Sovol3d By this logic, software is not OS if its not in version control - the history of changes is lost. If I write a one-off test, and don't commit it to vcs, my project can't be considered open source either? what about the notes on my whiteboard that were crucial to the design? ...

@GregoireSaunier @Sovol3d Not only do I do this regularly. sometimes I do it in the middle of a work session, because I've screwed up the timeline badly enough that nothing works correctly anymore? noob problem? probably, but it's how I work.

@GregoireSaunier @Sovol3d it may not be up to the standards of the OSHWA, Idk honestly, but it's how the project works, and how they want derivative works handled. that's what's important.

@GregoireSaunier @Sovol3d The sketches, parameters etc that you're referring to don't exist anymore, and likely never existed for more than a few hours on one persons machine.

@GregoireSaunier @Sovol3d The preferred format for making modifications to a Voron Design *is* STEP. Development isn't don't in a single software package, different engineers will work on different aspects of the design, and exchange STEP files as the lowest common denominator.

@GregoireSaunier @Sovol3d That document is about "best practices to encourage development of a vibrant community". it's not rules, those are listed on a different page here: oshwa.org/definition/ "... is available in the preferred format for making modifications to it."