2016-08-31 Meeting notes

Is there anything more effective we can do to get feedback?

• we are stumped so far
• target specific people with specific topics

People to target?

• comb through answers that are in the FAQ and ask for the people who contributed the answer to take a look at the broader category
• Also / or refine the list down to topics that really need answers or need to be looked at
• More specific questions might help
• Survey?

• Linking to the listserv answer or use the answer to create text for the FAQ
• Ask people / groups how they'd like their work / answers to be represented in the FAQ

• divide sections and see:
  • What's answered
  • What's not answered
    • For what's not answered, think of who might be able/willing to contribute an answer (is there a sub-team that could help with the section, especially)
    • Possibility: bundle set of questions and send to another sub-team

• List areas where there are active sub-teams adding to the documentation & asking how they'd like to have their work represented
• Compile list of people (and possibly also find people who have contributed answers and ask how they would like their work represented)

• Google groups has been suggested as a platform for the FAQ
• Rachel found an open source php platform http://moss.demo.phpmyfaq.de/
• DPN is using google groups https://groups.google.com/forum/#!forum/dpn-faq
• Github / Jekyll
  • https://sendgrid.com/blog/creating-sustainable-documentation-with-jekyll/
  • https://www.wisecashhq.com/blog/lessons-learned-creating-a-git-based-knowledge-base-for-my-saas-product
  • https://blog.timowens.io/writing-collaborative-documentation-with-dokuwiki-and-github/