Mach 30 launched Open Design Engine (ODE) in 2012. Since then we have run our own OSHW projects on ODE, observed other groups host OSHW projects on ODE and other sites, and held numerous conversations on and offline about the nature of hosting OSHW projects. Our conclusion after all these years and experience is the same one we held back in 2012: the OSHW community is still searching for a project hosting solution that meets the needs of hardware projects (where documentation is part of the source code).
What has changed is our approach to addressing OSHW project hosting. This time we are starting with the development of a tool independent methodology for developing and sharing OSHW, the Distributed OSHW Framework (DOF). What do we mean by methodology?
The Distributed OSHW Framework will be a systematic approach identifying:
-
What needs to be shared
-
How it should be shared
-
The relationships between the various kinds of shared content
Note how developing a methodology is different from identifying best practices, covering case studies, and creating definitions. A methodology is something one follows; it is a fully defined process. And by targeting tool independence, we can aim for developing a solution that will stand the test of time, just as version control methods have lasted through cvs, svn, and now git.
The Distributed OSHW Framework (DOF) is built upon 4 pillars. All design decisions for DOF are ultimately derived from one or more of these pillars.
OSHW projects should be developed and shared in accordance to the OSHW Definition.
OSHW projects should be developed and shared in accordance to the OSHW Certification process.
Open Source Hardware should be like Open Source Software to the greatest degree possible (e.g. sharing, development, licensing).
The source of an OSHW project is its: Bill of Materials Data (list of components and counts covering all parts which must be purchased to build the project), Assembly Instructions (complete list of instructions to build the project from its purchased parts), and Supporting Documentation (e.g. design files, schematics, operating instructions)
The methodology is being modeled in a series of YAML files under the architecture folder. A script is then used to generate this readme and the DOF architecture document (located in the dist folder). See the docs folder for material on the format of the architecture YAML files.
Please feel free to join the conversation by posting questions/comments as issues in the DOF repository.
-
Open Design Engine - legacy OSHW project hosting portal built on Redmine
-
Sliderule - Reference implementation of DOF, being developed in stages
-
Sliderule CLI - Initial component of Sliderule, a command line interface implementation of DOF developed by 7BIndustries
-
-
Howstr - A project by Matthew Maier to capture how to capture, share, and discover tangible projects