Is Duet still open source?
-
@zapta yes, I agree, I was talking about repairability part, not about OSH part
@bearer I don't think there is a way to provide BRD that will make creating printable gerbers impossible unless you remove all the internal layers (but that makes the BRD pretty useless for repair work).
-
@arhi said in Is Duet still open source?:
@zapta yes, I agree, I was talking about repairability part, not about OSH part
Yes, you are right, repairability and OSH have different goals and requirements. Reparability doesn't even require an open source license, but does require a schematic and parts list.
It was common for commercial electronic manufacturer to provide schematics and parts list. These days it's often discouraged, hence The Right To Repair movement.
BTW, this is my favorite repair document. The entire schematic is artfully condensed into a single page
http://colinoflynn.com/wp-content/uploads/2012/05/MX-500P-11.pdf
-
@zapta I have ton of old tektronix equipment (7106 is what I love the most)
that's documentation ppl should learn how to make these days, but back then the idea was to make repairable equipment, today I'd say the idea is completely opposite today 
so helping OSH projects like duet, smoothie... is really important -
@arhi, yes, I also appreciate the old repair manuals though I doubt if I would spend the time to read them in this era of TL;DR.
Duet uses a different model for reparability. Instead of spending time and money preparing in advance detailed repair documents, they use an 'on demand' approach where users can ask repair question whenever they arise.
I think this is a better model for small and fast moving company such as duet.
My 2c.
-
@zapta I find way duet doing thing great so far, no complaints
would not change a thing -
@zapta I agree on the OSHW side of things, mainly because Duet3D's website makes a big deal about being open source hardware, software, and an open community.
You can't have it both ways, either your hardware is opensource, and design files are released, or it's closed source, and they are not - but perhaps a schematic is provided for assisting with software dev.
For my project, I only need the schematic so my needs are covered, but I don't see that as falling under open source hardware.
Withholding the hardware design for whatever reason isn't in good faith for open source goals and claims. If the source is withheld, then the open source claim is just marketing fluff for people who think open source is good and want to support open source projects, even if they have no intention of using the source.
If you want sole distributorship/manufacturing rights (for whatever reason) and to not have anyone else sell your design or remixes thereof, don't release it as open source, or instead use a restrictive open license. Alternatively, make older versions open source, with the newest version proprietary commercial, but don't claim to be open source if you don't release the source files (which is the very definition of closed source.)
This is why I originally questioned whether the project was still open source.
-
FWIW, I believe Duet should either remove the entire "OPEN" green bar from their website, or, my preference, they should get a lot better about actually releasing things. And perhaps link from that green bar to the repository.
Right now, they clearly don't deserve to be representing that they are open.
-or-
Clearly state something like "hardware files will be released after first hardware shipments to customers" (and then, of course, do that).
-
@Danal said in Is Duet still open source?:
FWIW, I believe Duet should either remove the entire "OPEN" green bar from their website, or, my preference, they should get a lot better about actually releasing things. And perhaps link from that green bar to the repository.
Right now, they clearly don't deserve to be representing that they are open.
-or-
Clearly state something like "hardware files will be released after first hardware shipments to customers" (and then, of course, do that).
It’s amazing how many people are so demanding of projects (open and closed).
To the entire team of hardware and software devs building these products..Thanks, you are amazing and your work is awesome.
To those that are complaining, chill out. This stuff isn’t easy or free to design, build and test. If it is rushed you will just get buggy garbage that catches fire spontaneously.
-
@mwwhited said in Is Duet still open source?:
To those that are complaining, chill out. This stuff isn’t easy or free to design, build and test. If it is rushed you will just get buggy garbage that catches fire spontaneously.
and clones with the same issues with no incentive to fix it; duet have said they'll release it, just not when. idk if the license has any requirements to that regard
-
@bearer said in Is Duet still open source?:
... idk if the license has any requirements to that regard
I think that the concerns are about truthful representation to potential buyers. For example, the Duet's website currently states:
All the hardware designs are licensed under the CERN OHL 1.2. The design files are released on GitHub.
Not all buyers are long time members here and understand the nuances, timeline, and the dilemmas of the Duet team.
-
@zapta said in Is Duet still open source?:
Duet's website currently states:
I would think the simple explanation is the good old "it was true at the time"; and while I feel less strongly about it it would warrant adding an caveat to that statement or simply releasing the files.
Simply changing "are released" to "will be released" should satisfy the current and future debacles?
-
@mwwhited said in Is Duet still open source?:
@Danal said in Is Duet still open source?:
FWIW, I believe Duet should either remove the entire "OPEN" green bar from their website, or, my preference, they should get a lot better about actually releasing things. And perhaps link from that green bar to the repository.
Right now, they clearly don't deserve to be representing that they are open.
-or-
Clearly state something like "hardware files will be released after first hardware shipments to customers" (and then, of course, do that).
It’s amazing how many people are so demanding of projects (open and closed).
To the entire team of hardware and software devs building these products..Thanks, you are amazing and your work is awesome.
To those that are complaining, chill out. This stuff isn’t easy or free to design, build and test. If it is rushed you will just get buggy garbage that catches fire spontaneously.
Since you directly quoted me all I am really asking is:
"Do what you say; say what you do"
If THAT has somehow become to harsh to say out loud, or is "Demanding", or even worse if the principle itself is debatable... well, I don't even know how to finish that thought.
Search my posts. 99.9% or more are supportive of Duet, and I regularly recommend them to friends and on other forums. At the same time, "Do what you say, say what you do" with regard to being open is a statement that needs to be heard.
-
The design files are released on GitHub.
Can be interpreted in several ways. One way is of a generalized procedure.
The design files are (routinely) released on GitHub (at the time they are ready to be released).
It's not saying that all the design files are already there. It's saying that's where they are released.
-
@Danal said in Is Duet still open source?:
If THAT has somehow become to harsh to say out loud, or is "Demanding"
This is cognitive dissonance, and is not personal. We humans are not good with consolidating opposing views. In this case, "The Duet's people are awesome" (they are) vs. "The Duet website misrepresents the OSH situation" (it does). It creates stress.
-
Zapta said it very well. I have very positive opinion of Duet the company and the individuals in it. I also believe they can up the degree to which they align the green bar on the web site says with regard to 'open', align that better to actions.
Those two things may seem dissonant to others.
-
Appropos open source hardware, Prusa publishes this interactive BOM that is generated by this tool https://github.com/openscopeproject/InteractiveHtmlBom.
Duet team may find it useful for publishing, but I presume that everybody with access to kicad files can generate them as well.
-
@zapta hadn't seen that. It does seem geared towards assembly rather than repair/review but still I'd say anything that lowers the bar of accessibility is a good thing keeping multiple versions of KiCad on hand doesn't promote accessibility even if everyone in theory could do do it. Thanks for pointing it out, usefull to Duet or not.
