Hello everyone, I am a graduate student developing a free and open source hardware/software 3D printer designed to use friction stir surfacing and high shear extrusion machining to print high quality metals, plastics and ceramics on the home desktop. We are still in early days, but we are having some success in printing aluminum and copper, onto themselves and onto various ceramics, as well as organics like FR4.
Excited to watch this project grow, thanks for sharing!
@mtlynn I see your GitHub repository uses the GNU AGPLv3 license, cool! It’s one of my favorite licenses.
That said, for the hardware components may I suggest using a hardware-specific open source license? For example, the CERN OHL-S-2.0 is the equivalent of the GPL but for hardware designs. Here is an example GitHub project using it. You can still use the AGPLv3 for all software/firmware components.
For some background, check out this thread on the efforts of the GOSH community that successfully made the CERN OHLv2 family of open source hardware licenses available on GitHub!
If you would like to feature it, I would be honored.
I would also refer you to the recent literature on the technique.
I did not invent it, just scaled it down.
Regarding gallium and indium mixtures, I will keep this in mind. I have actually been trying softer alloys like Zamak, and lead tin solders as well, as gallium/indium are quite expensive.
The melting point of the alloy is not the most critical element, its really how its viscosity evolves with shear and temperatures. In general, the more machinable the material, the more extrudable it is for rotoforge.
I had not previously, thoroughly considered the hardware licenses that were actually available.
I will act on this in short order. Thanks for the tip!
Splendid! Some practical steps for doing this would include stating which licenses apply to which components in the README file, and using the REUSE and Open Know-How standards to make your hardware design information machine readable and more easily reproducible by others.
cool project! I just wanted to chime in and throw yet another OSH resource at you
Me, @jarancio and @vektor have developed a training program on best practices for open hardware development. This has been widely reviewed by this community and addresses a lot of interesting aspects on OSH (some of which @hpy has pointed out here, like licensing, findability, etc), including suggestions and materials to prepare your project for community engagement and support…