# Open Source Hardware

## Summary


Many developments have contributed to the interest and growth of Open Source Hardware (OSHW): free and open source software (FOSS), 3D printing, crowdfunding, the maker movement, and Moore's Law reaching its limits.

While OSHW is commonly thought to include electronics and mechanical designs, OSHW today has a much broader reach including fashion, furniture, musical instruments, farm machinery, bio-engineering, and more. 

OSHW is not a standard, nor is there a single organization tasked with leading the OSHW movement. However, the Open Source Hardware Association (OSHWA) hopes to become the hub of this movement. There's also the Open Source Hardware Definition, which forms the basis for defining licenses for OSHW.

## Discussion

### What's the historical context for open source hardware?

In the ham radio community sharing knowledge was a common practice. Then in the 1970s, computers were shipped as kits with schematics included. This resulted in a hacking culture among computer enthusiasts. This culture was about tinkering, experimenting, sharing, and collaborating. 

FOSS that started in the 1980s contributed to OSHW, although open hardware need not be about either electronics or software. The web of the 1990s made it easier to share designs and best practices. By early 2010s, OSHW became more widely known due to the following reasons:

    + **3D Printing**: This brought down prototyping and production costs. It made design iterations easier and faster.
    + **Maker Movement**: Started in the mid-2000s, this established magazines, platforms, and fairs/exhibitions for people to come together, collaborate and co-create. Maker labs brought essential tools under roof, gave people affordable access to these tools, and thereby democratized production.
    + **Crowdfunding**: Those with good ideas could get upfront funding from potential users of the product without depending on traditional investment routes or financial institutions.
    + **Moore's Law**: With the Law reaching its limits, there's a need to create application-specific silicon and open designs can keep costs down.

### What aspects of hardware can be open sourced?

Open source hardware is about sharing the design files of hardware. This may include architecture/design drawings, schematics, PCB layout, bill of materials, HDL code, production/assembly instructions, and anything else that can enable others to replicate the hardware. 

There's no use claiming open design if the file format is proprietary and can be opened only with closed tools. Thus, the definition of open source can be expanded to include design file formats and/or access to tools or software to manipulate the files. Along with original proprietary files, intermediate files in open formats should be made open. Examples of file formats include PDFs of circuit schematics, Gerbers for circuit board layouts, and IGES or STL files for mechanical objects. OpenCAD, KiCAD and Eagle are examples of open tools. 

In the spirit of open source, users should be able to study the design, modify it for their specific needs, or distribute it. They also have the freedom to make and sell hardware based on the design. 


### Won't people misuse my designs and get rich at my expense?

Maybe but not necessarily. Firstly, just because you adopted OSHW licensing, doesn't mean you cannot also sell your products commercially and be successful in the process. Even if others have access to your design, there's cost and effort involved in sourcing, manufacturing, assembling, testing, distributing and providing technical support. If you establish your own brand value, provide a quality product at a good price, it's difficult for others to compete. 

The advantage of being open is that you benefit from community support and contributions. You establish an ecosystem around your product. While commercial vendors offer free reference designs, OSHW is a community effort. An open source design is likely to be more robust. It enables faster prototyping and it's continuously improved via multiple contributors. 

In conclusion, the case for keeping your hardware design proprietary is weaker than for software. Investment towards manufacturing and distribution is still a barrier to entry. Hardware can also be differentiated based on the firmware that need not necessarily be open.


### What business models are possible with OSHW?

Your design may be open and freely shared but you may charge for products made from open designs. Technical support, maintenance and upgrades can be part of your services model and customers will be willing to pay for them. 

You could create innovative services around open designs. You could then set up an online marketplace, aggregate and analyze data, etc. Openness becomes an incentive for customers because they have the freedom to tinker and customize. You can provide them training, resources, and additional services. 

Your product and its open design should be a market enabler. You can build an entire platform based on your open design. You can partner with others for peripherals that may or may not be open. In any case, a healthy ecosystem based on your open design will likely lead to better adoption and sales of your core products. This has been the case with Arduino and add-on boards called *shields*; and Raspberry Pi and add-on boards called *hats*.


### What's the recommended licensing for OSHW?

In the days before any OSHW licenses were defined, people simply used FOSS licenses for CAD drawings or firmware. To call something OSHW, it should be completely open without restrictions. Any license that prevents commercial use is not compatible with OSHW. 

"Creative" works are protected by copyright and "useful" or functional works are protected by patents. Thus, copyrights don't apply to hardware. If hardware is not patented, anyone can copy, modify or build upon the hardware. But copying or modifying hardware is lot easier if the design files are available. Thus, when we talk about open licensing or copyleft for hardware, we are referring to the design files and related documentation. 

In the world of software, there are plenty of licenses with different degrees of openness. Among the copyleft (share-alike or viral) licenses are GPL, CC BY-SA, CERN Open Hardware License (OHL) and TAPR Open Hardware License (OHL). Permissive licenses that allow for closed derivatives include FreeBSD, MIT, CC Attribution, and Solderpad Hardware License.  


### What are some examples of OSHW projects?

Well-known examples that use CC BY-SA include Arduino, mBed HDK, BeagleBoard, Particule (formerly Spark), and Tessel. mangOH is an example that uses Creative Commons Attribution license. 

Back in 2013, some successful OSHW projects included Arduino, Raspberry Pi, OpenROV (remote-operated underwater robot), DIY Drones, LittleBits, and Makerbot Replicator 2, Lasersaur, Robo3D, and Console II. 

Noteworthy projects of 2016 included the Global Village Construction Set (fabricate industrial machines), Open Source Beehives (bee home and sensor kits for tracking), AKER garden kits, WikiHouse (building system), FarmBot (CNC farming machine), OpenDesk (make furniture), OSVehicle, RepRap (3D printer), OpenKnit (digital knitting), Defense Distributed (3D firearms), APM:Copter, and Open Hand Project (robotic prosthetic hands).

Some OSHW boards include Arduino Due, Freescale Freedom, Microchip ChipKIT Uno32, and Beaglebone Black. Mouser website also lists dozens of other boards. Olimex offers OSHW boards including Linux-based OLinuXino boards. 

At chip level, RISC-V offers an open architecture from which customized SoCs can be designed. Other include lm32, mor1kx, and blocks from the OpenCores project. There's talk of even building an open source supercomputer. 


### What are some online resources for OSHW?

Design files, particularly for 3D printing, can be downloaded from Thingiverse, MyMiniFactory, Pinshape, and Cults. Thingiverse was launched in 2008 and it encourages folks to modify and re-upload designs to the site. Other sources are Hackster.io, Hackaday, Open Electronics and the Open Circuits Institute. 

For crowdfunding, try CrowdSupply, Kickstarter, Goteo and Tindie. Adafruit and SparkFun, while selling proprietary products, also promote OSHW. Olimex, Pandaboard.org, and SolderCore are suppliers of OSHW that are also available from Mouser. 

If you're open sourcing your own product, you may release the design files on your own website, on Thingiverse or similar sites. If you wish to make it open during the design and development stages, GitHub or its alternatives can be a place to share. Prusa Mendel and Mendel90 are just two examples of projects that have received lots of community contributions, what in the tech speak are called "pull requests". 

Element14 has an online community forum for discussions on OSHW.

## Milestones

Mar  
1975

At a garage in Menlo Park, California, some computer hobbyists have the first meeting of their newly formed **Homebrew Computer Club**. At such a meeting, Steve Wozniak gets inspired to build his own computer and share the blueprints with others. This leads to Apple-1. However, Steve Jobs convinces Wozniak to sell Apple-1 rather than share them freely, thus marking the birth of Apple in 1977. 

1997

Bruce Peters launches the **Open Hardware Certification Program** to allow vendors to self-certify their products as open. This implies availability of documentation so that anyone could write their own device drivers. 

1998

Mozilla releases source code of Netscape browser suite. Not wanting to call it free software (in the spirit of the Richard Stallman's Free Software Foundation), the term **Open Source** is coined. The **Open Source Initiative (OSI)** is also formed by Eric Raymond and Bruce Peters. At this point, it's all about software, not hardware.  

2003

Hernando Barragán creates **Wiring** so that designers and artists can approach electronics and programming more easily. This work leads to the creation of **Arduino** in 2005. 

2005

The birth of the modern maker movement starts with the launch of **Make: magazine**. In August, **Instructables** launches as an online platform to share step-by-step instructions to make something.  

2006

Dale Dougherty organizes the first **Maker Faire** for makers to showcase their creations. In October, as an open access DIY workshop, **TechShop** opens in Menlo Park, California. 

2010

At a open hardware workshop in March, some folks define the Open Source Hardware Definition 0.1. In July, v0.3 is made public. These are based on the definition of open source (from 1998). As on June 2019, Open Source Hardware (OSHW) Definition 1.0 is current. Open-Source Hardware Definition is not itself a license but OSHW licenses are written so as to be compatible with the definition. In September, the first **Open Hardware Summit** is organized, in New York City. Since then it has become an annual event. 

2011

The original gear logo of OSHW is selected via a community contest. A modified version of the winning logo is announced at the Open Hardware Summit. In July, the **CERN Open Hardware License (OHL)** is announced. To facilitate collaboration and sharing, CERN had already set up the Open Hardware Repository in January 2009.  

Feb  
2012

The first **Raspberry Pi Model B** is released as a credit-card-sized single-board computer (SBC) retailing at only $35. The idea is to make computers affordable, accessible and fun to a new generation of programmers.  Within two years, 2.5 million units are sold. By 2018, 22 million are sold worldwide. Also in 2012, the **Open Source Hardware Association (OSHWA)** is formed. Certification of OSHW is also done by the Association.

Jul  
2018

The U.S. DARPA announces funding of $1.5 billion over five years for what it calls the Electronic Resurgence Initiative (ERI). This includes the **POSH (Posh Open Source Hardware)** project meant to create a Linux-based platform for the design and verification of open source hardware IP blocks for SoCs. 

Mar  
2019

Esperanto, Google, SiFive, and Western Digital get together to form the **CHIPS Alliance**. The purpose is to foster open-source chip designs. The alliance is committed to RISC-V architecture but wishes to encourage more such open designs.