Close

A word on open source

A project log for Solder Ninja

A 40W Portable USB-Powered Soldering Iron for Makers and Professionals compatible with Weller RT Tips

Nicolas SchurandoNicolas Schurando 08/25/2019 at 10:183 Comments

I am aware that the following statement might upset some. And yet, open source is something that I truly do believe in. Working on this project, I have come to the interesting realization that there is a difference between design for manufacturing and design for open source that makes not every project the ideal candidate for open source.

Bear me with.

The way I see it, the interest of open source is maximized when the majority of people can actually make use of the published resources, with the least amount of extra steps as possible. It is not good enough to make a product, and say "oh, by the way here are my files",  I believe it is important to push things a step further by saying "and this is how you could do it, you, an individual".

And this is what a majority of projects that I see manage to do. But when, in the early stages, I asked myself how I could open source this project, I found myself confronted with a contradiction: the same technical choices that I was making to make this an appealing product where going to prevent people from making an immediate use of what I would share.

In particular, let's take the following three examples:

So, I decided to make the scope of this project twofold:

I fully intend to document both aspects. And I realize this means more work for me compared to just making one device. But I do believe this is the best way to go. Let me know what you think.

Discussions

aaron wrote 09/10/2019 at 01:10 point

The design scope of your project is for two separate use cases: one is to optimize for accessibility and one to optimize for cost vs function. The value of open source can be applied in both of those situations and is independent of assumed resource limitations. 

For example, professional EEs regularly use (and possibly contribute, while remaining anonymous to their employer ;) ) to OS hardware and firmware for real products. e.g. within many BTLE products you will find SoCs with relatively large communities of open source firmware support. Same could be said about many (canonical) circuit designs, see EE stack exchange.

  Are you sure? yes | no

Elliot Williams wrote 08/26/2019 at 14:10 point

I think about this a lot in the context of OS Hardware vs OS Software.  One of the biggest differences between them, IMO, is the ease of jumping into an OSS project to bugfix/contribute.  Software iterations are mostly free (download code, tweak, e-mail) but hardware iterations are expensive (get board made, source parts, assemble...).

Industry is driving the costs of getting a lot of this done, but real turnkey 'build me one of this device' service is still tricky.

But anything you can do to minimize the one-time costs of someone reproducing your project should help increase contributions and participation, so yeah: what you said.  :)  Good design, simple design, clear design.

  Are you sure? yes | no

de∫hipu wrote 08/25/2019 at 20:28 point

Hmm, I'm not sure that having as many people as possible follow blindly your instruction to replicate your product is really that good for an open source project.  Maybe this will sound elitist, but the people who don't understand the project and are unable to adapt it to their needs and available tools are not going to contribute back much, at least not in those areas where they need hand-holding. On the other hand, having the design files for the "production" device available allows for buying the product and *then* modifying it to better suit your needs, whether by attaching additional parts, designing accessories that can cooperate with it, or modifying the firmware for the device. This way the advances and improvements go back to that product version, instead of some "dumbed down" open source version.

  Are you sure? yes | no