Hardware Reference
In-Depth Information
as possible, organize in some sort of logical sequence and note any departures from standard
manufacturing procedures. In addition to the raw files, provide any other files that would be
useful for others such as STL files for use in 3-D printers of designs. Although the design files
may provide all the materials and subcomponents, it is generally a good idea to include a bill
of materials (BOM). Again, ideally the BOM should not only include the names of parts and
part count but also the vendors/suppliers with prices and urls. The BOM can be a spreadsheet
licate anywhere throughout the entire world by choosing standard, widely available parts in
your design whenever possible, and when you are not using a tool like a 3-D printer, which
enables others to make custom parts with ease. Obviously, make any firmware or software
available following the open-source principles and document/comment on it as well. For hard-
ware projects, you should also include pictures of the design and document with pictures at
appropriate times during its assembly or fabrication. This topic provides (hopefully clear) doc-
umentation to be used as an example for some of the OSHW builds, such as the environmental
chamber, in the next chapter. It is best to house instructions on an open wiki, so others may
add to it and improve them. It is also helpful to link to datasheets for the components and
parts of your hardware and to list the tools required to assemble it. For projects requiring spe-
cialized tools or equipment, also list sources and prices. Finally, share your designs in an ap-
propriate centralized and easily accessible online location such as GitHu
b
26
, Thingivers
e
27
,
Ap-
BOM, assembly instructions, code, movies of installation, etc.) should be version controlled
whenever possible and under an appropriate open license.
When using OSHW designs, some basic etiquete is necessary as well. Even if you are not
legally bound to do so, respect the wishes of the makers that came before you as determined
by the license that they chose. For example, CC-BY-SA demands that you share your derivat-
ives back with the community. Similarly, many makers will share the plans to build a device
with the world while also making it for sale. These entrepreneurs normally request that you
do not go into business against them simply making copies of their product. You are, of course,
free to make it for yourself and your lab, but if you want to create a business of of the idea,
make sure that you have made a substantial contribution to making the product better. All
ways provide atribution and thanks for the work of others that you use. It costs you nothing
to thank people in the acknowledgments of your papers, and it is a good way to encourage
additional open-source design work for scientific equipment if we all make it a habit of thank-
ing everyone that helped your research succeed. It is also a good idea to send a quick thank
you email to designers whose work you appreciate and, if it is appropriate, give back to them
through voluntary donations to continue development.
3.6 Continued IP Challenges
Current IP laws, which were ostensibly set up to encourage innovation, are coming increas-
ingly under harsh scrutiny. An overwhelming barrage of carefully executed studies and art-
icles have found weak or no evidence that IP increases innovation and, in fact, IP law often
hinders it [
23
]
. It is hard to imagine a truly advanced civilization arbitrarily holding back in-
dividuals to make use of the best possible combination of technologies, because someone else
thought of a similar “embodiment” earlier. We find it difficult to imagine, because it is obvious
that it is simply inefficient not to use the best technology available at the time to solve a prob-
lem. The following other inefficiencies elucidate the overall conclusion that IP (both copyright
and patents) are actively hampering innovation:
Search WWH ::
Custom Search