Immersion Program Goals: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
*Continuous improvement, using simple tools: wiki, templates, and modular embedding - and eventually semantic wiki - after templates are maxed out. | *Continuous improvement, using simple tools: wiki, templates, and modular embedding - and eventually semantic wiki - after templates are maxed out. | ||
*Modular embedding revolves around picking the best software | *Modular embedding revolves around picking the best software | ||
*Peerless - like [[Serverless]] - but with peers. That means peers provide the synching infrastructure, as clients and servers. This is the ultimate distributed way to do a small state republic. | *Peerless infrastructure for wiki and apps - like [[Serverless]] - but with peers. That means peers provide the synching infrastructure, as clients and servers. This is the ultimate distributed way to do a small state republic. | ||
=Links= | =Links= | ||
*[[Immersion Training]] | *[[Immersion Training]] | ||
Revision as of 13:29, 12 March 2018
Goals
- To create a world-class open source product development process, all trainees of the OSE immersion program are to be involved in collaboration architecture development. Thus, the goal of any 1 month+ long training program is to include training in collaboration ecology, collaboration task breakdown - with clear infrastructure for contributing to the development process.
- Continuous improvement, using simple tools: wiki, templates, and modular embedding - and eventually semantic wiki - after templates are maxed out.
- Modular embedding revolves around picking the best software
- Peerless infrastructure for wiki and apps - like Serverless - but with peers. That means peers provide the synching infrastructure, as clients and servers. This is the ultimate distributed way to do a small state republic.