2. There Must Be a Better Way
1. Core Capabilities
From 1. Core Capabilities
Go to text →
These are the core needs of the OSHW community when sharing, communicating, and collaborating on OSHW projects
1. OSHW Definition
From 1. OSHW Definition
Go to text →
OSHW projects should be developed and shared in accordance to the OSHW Definition.1
2. OSHW Certification
From 2. OSHW Certification
Go to text →
OSHW projects should be developed and shared in accordance to the OSHW Certification process.1
3. OSHW Should Be like OSS
From 3. OSHW Should Be like OSS
Go to text →
OSHW should be like Open Source Software (OSS) to the greatest degree possible (e.g. sharing, development, licensing).
4. OSHW Development Should Leverage Modern Software Development Techniques
From 4. OSHW Development Should Leverage Modern Software Development Techniques
Go to text →
OSHW development should leverage modern software development techniques to improve the OSHW developer experience.
examples
- package management
- DevOps (e.g., DevSecOps, DocOps)
- mono-repos
- design patterns (e.g., model-view-controller)
- semantic versioning
2. Pillars
From 2. Pillars
Go to text →
Classes of data that need to be captured 1. Core Capabilities
1. BOM Data
From 1. BOM Data
Go to text →
Bill of Materials (BOM) data: list of components and counts covering all parts and tools which must be procured to build the project
2. Instructions
From 2. Instructions
Go to text →
- Assembly Instructions: complete list of instructions to build the project from its procured parts
- Operating Instructions: complete list of instructions to use the project safely and effectively
3. Supporting Data
From 3. Supporting Data
Go to text →
e.g. design files,
- CAD models (e.g., Mechanical CAD files, PCB Gerbers files)
- Specifications (e.g., operating temperature range)
- Interface definitions (e.g., board pinout)
- Schematics (e.g., Circuit boards)
Children
Backlinks