QUESTIONS
-- How can a community be stimulated to document?

• one enjoyable activity for documentation of open hardware in a group context is to get two groups with two projects: each group documents their project as best they can, then the other group has to try to make it using only that documentation, no questions or other communication allowed. It makes clear how important good documentation can be, and puts them in the mindset of somebody trying to recreate the project. . the most important issue to get across is that documentation is not just nice storytelling, it's really valuable and essential to the open source process.

-- How do you experience this is in your own practise?

• 
  

-- Even die-hard fablab wiki fans are thinking about switching to something like Instructables, because there is a community and it points out incompleteness, things not working etc

• Wikifab is still new but it seems like the most promising development in documentation of maker/OSHW projects, as it integrates well with exisiting free culture infrastructure like wikipedia, can export to open standards,  is a non-profit, doesn't serve ads, and has a quickly growing community. http://en.wikifab.org/index.php/Main_Page

-- Do you have any experience with this?

-- Other ideas ...