OSE Standards: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
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. | ||
OSE Founder proposes the following strategy for replication/branding/identity for open hardware development under the OSE label: | |||
*Develop standards for the meaning of Open Source Ecology operations | |||
*Get advice from flossfoundations.org as the closest allied organization for identity/standards creation, | *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 | *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: | *Evolve development standards to these required elements: | ||
**Technical development: [[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 | |||
**Development Process Streamlining: Recruiting OSE Spec Review - scoring a particular approach, after clarifying score methodology (based on [[OSE Specifications]], applied to a particular product; Testing; Iteration | |||
*Define the OSE License for physical products | |||
OSE License Strategy | =Standards for OSE= | ||
What does an OSE Facility, Operation, Affiliate, Developer, User mean? | |||
==OSE Brand Identity== | |||
OSE follows these goals: | |||
#Development of the GVCS, a minimal yet robust infrastructure platform for | |||
=OSE License Strategy= | |||
1. No restrictions on use | 1. No restrictions on use | ||
2. OSE Label - only to those who follow OSE Specifications and share | 2. OSE Label - only to those who follow OSE Specifications and share | ||
Revision as of 14:04, 15 June 2011
Recently, the project has been growing significantly, so standards definition is gaining in importance.
OSE Founder proposes the following strategy for replication/branding/identity for open hardware development under the OSE label:
- Develop standards for the meaning of Open Source Ecology operations
- 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:
- Technical development: 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
- Development Process Streamlining: Recruiting OSE Spec Review - scoring a particular approach, after clarifying score methodology (based on OSE Specifications, applied to a particular product; Testing; Iteration
- Define the OSE License for physical products
Standards for OSE
What does an OSE Facility, Operation, Affiliate, Developer, User mean?
OSE Brand Identity
OSE follows these goals:
- Development of the GVCS, a minimal yet robust infrastructure platform for
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