Open Licensing—Advanced Sharing - Open-Source Lab: How to Build Your Own Hardware and Reduce Research Costs - page 39

You may distribute modified documentation or products based on it, if you
license your modifications under the OHL;
include those modifications, following the requirements stated below;
atempt to send the modiied documentation by email to any of the developers who have
provided their email address. This is a good faith obligation—if the email fails, you need
do nothing more and may go on with your distribution.
If you create a design that you want to license under the OHL, you should do the following:
Include the OHL document in a file named LICENSE.TXT (or LICENSE.PDF) that is in-
cluded in the documentation package.
If the file format allows, include a notice like “Licensed under the TAPR OHL
( www.tapr.org/OHL )” in each documentation file. While not required, you should also
include this notice on printed circuit board artwork and the product itself; if space is lim-
ited, the notice can be shortened or abbreviated.
Include a copyright notice in each file and on printed circuit board artwork.
If you wish to be notified of modifications that others may make, include your email ad-
dress in a file named “CONTRIB.TXT” or something similar.
Any time the OHL requires you to make documentation available to others, you must in-
clude all the materials you received from the upstream licensors. In addition, if you have
modified the documentation, you should do the following:
You must identify the modifications in a text file (preferably named “CHANGES.TXT”)
that you include with the documentation. That file must also include a statement like
“These modifications are licensed under the TAPR OHL.”
You must include any new files you created, including any manufacturing files (such as
Gerber files) you create in the course of making products.
You must include both “before” and “after” versions of all files you modified
You may include files in proprietary formats, but you must also include open format ver-
sions (such as Gerber, ASCII, Postscript, or PDF) if your tools can create them.
For a full treatment and text of the TAPR OHL, see htp://www.tapr.org/ohl.html .
3.3.2 Chumby license
Another OSHW license was developed by Chumby HDK (2013) [ 16 ] . Simply stated:
Under this Agreement, as set out below, chumby grants you a license to use the chumby HDK to
hack your chumby Device. In return, we ask that you: keep the chumby Service on an even play-
ing field with any other service you want to point your chumby Device to; grant us a license re-
lated to your modifications and derivatives, when and if you make them available to others; and
agree to the other terms below.
3.3.3 Using open-source software licenses for open hardware
The last two subsections covered two good examples of OSHW licenses, neither are quite per-
fect, so what many open-source designers have done is simply substituting in an open-source
software license such as the GPL, CC, MIT, BSD and similar open licenses. These licenses
are reasonable for firmware or CAD drawings and thus Thingiverse (which has over 95,000
designs in May 2013 and is growing rapidly) uses the following licenses: CC licenses of the
CC-BY, CC-BY-SA, CC-BY-ND, CC-BY-NC, then BY-NC-SA a BY-NC-ND, CC-public domain
dedication, GNU-GPL, LGPL and BSD license.