It's an unconference!

Please edit this page boldly and add your ideas. You must be registered to edit this page.

• Book sprints: 0 to book in 5 days or less, with FLOSS Manuals (Janet Swisher)

• Pydocweb: Round-tripping API docs from code to wiki and back (Janet Swisher)

• Group discussion: Strategies for recruiting writers

• Group discussion: Community structures. Talk about how do the ways we set up various formal or informal structures in our communities effect how documentation teams work (or don't).

• Group discussion: "3rd party" vs. "Community" documentation - Books, DVDs, and documentation from companies vs. the raw, open democracy/meritocracy of the open source project. Is there room for both? Do they compliment or compete? How to profit from them all as a community and project.

  The Drupal project is going through some intense discussion around this and other aspects of documentation. Fresh opinions, perspectives and ideas from other projects very welcome! (jam)

• Documentation workflows - cross pollination: Acquia currently has an all open source, mostly Drupal solution for preparing and presenting its documentation online and generating PDFs from the source XHTML. This has both strengths and weaknesses. I'll share how it works and I'd appreciate feedback and suggestions on how it might be improved. I am also very interested how other companies and projects do similar work. (jam)

• Gnome Show & Tell - A quick glimpse into the problems we've faced in the Gnome documentation team and how we're trying to solve those problems today. (Shaun McCance)

• Documentation usability - Learning style matching - 80/20 for documentation - Beyond text and screenshots; where does documentation go? What are effective strategies to help users? How to enable users to self-select different versions of the same information? Is this even practicable?

• Translation - How do we prepare documentation that is ready to be translated?