1. Core Capabilities
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
Children
- 0. Unidentified
- 1. OSHW Definition
- 2. OSHW Certification
- 3. OSHW Should Be like OSS
- 4. OSHW Development Should Leverage Modern Software Development Techniques
Backlinks
- 2. There Must Be a Better Way
- OSHW Project Management User Stories
- 2. Pillars
- User Story
- Developer Associate a Figure with Elements
- Developer Associate an Asset with Elements
- Developer Attach a Citation
- Developer Automate Certification
- Developer Decompose Project
- Developer Ensure Unique Project Element Names
- Developer Organize Projects
- Developer Reference Elements from an Element
- Developer Reuse Elements of External Projects
- Developer Reuse Elements of This Project
- Developer Verify Project Data
- User Annotate an OSHW Project
- User Build an OSHW Project with Alternative Components
- User Build an OSHW Project
- User Comment on Elements
- User Create Agile Decision Record
- User Fork an OSHW Project