OSE Naming Convention: Difference between revisions
(Created page with "The OSE naming convention involves using the official machine name - see Machine Naming Convention. For other projects, use a descriptive name, and use the Dashboard....") |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The OSE naming convention involves using the official machine name - see [[Machine Naming Convention]]. For other projects, use a descriptive name, and use the [[Dashboard]]. | The OSE naming convention involves using the official machine name - see [[Machine Naming Convention]]. Remember that at the end of the day, we are solving for 50 machines of the [[GVCS]] - and final designs are at the [[OSE Part Library]], which needs to be curated by maintainers of each project. | ||
But more broadly - one needs to also consider [[Taxonomy]], [[Genealogies]], and [[Versioning]] - to track product evolution and other naming detail. | |||
For other projects, use a descriptive name, and use the [[Dashboard]]. | |||
This video explains how to name the granular development assets that are involved in the complete documentation of a given project: | This video explains how to name the granular development assets that are involved in the complete documentation of a given project: | ||
| Line 6: | Line 10: | ||
The video explains how the specific development items are named when using the Development Template - '''[[Development_Spreadsheet_Template#Simple_Template]]''' | The video explains how the specific development items are named when using the Development Template - '''[[Development_Spreadsheet_Template#Simple_Template]]''' | ||
=Links= | |||
*''[[Taxonomy]]''' - for updates | |||
[[Category:Collaboration Architecture]] | |||
Latest revision as of 03:23, 3 February 2022
The OSE naming convention involves using the official machine name - see Machine Naming Convention. Remember that at the end of the day, we are solving for 50 machines of the GVCS - and final designs are at the OSE Part Library, which needs to be curated by maintainers of each project.
But more broadly - one needs to also consider Taxonomy, Genealogies, and Versioning - to track product evolution and other naming detail.
For other projects, use a descriptive name, and use the Dashboard.
This video explains how to name the granular development assets that are involved in the complete documentation of a given project:
The video explains how the specific development items are named when using the Development Template - Development_Spreadsheet_Template#Simple_Template
Links
- Taxonomy' - for updates