OSE Strategy Notes

Summary of Points

• Develop OSE Linux, via quick MVP test-driven prototype, and iterate.
• Build relationships with key community leaders to develop the key OSE tools, from CAD to marketing, etc. This is because we are overtly building upon prior open knowledge.
• Engage a high performing team of part time professionals (minimum 4 hours per week), with strict hiring and firing procedures, as in the Rare Genomics Institute model.

Rationale

• Open products must get only to a minimum level of effectiveness before their economic cost advantage becomes a compelling motive for adoption and further development. This starts with early adopters.
• Unfunded development can go onluly so far, as economic pressure is a major competitor with voluntary contributors.
• However, the revolution cannot be funded, typically because those who have gained by the system are too engrained in it, and it is difficult for them to see outside
• Complex, integrated enterprises are primary targets. In the more radical sense, autonomous communities are most favorable places for deployment. However, since there is a large entry barrier to creating an integrated package, there are limits to this strategy. Thus, we start small.
• Starting small may well.involve the mass creation of right livelihood.
• The pen is mightier than the sword - for those who have mastered the sword. This means that organizing social + social capital can be leveraged honestly only after one has shown a track record of getting their hands dirty and gained a deep understanding of the issue.

Points to Consider

• Fund close collaborators via the Xtreme Manufacturing Workshop Model.
• Build relationships with key allies while educating about distributive enterprise, regenerative development, and open source culture.

Other

• Write Grants from TED Fellows list of grants. Structure first with compliance, then allocate a grant writer to this.
• Evaluate Comparison of Urban vs Rural OSE Development Sites