OSE Standards: Difference between revisions
(Created page with "Recently, the project has been growing significantly, so standards definition is gaining in importance. I would like to propose the following strategy for replication/branding/i...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Recently, the project has been growing significantly, so standards definition is gaining in importance. | Recently, the project has been growing significantly, so standards definition is gaining in importance. | ||
I would like to propose the following strategy for replication/branding/identity: | I would like to propose the following strategy for replication/branding/identity for open hardware development: | ||
*Get advice from flossfoundations.org as the closest allied organization for identity/standards creation, | |||
*Integrate with GitHub as a hardware repository for commits, including developing web-3D viewing and 3D diffs for hardware designs | |||
*Evolve development standards to these required elements: | |||
1. [[SEBD]], Conceptual Drawings, Design Rationale, Fabrication Procedure, Fabrication Drawings, BOM, Sourcing, CAD, Exploded Part Diagram, CAM files, Toolchain Specifications, Instructional Video, Test Results - to GitHub repository. Official commits approved by Project Leaders and Project Director. Project Curator approves all Project Leaders | |||
2. Process: OSE Spec Review - scoring a particular approach, after clarifying score methodology applied to a particular product, Testing, Recruiting | |||
3. | |||
OSE License Strategy | |||
1. No restrictions on use | |||
2. OSE Label - only to those who follow OSE Specifications and share | |||
3. OSE trademarked - for OSE Label | |||
4. OSE License - not legal but effectively legal | |||
5. Free to produce commercially under own label, with attribution | |||
6. 5% tithe to produce commercially under OSE Label | |||
7. Fabricator certification required to produce under OSE Label | |||
8. Developers contribute to | |||
[[Category:Standards]] | |||
Revision as of 13:58, 15 June 2011
Recently, the project has been growing significantly, so standards definition is gaining in importance.
I would like to propose the following strategy for replication/branding/identity for open hardware development:
- Get advice from flossfoundations.org as the closest allied organization for identity/standards creation,
- Integrate with GitHub as a hardware repository for commits, including developing web-3D viewing and 3D diffs for hardware designs
- Evolve development standards to these required elements:
1. SEBD, Conceptual Drawings, Design Rationale, Fabrication Procedure, Fabrication Drawings, BOM, Sourcing, CAD, Exploded Part Diagram, CAM files, Toolchain Specifications, Instructional Video, Test Results - to GitHub repository. Official commits approved by Project Leaders and Project Director. Project Curator approves all Project Leaders 2. Process: OSE Spec Review - scoring a particular approach, after clarifying score methodology applied to a particular product, Testing, Recruiting 3.
OSE License Strategy 1. No restrictions on use 2. OSE Label - only to those who follow OSE Specifications and share 3. OSE trademarked - for OSE Label 4. OSE License - not legal but effectively legal 5. Free to produce commercially under own label, with attribution 6. 5% tithe to produce commercially under OSE Label 7. Fabricator certification required to produce under OSE Label 8. Developers contribute to