Collaborative Development Log: Difference between revisions
| Line 6: | Line 6: | ||
We can address the high level items of development of the first 4 days of the STEAM Camp - as shown at [[STEAM_Camp_Curriculum#Overview_Schedule_Narrative]] - by calling on the star DIYers and to join as partners with compensation for non-alienation. But the devil's in the details: OSE is an integrated technology set, so we need to translate the work of the stars to a language that fits with OSE. How to do that - is the last frontier of scaling open source product development for us. | We can address the high level items of development of the first 4 days of the STEAM Camp - as shown at [[STEAM_Camp_Curriculum#Overview_Schedule_Narrative]] - by calling on the star DIYers and to join as partners with compensation for non-alienation. But the devil's in the details: OSE is an integrated technology set, so we need to translate the work of the stars to a language that fits with OSE. How to do that - is the last frontier of scaling open source product development for us. | ||
The answer may lie in '''More than 6''' as above. | The answer may lie in '''More than 6''' as above, with synergy and urgency based on a proposed Camp date. | ||
Revision as of 21:45, 15 August 2019
Hint: Documenting collaborative development evolution at OSE
Thu Aug 15, 2019
To date, we've achieved Realtime Documentation, One Day Builds of Extreme Manufacturing, and have broken down designs according to Module-Based Design. Today we are pleased to announce the STEAM_Camp_Curriculum#Curriculum_Development_Model where we sextuple the STEAM Camp event in order to achieve accelerated product development. In summary - we pool the efforts of 6 rock-star DIY people to produce STEAM Camps. Can it be more than 6? 6 is a manageable number of people to manage for an event. It qualifies also as an 2 Pizza Rule. Yes - we keep scaling by adding additional locations, where we run the event all at the same time. We can have smaller players participate, possibly even cross-subsidized by the larger events.
We can address the high level items of development of the first 4 days of the STEAM Camp - as shown at STEAM_Camp_Curriculum#Overview_Schedule_Narrative - by calling on the star DIYers and to join as partners with compensation for non-alienation. But the devil's in the details: OSE is an integrated technology set, so we need to translate the work of the stars to a language that fits with OSE. How to do that - is the last frontier of scaling open source product development for us.
The answer may lie in More than 6 as above, with synergy and urgency based on a proposed Camp date.