Open hardware, the idea that physical objects can carry the same freedoms as open-source software, needs a clear statement of rights to be more than a vibe. A charter of tenets gives makers, users, and manufacturers a shared language: what it means for hardware to be open, what rights attach to it, and what obligations follow. Without that shared language, every project defines openness for itself, and the term stretches until it means nothing. These are the core tenets such a charter must contain to be worth the paper it is printed on.
The right to understand
Open hardware must be documented well enough to be understood: schematics, board layouts, mechanical drawings, bills of materials, and firmware source, in formats that do not require proprietary tools to read. Documentation that exists but cannot be opened is not documentation. Prefer open formats and widely readable exports alongside any native design files, so the documentation outlives the tools that created it. This tenet is the foundation; every other right depends on the ability to comprehend the design.
Understanding includes the why, not just the what. Design rationale, known limitations, and safety-critical notes belong in the documentation. A schematic without notes on the high-voltage section is a trap; a mechanical drawing without tolerance callouts is a guess. The charter should demand documentation sufficient for a competent practitioner to reproduce, modify, and safely operate the hardware.
The right to repair and modify
Users must be free to repair their hardware and modify it for their needs, using the documentation above. This means designs should avoid gratuitous barriers: glued assemblies where screws would do, proprietary fasteners, fused or locked firmware, and parts chosen for unavailability. Where a barrier is genuinely required by safety or regulation, the charter should require it to be documented and justified, not silently imposed. The charter cannot ban every anti-repair practice in every context, but it can require that openness be genuine rather than nominal.
Modification rights include the right to share modifications. A charter that permits personal tinkering but forbids distributing improved designs is open hardware in name only. Share-alike provisions, requiring derivatives to remain open, protect the commons from enclosure.
The right to fabricate
Open hardware must be fabricable by its users: the design files must be complete enough to manufacture from, and licensed to permit manufacture, including commercial manufacture. A design that can be studied but not built is a museum piece. This tenet is what separates open hardware from look-but-don't-touch reference designs.
Fabrication rights carry a practical corollary: designs should prefer widely available parts and processes where possible, and document substitutions where not. A design requiring unobtainium components is open in license and closed in practice; the charter should encourage, if not require, attention to real-world buildability.
Attribution and the commons
Openness is not anonymity. The charter should require attribution: derivatives credit their sources, so the lineage of improvements is traceable and contributors receive recognition. Attribution sustains the commons by making contribution visible and rewarding; projects that strip attribution poison the well for everyone. A simple, standard way of giving credit, a line in the documentation naming the sources, is enough; the requirement is consistency, not ceremony.
The commons also needs defense. Patent pledges or defensive licensing provisions keep open designs from being captured by patent claims after release. A charter serious about permanence addresses the legal attack vectors, not just the licensing of the files.
Safety and responsibility
Rights imply responsibilities. The charter should state plainly that openness does not transfer liability: builders assume responsibility for their builds, especially where safety is concerned. It should require safety documentation for hazardous designs, high voltage, lasers, pressure, chemistry, while refusing to infantilize users. The maker tradition assumes competent adults; the charter should too, while giving them the information competence requires.
Finally, the charter should be a living document, amendable by its community, with its own governance stated openly. A charter imposed from above and never revised becomes dogma; one maintained by its practitioners stays relevant. Openness, applied to the charter itself, is the final tenet and the one that keeps the others honest.
A charter worth adopting promises understanding, repair, modification, fabrication, attribution, and safety, each stated plainly enough to judge real designs against. It should also name what it does not promise: no warranty, no fitness for any particular purpose, no shield from the consequences of a bad build. Write it down, argue about it, revise it, and then hold hardware to it. That is how a vibe becomes a standard.
Related Guides
- Attribution Licensing for Physical Open Hardware CAD: You release a CAD design for a tool, a jig, or a machine, and you want two things: for people to build on your work, and for your name to stay
- BOM Transparency Standards in Physical Hardware Sharing: Open hardware lives or dies on its bill of materials. A beautifully documented circuit board with a BOM that says "10k resistor" is not reproducible
- Defining Public Domain Boundaries in Open 3D Scans: 3D scanning has made it trivially easy to capture the physical world as digital meshes: museum artifacts, architectural details, machine parts
- Licensing Non-Functional Aesthetic CAD Enclosures: Maker CAD files occupy a strange legal middle ground. A bracket that holds a motor is a functional object; an enclosure shaped like a vintage radio