Dev Team Involvement Email: Difference between revisions
(Created page with " the first thing is declaring an OSHWA compliant open hardware license. https://www.oshwa.org/definition/ The second step is to join our Dev team. https://wiki.opensource...") |
No edit summary |
||
| Line 17: | Line 17: | ||
https://wiki.opensourceecology.org/wiki/OSE_Specifications) | https://wiki.opensourceecology.org/wiki/OSE_Specifications) | ||
The main parts of OSE Spec are modularity: | |||
https://wiki.opensourceecology.org/wiki/Module_Based_Design | |||
and scalability, | |||
https://wiki.opensourceecology.org/wiki/Scalability | |||
which allows for a Construction Set Approach: | |||
https://wiki.opensourceecology.org/wiki/Construction_Sets | |||
The design you make must fit in the rest of the OSE product ecology: | |||
https://wiki.opensourceecology.org/wiki/Product_Ecologies | https://wiki.opensourceecology.org/wiki/Product_Ecologies | ||
The steps we take follow our general Development Template: | |||
https://wiki.opensourceecology.org/wiki/Development_Spreadsheet_Template | |||
The main perfomance indicator is how many reusable part libraries you generate for your project: | |||
https://wiki.opensourceecology.org/wiki/OSE_Part_Library | |||
This means CAD files of parts and assemblies in FreeCAD. For electronics - this means part libraries consisting of single or multiple components with wiring connections included. Both of these are intended to be merged or imported into larger assemblies. | |||
The goal for making this contribute to OSE is to keep in mind how your project would feed other OSE projects in terms of interchangeable components or common build techniques - and how OSE techniques and part libraries feed into your design. | |||
With this said - can you join the Dev Team for a 90 day period? The goal would be to generatete one library part per week, so we build up to a construction set. | With this said - can you join the Dev Team for a 90 day period? The goal would be to generatete one library part per week, so we build up to a construction set. With construction sets generated, we can create design guides for building variations of a product, and then we create FreeCAD macros and workbenches that can help others design with our construction set more effectively. | ||
Thanks, | Thanks, | ||
Marcin | Marcin | ||
Revision as of 16:12, 21 November 2018
the first thing is declaring an OSHWA compliant open hardware license.
https://www.oshwa.org/definition/
The second step is to join our Dev team.
https://wiki.opensourceecology.org/wiki/OSE_Developers
The Dev Team works on projects collaboratively, with a 10 hour per week requirement for a 90 day duration. You would have to work in FreeCAD:
(https://wiki.opensourceecology.org/wiki/FreeCAD_101)
and follow OSE Specifications
https://wiki.opensourceecology.org/wiki/OSE_Specifications)
The main parts of OSE Spec are modularity:
https://wiki.opensourceecology.org/wiki/Module_Based_Design
and scalability,
https://wiki.opensourceecology.org/wiki/Scalability
which allows for a Construction Set Approach:
https://wiki.opensourceecology.org/wiki/Construction_Sets
The design you make must fit in the rest of the OSE product ecology:
https://wiki.opensourceecology.org/wiki/Product_Ecologies
The steps we take follow our general Development Template:
https://wiki.opensourceecology.org/wiki/Development_Spreadsheet_Template
The main perfomance indicator is how many reusable part libraries you generate for your project:
https://wiki.opensourceecology.org/wiki/OSE_Part_Library
This means CAD files of parts and assemblies in FreeCAD. For electronics - this means part libraries consisting of single or multiple components with wiring connections included. Both of these are intended to be merged or imported into larger assemblies.
The goal for making this contribute to OSE is to keep in mind how your project would feed other OSE projects in terms of interchangeable components or common build techniques - and how OSE techniques and part libraries feed into your design.
With this said - can you join the Dev Team for a 90 day period? The goal would be to generatete one library part per week, so we build up to a construction set. With construction sets generated, we can create design guides for building variations of a product, and then we create FreeCAD macros and workbenches that can help others design with our construction set more effectively.
Thanks, Marcin