Documentation Taxonomy - Refactoring: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
=Going Forward= | =Going Forward= | ||
*See graphical representation of documentation requirements - [https://docs.google.com/drawings/d/1HJa6yWnQvXVHd72nemBcIkB67-w5RZBMJQlIeyc87M4/edit] | *See graphical representation of documentation requirements - [https://docs.google.com/drawings/d/1HJa6yWnQvXVHd72nemBcIkB67-w5RZBMJQlIeyc87M4/edit] | ||
*Add Development to the Documentation - some of the Dashboard is related to development already | |||
Based on feedback: | Based on feedback: | ||
*Distinction should be made between Source Code (actual designs) and Metadata (dashboard) and Processes (fabrication) and Development Process. | *Distinction should be made between Source Code (actual designs) and Metadata (dashboard) and Processes (fabrication) and Development Process. | ||
Latest revision as of 21:00, 13 April 2013
Existing Best Practices & Taxonomies
- OSHWA Best Practices for Open Source Hardware by David Mellis - [1]
- OSE Taxonomy - OSHW Documentation Taxonomy
- Tom Igoe for Electronics - [2]
- OSHWA Guidelines by Nathan Seidle- [3]
- Software - [4]
- Repositories - [5]
- Formats, Protocols, Standards - [6]
Documentation Jam Suggestions
- David Mellis Suggestion
- Guidelines for participation - [7]
Going Forward
- See graphical representation of documentation requirements - [8]
- Add Development to the Documentation - some of the Dashboard is related to development already
Based on feedback:
- Distinction should be made between Source Code (actual designs) and Metadata (dashboard) and Processes (fabrication) and Development Process.