-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSCAD? #21
Comments
Hi @infosisio , reason why we are no longer using OpenSCAD is that we found better solution. |
@JohnnyDeer I don't know what solution you found but you are no longer sharing them in a format the community can build upon. |
@infosisio we are still sharing all data in format which is usable to build upon. |
@JohnnyDeer That is not true, STEP is an archival format that doesn't give parametric control. The only thing it is useful for is to act as reference for reverse engineering a part, in order to be able to make changes and improvements. Please reconsider this. |
From the headers in the released STEP files it appears they were generated using Autodesk Inventor. Example from MINI-x-end.stp:
I believe this would mean that the STEP files are indeed not the source files, and that this would make the printer not open-source as claimed. This also severely hampers the speed and accuracy of community improvements. Even if you Prusa Research believes that STEP files are source files (please make clear if this is the case), I think it can be agreed that the practice is against the community accepted definition of the term and how it is used to imply an ecosystem encouraging communal improvement and iteration. |
Sadly this has been happening more often that a lot of us would like. They have been dragging their feet to release source files or just setting their own timelines and borderline redefining the licenses used to release their products. They have actually made changes to some of the “Open Source” products and not update the git files until been pressed on. @JohnnyDeer it is not about releasing “usable files to build upon”, it is about releasing the actual source files for products that are touted as Open Source and come with a big Open Source logo stamped on the box. |
I will also like an explanation, hopefully this is not a case of #openwashing. |
It's a bit like releasing a binary Java file and calling it open source because you can decompile it. It's nice that Prusa is releasing the step file, but calling it an open source printer at the same time is appalling.
|
Let me clarify and correct some statements here from our side. |
Thank you @josefprusa for agreeing that native source files are important for the community to develop and improve in an open and efficient manner. I'm hoping this will also carry over to the mk3s parts that also lack source files at the moment. In the future you might want to consider a different license on release and make it clear what your release schedule and intents are from the beginning. "Surprises" like the appendix being released post-preorder and the lack of files and firmware tools aren't good for the community or how your brand is seen by the community. Not too long ago you were an outstanding example of what was good in the open community and these recent evens have begun to tarnish that. I don't think it's too late to turn that around though! TLDR: The community is smart enough to understand if you just tell them what you plan outright. Just be open about it and stay faithful to the true intent of the open-source practice if you really want to be called open-source. Don't just do the minimum to keep the open tag on your products as it just makes you look untrustworthy. I'm excited and hopeful for the future! |
Prusa can keep the Autodesk Inventor files - as long as they release a version in openscad (or freecad for that matter) that the community can open and modify at source level, not at archive level (like Step or STL). |
Is there a particular reason that this wasn't designed in OpenSCAD as per the usual tradition?
Thanks.
The text was updated successfully, but these errors were encountered: