Hardware Reference
In-Depth Information
A.
Open Source Hardware Checklist
This checklist is made up from key points of the Open Source Hardware Definition and Best
Practices. It is meant to serve as a quick reference guide to ensure that your project is prop-
erly labeled as open source hardware.
1
Does your hardware comply with the Open Source Hardware Definition (
ht-
Have you allowed anyone to study, modify, distribute, make, and sell the hardware?
If you used a Creative Commons license for your source files (documentation), did
you chose options compatible with the definition? Noncommercial and no derivat-
ives licenses are not open source.
Did you put the OSHW logo on your hardware so people can easily identify it as
open source hardware? (Strongly recommended)
Do all company logos on the hardware belong to you? Do not infringe on trade-
marks!
Are your source files in an easily attainable format?
Are the source files publicly available online?
Are your source files easy to find—for example, are they linked to and from the
product page?
Have you documented your project in such a way that people will be able to copy it?
Is your documentation free of charge?
Have you included images in your documentation? (Strongly recommended)
Are you emotionally prepared to allow your project to be copied?
If not all parts/versions are open, have you clearly specified which portions of the
design are being released as open source hardware and which are not?
If you answered yes to all of these questions, your project is considered open source
hardware!
