Open source hardware provides several benefits: keeping prices low and fair, enabling customization and integration, and sharing knowledge through community contributions. The Open Source Hardware Association maintains a directory of certified open source hardware projects and provides unique IDs and logos to ensure projects meet the community definition. Using proprietary software for open hardware design is discouraged as it limits community participation. Key ingredients of open source hardware include hardware designs, free and open source software like KiCad for design, and documentation in formats like Markdown. Popular version control systems like Git and services like GitHub support open hardware development. The document discusses one maker's experience designing their first open source hardware project from scratch using KiCad.

1. Open Hardware Makers

2. What are the benefits of open source hardware?
Open source hardware is good for:
 Giving confidence that the design will be available if the original manufacturer
stops production or stops selling in certain regions
 Keeping the prices low and fair
 Repairing and maintaining hardware
 Enabling customizations and integration in 3rd party products
 Sharing knowledge, educating students and getting feedback and contributions
from the community

3. Open Source Hardware Certification
Open Source Hardware Association (OSHWA):
 Maintains Certified Projects Directory
 Ensures that the definition of “open source hardware” used by a specific project
matches the community definition of open source hardware
 Provides an unique ID for certified hardware based on the country code and a
number, for example: BG000007
 Provides an unique logo for the certified ID
 https://certification.oshwa.org/

4. Does it make sense to use proprietary software for open hardware?
 Is it worth designing open source hardware with expensive proprietary software
tools?
 Can you build a sustainable community if your contributors have to pay gazillions
for software licenses to modify and contribute back to your open source hardware
project?

5. Does it make sense to use proprietary software of open hardware?
NO

6. Ingredients of an Open Source Device
Hardware
Software Documentation

7. Free and Open Source Design Automation (EDA)
 KiCAD
 Fritzing
 gEDA
 Other tools (Electric, FreePCB, KTechLab, Magic, Ngspice, Oregano, Quite
Universal Circuit Simulator, XCircuit)

8. Made with KiCad: Olimex A64-OLinuXino

9.  OpenSCAD
 QCAD
 FreeCAD
 LibreCAD
 SolveSpace
 Blender
Free and Open Source Computer-Aided Design (CAD)

10.  Markdown (.md), LaTeX, HTML, etc.
 MediaWiki with wiki markup, DokuWiki, Wikifactory, readthedocs.org, etc
 Pandoc - convert files from one markup format into another, including PDF
 DIN SPEC 3105 - a specification produced by Deutsches Institute fur Normung
defining the standards for the documentation of open source hardware
Documentations

11. Open source systems:
 Git
 Mercurial
 Subversion (SVN)
Version Control
Popular services:
 GitHub
 GitLab
 BitBucker
 SourceForge

12. My First Own KiCad Project from Scratch
 It all started with an add-on board for Raspberry Pi
 Thanks to friends for helping me to get started with KiCad
 For details have a look at FOSDEM 2017: Making Your Own Open Source Raspberry Pi HAT
https://archive.fosdem.org/2017/schedule/event/diy_pi_hat/

13. It Becomes Easy After Getting Used to KiCad and Open
Source Hardware

14. ANAVI Info uHAT
https://www.crowdsupply.com/anavi-technology/anavi-info-uhat

15. Thank you!
Useful links:
 https://anavi.technology/
 https://www.oshwa.org/
 https://certification.oshwa.org/process.html
 https://github.com/AnaviTechnology/
 https://opennext.eu/
 https://www.crowdsupply.com/
 https://www.tindie.com/
 https://lectronz.com/