1. Nice to Have
1.1. CAD
1.1.1. ideas
1.1.1.1. incentivising open hardware - if people offer their designs under open source licences, we can let them use a fully functional version of the cad platorm
1.1.1.2. Develop a standardised, open parametric file format- lends itself to objects being stored on git. version comparison on github for assemblies would be possible. could open scad be a file format, even if everything else is independent code
1.1.1.3. large potential for crowd funding. can offer more than sketchup and solidworks.
1.1.2. people
1.1.2.1. prema paetsch
1.1.2.1.1. software developer, made his own rendering engine
1.1.2.2. Larry Gritz
1.1.2.2.1. would need to be paid, but would be an incredible resource
1.1.3. Need
1.1.3.1. at least 1 person who has developed cad software before
1.1.4. existing resources
1.1.4.1. open scad
1.1.4.1.1. could be the basis of a parametric file format
1.1.4.2. http://www.opencascade.org
1.1.4.2.1. open source cad building blocks
1.1.4.3. freeCAD
2. Notes
3. Project Information
3.1. Open Hardware Database
3.1.1. Instruction platform
3.1.1.1. Unlimited you education
3.1.1.1.1. ideas
3.1.1.1.2. in progress
3.1.1.1.3. needs
3.1.1.2. what if we continue with the dozuki platform
3.1.1.2.1. is ifixit's api exactly the same as dozuki? or did they add it?
3.1.1.2.2. what is dozuki's view of taking their web services and writing their own apps to add in and embed their own information? can we just use dozuki as our back end?
3.1.1.2.3. can we read and write those databases with our own app?
3.1.1.2.4. can we embed a stack exchange platform
3.1.1.2.5. can you have videos per step? not just the intro
3.1.1.2.6. are we good to download documents/work offline?
3.1.1.2.7. we need to create our own trovebox like submission of images.
3.1.1.2.8. can we have a front end that is open, but if people want to make money they pay for their dozuki account and pay us for a support based model. otherwise all open source users are free.
3.1.1.3. what are we bringing?
3.1.1.4. monetisation
3.1.1.4.1. service based model
3.1.1.4.2. we provide as much high functionality as possible to open source users
3.1.1.4.3. but users that want to charge for their content, thats where the platform takes its cut.
3.1.1.4.4. need to solidify the concept and crowdfund it.
3.1.1.5. what about adoption?
3.1.1.5.1. find example cases for use/visibility
3.1.1.5.2. attraction points
3.1.1.5.3. needs to be mobile friendly
3.1.1.6. problems
3.1.1.6.1. no open documentation platform without limits.
3.1.1.6.2. we need an education platform that is open so it can be altered to our needs, much like dozuki.
3.1.1.6.3. We need an open source stack exchange like forum where modules can be embedded in our documentation, while all being contained in a nother central location
3.1.1.6.4. cloud based image storage for collaboration requires web access, this is really dumb
3.1.1.7. Technology
3.1.1.7.1. http://www.omanual.org/
3.1.1.7.2. https://www.ifixit.com/api/2.0/doc/
3.1.1.7.3. http://www.question2answer.org/
3.1.1.7.4. trovebox
3.1.2. Collaboration platform
3.1.2.1. problems
3.1.2.1.1. wiki platform doens't work, its clunky
3.1.2.1.2. no indexing on wiki, this should be automatic. no orphan pages
3.1.2.1.3. no good free mindmapping software exists mindmeister without limits.
3.1.2.1.4. need rapid logging ability from mobiles, rapid embedding of images and videos
3.1.2.2. ideas
3.1.2.3. needs
3.1.2.3.1. key step to acceleration of development and parallelisation of human resources
3.1.2.3.2. user logs
3.1.2.3.3. rapid posting ability for text, images, video.
3.1.2.3.4. mindmapping
3.1.2.3.5. rapid embedding of google docs, not the current 4 or 5 step process.
3.1.2.4. Technology
3.1.2.4.1. http://www.mediawiki.org/wiki/API:Main_page
3.1.3. Crowd based support
3.1.3.1. OSQA
3.1.3.2. question2answer
3.1.3.3. Shapado
3.1.3.4. Stackexchange
3.1.4. Git Versioning System
3.1.5. Bill or materials
3.2. Messaging
3.2.1. Instant messaging
3.2.2. Forums - Group Chat
3.2.3. Send images/audio etc
3.2.4. Q & A
3.3. Blog and News
3.3.1. Included
3.3.2. Included
3.3.3. Excluded
3.4. Crowd Sourcing
3.5. Crowd Funding
4. Timeline
4.1. Schedule
4.2. Budget
4.3. Resources
4.4. Delays
5. Limitations
5.1. Budget
5.1.1. Materials
5.1.2. Personel
5.1.3. Services
5.1.4. Duration
5.2. Delivery Timeline
5.3. Requirements
6. Actions
6.1. Define Project Schedule
6.1.1. Dependencies
6.1.2. Milestones
6.2. Limitations
6.2.1. Schedule
6.2.2. Budget
6.3. Define Project Development Measurement
6.3.1. KPI's
7. Resources
7.1. Content Management
7.1.1. Druple
7.1.2. Joomla
7.2. Version Control
7.2.1. Github
7.3. Communication
7.3.1. For Builds
7.3.1.1. ? Git ? Ability to look at modules
7.3.2. Per Person
7.3.2.1. Slack
7.3.3. Problem Solving
7.3.3.1. Stack Exchange
7.3.3.2. http://www.question2answer.org/
7.3.4. Forum?
7.4. BOM (Bill Of Materials)
7.4.1. Octopart