====== Minutes for Documentation Interest Group Meeting 3/7/11 ======

====Attendance / roll call====
  * rsoulliere is is Robert Soulliere, Mohawk College
  * kmlussier is Kathy Lussier, MassLNC
  * sfortin is Sally Fortin, Equinox Software
  * dbs is Dan Scott from Laurentian University, on the periphery
  * jenny is Jenny Turner, PALS
  * csharp is Chris Sharp, GPLS, mostly lurking 
  * jeff is Jeff Godin, TADL. Observing by happenstance.
  * bshum is Ben Shum, Bibliomation




====Staff client help pages====
  * Postponed for future meeting


====DIG Roles Update====
  * rsoulliere reported no volunteers before meeting after posting call on DIG list
  * Jenny volunteered for Reports Coordinator
  * kmlussier volunteered for OPAC/staff tasks content coordination

====1.6 and 2.0 Progress Report====
  * rsoulliere reported International access issues to documentation site seem to be resolved now with testers reporting that they are able to access site from all their locations
  * Many chapters have been added to 2.0 some of which were ported from 1.6 since content was the same.
  * KCLS and GPLS generously submitted documentation content for 2.0 last week and on the weekend before meeting. They have been added to documentation repository in asciidoc and DocBook XML formats.
  * More work on those to be done...
  * rsoulliere: Please review 2.0  outline and look for needed chapters or sections at http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.0:outline#partadministration
  * rsoulliere: In particular is anyone writing documentation for the Public Access Catalog part for 2.0 which could be contributed?
  * kmlussier with check with her group regarding Public Access Catalog documentation
  * kmlussier planning to tackle the cataloging tasks this week.
  * dbs still planning to write up "why nullability matters in reports"
  * jenny has some new info on reporting sources in 2.0 and will see if anything is new at Reports Task Force Meeting


====Need more policies====
  * rsoulliere asked if more formal written policies were need for DIG documentation?
  * jenny mentioned that having coordinators for each section might help with some recent issues. At least then, if something were submitted to the general DIG list, the coordinator for that section could at least be responsible for grabbing it?
  * dbs pointed to some guidelines at http://www.evergreen-ils.org/dokuwiki/doku.php?id=contributing#documentation_contribution which could be augmented
  * kmlussier also found this - http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_participation
  * csharp referred to the fedora project (https://fedoraproject.org/wiki/Docs_Project_licensing_FAQ) as a good example.

====AsciiDoc====
  * AsciiDoc was discussed as an option to use for documentation
  * Many advantages of the format were discussed.
  * dbs: pointed out that it could offer a good way of single-sourcing some documents that we want in the tarball anyway - like the README (install instructions), release notes, other text docs
  * It was clarified that AsciiDoc is not going to replace the current DocuBook format for official documentation, but simply provide a means to  automate a single-sourcing of some docs
**Action Item: rsoulliere will experiment more with AsciiDoc and provide more info on list.** 

====April 4, at 2:30 PM EST is the next scheduled DIG meeting====