Proposals/Generic Proposal Outline
Revision as of 06:22, 11 November 2009 by Sebastien Bailard (talk | contribs) (New page: =Identify Problem= =Describe available non-RepRap, non-GPL solutions which are not on the wiki, explain why they are unsuitable.= =Analyze domain, identify community resources if they exis...)
Contents
- 1 Identify Problem
- 2 Describe available non-RepRap, non-GPL solutions which are not on the wiki, explain why they are unsuitable.
- 3 Analyze domain, identify community resources if they exist and experts.
- 4 Make Simple Model Using RepRap
- 5 Try to identify domain expert with proven ability to get things dones, solicit advice.
- 6 Optional: Create Working Group of advisors. (Difficulty: No Talking-Shops
- 7 Describe Solution
- 8 Identify Domain Expert with proven ability to get things done: "Bob'
- 9 Secure Funding to donate RepRap: RepRap Research Foundation funds, PayPal, DARPA or Non-Profits etc.
- 10 Bob uses RepRap to design solution, demonstrates, puts on RepRap wiki under GPL.
- 11 Use RepRaps to make solution, deploy 1000 examples.
- 12 Agitprop: after deploying working examples, alert media, BoingBoing.
Identify Problem
Describe available non-RepRap, non-GPL solutions which are not on the wiki, explain why they are unsuitable.
Analyze domain, identify community resources if they exist and experts.
Make Simple Model Using RepRap
- This is a key step. If you walk into a prosthetic designer's workshop or a roboticist designer's workshop, you better have a physical simple non-working example, printed out with a RepRap. This will engage the designer's somatic sense, their professional instincts will kick in, and he or she will tell you why this won't work.
- Lay out large sheets of paper.
- Ask them to make a drawing explaining their criticism.
- Scan sheets of paper.
- Make new model.
- Repeat. Go back to
- This is a little sneaky, but will work. We will call it the Columbo method of getting started on a project.
