Developer Crash Course: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
This is about rapid on-boarding for full OSE-developer capacity to collaborate as a team of 1000 or more people. | This is about rapid on-boarding for full OSE-developer capacity to collaborate as a team of 1000 or more people. | ||
This is like the invention of email lists, Git, and code modularity that was behind [[The Success of Open Source]]. | This is like the invention of email lists, Git, and code modularity that was behind [[The Success of Open Source]] in the early 90s. | ||
We have email lists, version control through wiki or Git, modularity via [[Development Template]], [[50 GVCS Machines]], [[500 Modules]], and [[Module-Based Design]] - adding up to a [[Construction Set Approach. | |||
For Hardware, we need a Linux-scale development effort to succeed at creaating a new kernel for collaborative, open technology. This kernel is embodied in the 500 Modules, 50 GVCS Machines, and the OSE project in general. | |||
To get there, we need to onboard people readily to basic skills. Since this process is much more complex than software, we need a deeper understanding - of what open soruce physical product design entails. It requires a programming langauge - in hardware known as FreeCAD design - where CAD is the main language spoken in product development. We need the ability to prototype, documemnt, test, and develop enterprise to support the whole endeavor. In software, large companies began to fund Linux. In hardware, we expect bootstrap funding to be more applicable - simply because of the 200 years of inertia that has pervaded in hardware since the first industrial revolution. | |||
=8 Lessons= | =8 Lessons= | ||
Revision as of 23:18, 24 May 2020
Intro
This is about rapid on-boarding for full OSE-developer capacity to collaborate as a team of 1000 or more people.
This is like the invention of email lists, Git, and code modularity that was behind The Success of Open Source in the early 90s.
We have email lists, version control through wiki or Git, modularity via Development Template, 50 GVCS Machines, 500 Modules, and Module-Based Design - adding up to a [[Construction Set Approach.
For Hardware, we need a Linux-scale development effort to succeed at creaating a new kernel for collaborative, open technology. This kernel is embodied in the 500 Modules, 50 GVCS Machines, and the OSE project in general.
To get there, we need to onboard people readily to basic skills. Since this process is much more complex than software, we need a deeper understanding - of what open soruce physical product design entails. It requires a programming langauge - in hardware known as FreeCAD design - where CAD is the main language spoken in product development. We need the ability to prototype, documemnt, test, and develop enterprise to support the whole endeavor. In software, large companies began to fund Linux. In hardware, we expect bootstrap funding to be more applicable - simply because of the 200 years of inertia that has pervaded in hardware since the first industrial revolution.
8 Lessons
- Collaboration. Collaboration: what it is and isn't. OSE vision. Collaborative Literacy. Goals and scope (edit down the Collaborative Literacy Webinar). Relation to solving pressing world issues.
- FreeCAD and 3D Printing. Designing as a crowd. FreeCAD and part libraries, workbenches for 50 Tools. 500 Modules.
- Wiki - what is is. How to do a template. Dev Template. Work Log. Recent Changes. Hypertext. Modularity. Module-Based Design - Development Process. Embedding Collaborative Docs and other assets - live, editable things. Contributor Template. Dev Template. Enterprise Template.
- Enterprise -
- Product Ecologies - Recursion. Bootstrapping. Progress of tech. 500 Modules
- [[500 Modules - Summary of All Mechanisms.
- Microfactory - from desktop, the garage, or hackerspace to 4000 square foot module. Production Processes. and