Dev Team Involvement Email

From Open Source Ecology
Revision as of 15:58, 21 November 2018 by Marcin (talk | contribs) (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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


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)

so that the product fits 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 generating Part Libraries (https://wiki.opensourceecology.org/wiki/OSE_Part_Library) for the off-road electric vehicle. 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 vice versa.

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.

Thanks, Marcin

Retrieved from "https://wiki.opensourceecology.org/index.php?title=Dev_Team_Involvement_Email&oldid=182082"