Licensing
HAPTIC.SKIN is multi-licensed: each kind of artifact is covered by the license best suited to it. By contributing, you agree your contribution is released under the corresponding license.
| What | Covers | License | File |
|---|---|---|---|
| Code | firmware (firmware-rust-v2/, firmware/), the haptic_skin Python package (client/), the Street View demo (demo/), scripts, CI | MIT | LICENSE |
| Documentation | everything under docs/, docs-site/, research/, README, the published site at docs.haptic.skin, text & images | CC BY-SA 4.0 | LICENSE-DOCS |
| Hardware | schematics, wiring diagrams, PCB/3D-printable parts and the BOM under hardware/ | CERN-OHL-P v2 | LICENSE-HARDWARE |
How to comply
- Reusing the code? Keep the MIT copyright notice. That’s it.
- Reusing the docs? Credit “HAPTIC.SKIN” with a link, and share adaptations under the same CC BY-SA 4.0.
- Building the hardware? CERN-OHL-P is permissive: keep the notices and the link to the source design.
Why three licenses
A wearable project produces three different things — software, written knowledge, and a physical design. Each ecosystem has a standard, well-understood license; using the right one for each maximizes reuse and removes ambiguity for anyone who wants to fork, manufacture, or cite the project.
SPDX
Where practical, source files carry an SPDX-License-Identifier header
(MIT, CC-BY-SA-4.0, or CERN-OHL-P-2.0) so tooling can detect the license
automatically.
Questions
Open a discussion
or see CONTRIBUTING.md.