OSE Collaboration Protocol

Overview

OSE engages in large-scale product development. To date, this development was never large scale, peaking at only ~50 during some of OSE's Extreme Builds. But the goal is to coordinate ~2000 developers effectively in concurrent tasks consistent with a Second Toyota Paradox style of development.

edit

Basic Questions

• How do you assure widespread interest? Work on important problems, such as solving for renewable energy, planting trees, or ending poverty. The GVCS qualifies as an important problem. However, the second side of this is that the solutions to these are simple and not exotic, requiring embrace of complexity - so it's often easier to do things like 'saving puppies' than 'transforming the world'.
• How to assure widespread participation? Host incentive challenges, hackathons, or other Apollo-style projects. The OSE Incentive Challenge qualifies.

Links

• Collaborative Literacy
• See Large-Scale Collaborative Design for basic requirements
• OSE Collaboration Ecology
• Time Binding
• Collaborative Waste
• Economic Time Binding
• Collaborative Development Log
• Difference Between Crowd Sourced and Collaborative
• Difference Between Collaborative and Open Source
• Fake Open Source
• Collaboration vs Competition
• OSE Collaboration Mechanics‎‎‎‎
• OSE Collaboration Architecture
• Academic Collaborators‎‎‎‎
• Collaboration Vision‎‎
• Psychology of Non-Collaboration
• OSE Clubs Collaboration
• Book - How to Design an Incentive Challenge to Get Collaborative Results
• Collaboration Architecture
  • Design Sprint Collaboration Architecture
• Collaborator Map
• OSE Collaboration Best Practice
• Independent Collaborator Guidelines
• Does Society Collaborate?
• Realtime Cloud Collaboration
• Collaborative Product Development
• Collaborative Video Editing
• OSE_Collaborators - bug - no edit bar? How to fix?
• OSE_Open_Collaboration_Guidelines
• Collaboration Ecology
• Collabora - is this the most promising open version of Google Docs?