The Real Open Source Hardware Revolution

I recently wrote about the latest iteration of the Open Source Hardware Definition, which provides a framework for crafting open hardware licences. It's a necessary and important step on the road towards creating a vibrant open source hardware movement. But the kind of open hardware that is commonly being made today – things like the hugely-popular Arduino - is only the beginning.

On Open Enterprise blog.

Open Source's (Not-so-)Secret Sauce: Modularity

Why does open source succeed? Apart, that is, from the fact that it is created by huge numbers of amazingly clever and generous people? Or, put another way, what is a key ingredient that must be present for the open source methodology to be applicable to other spheres?

Modularity.

If the stuff to hand isn't modular, you can't really share, because your stuff isn't compatible with other people's stuff. If it isn't modular, you can't share out tasks and scale. If you can't share out tasks, you can't have people working independently, at their own pace and in their own way, which means the project isn't really open. If it isn't modular, you can't swap in some new elements while leaving everything else untouched, which means no "release early, release often", no experimentation, no rapid evolution. Modularity is indispensable.

I think that's why open source hardware has singularly failed to take off. It's difficult to make bunches of atoms modular in the way that bunches of bits are (at least until we have general 3D printers, in which case we're done...)

But could there be a way of introducing that modularity at a higher level so as to enjoy the benefits outlined above? I do believe there is, and with hindsight, it was pretty obvious (er, so why didn't I think of it?). It's called OpenStructures:

The OS (OpenStructures) project explores the possibility of a modular construction model where everyone designs for everyone on the basis of one shared geometrical grid. It initiates a kind of collaborative Meccano to which everybody can contribute parts, components and structures.

As you can see, the clever people behind this project have the magic word "modular" in there. Specifically, they have devised a very simple grid system that ensures that things fit together, even when they're made by different people at different times and for different purposes. Significantly, the grid is based on binary multiples and subdivisions:

If you choose to apply the OS grid for the dimensions of a part, at least one of the measurements of this part (length, wideness and thickness or height) should correspond to either 0,125cm / 0,25cm / 0,5cm / 1cm / 2cm and multiples of 2cm in order to be compatible with other parts. (see part examples)

What's really impressive about this project is not just this insight into the modularity of elements, but the completeness of the vision that results. For example, there is an explicit hierarchy of elements, starting from OS Parts, which combine to form OS Components, from which are made OS Structures, and finally OS Superstructures.

It's an amazing vision, and I think it could have a major impact on the world of open source hardware, at least of this particular construction-set type. If you want to see some of the exciting objects that have already been created, don't miss the fab photos on the project's blog. (Via @opensourcerer.)

Follow me @glynmoody on Twitter or identi.ca.

Open Source Hardware: A Meme That Won't Die

Open source hardware is nice in theory, but currently self-contradictory in practice. The key thing about open source is that it's generated by code, and the code can be hacked. The same is true of open content, open data, open genomics and the rest. Until they come out with better fabbers whose underlying generative code is both available and hackable, we're doomed to pale imitations of true open source hardware.

In the meantime, Bug Labs has come up with a fun waystation on the road to that end goal:

BUG is a collection of easy-to-use, open source hardware modules, each capable of producing one or more Web services. These modules snap together physically and the services connect together logically to enable users to easily build, program and share innovative devices and applications. With BUG, we don't define the final products - you do.

Note that one key open source feature that you can reproduce in hardware is modularity, and indeed it's key to Bug's approach. And in a real sense, Bug has its heart in the right place:

BUGbase is the foundation of your BUG device. It's a fully programmable and "hackable" Linux computer, equipped with a fast CPU, 128MB RAM, built-in WiFi, rechargeable battery, USB, Ethernet, and a small LCD with button controls.

Open Source Hardware

One of the central beliefs at the heart of this blog is that open source ideas can be applied in many other, quite different, fields. But even though the concept of "open source hardware" is bandied around quite freely, it's not entirely clear how hardware can be open.

Try this for an explanation - with pix - which sensibly uses a layer model. (Via Slashdot.)