DIG hack-a-way 2014 - Agenda/Goal Ideas

DIG hack-a-way 2013 - Agenda/Goal Ideas

Docs Bitesize Bugs (helpful for newcomers to practice on)
- Documentation Bitesize Bugs on Launchpad
- Update any doc to conform with the DIG AsciiDoc Style Guide (rough draft)
- Rewrite pieces of the Floating Groups doc for readability
- Add screenshots to the Floating Groups doc
- Update old screenshots in various sections (TODO: add specific sections)
  - Chapter 7. Installing the Staff Client
Proofread Berklee intern documentation conversions
- Consider new way to organize the very large "Cataloging" section — Ruth Frasur 2013/11/09 10:35
Convert and update old documentation into AsciiDoc
Discuss a DIG style guide
- Example: Should menu item labels that are referenced be bolded or monospaced, both?
- Rough draft (feel free to edit): DIG AsciiDoc Style Guide (rough draft)
Fix documentation bugs reported on Launchpad, IRC, or mailing list — Ruth Frasur 2013/11/09 10:38
- search for the term "documentation" , "docs" in logs/list
- Launchpad bugs with tag "documentation"
"Evergreen in Action" work
- Update content for EG 2.5
- Move more content from book into regular docs
Create new documentation for new or undocumented features
- 2.4 documentation needs
- 2.5 documentation needs

Berklee College of Music Library - Boston, MA
Equinox Software - Duluth, GA ‎(see http://markmail.org/message/g5u7jjsgr5xsvego)

AsciiDoc training (proposed by Yamil)
migrate older documentation to 2.2 or 2.3 docs that works as is (proposed by Yamil)
update and migrate older documentation to work in 2.2 or 2.3 docs (proposed by Yamil)
create new documentation for brand new features in EG 2.3 by looking for minimal asciidoc files created by developers in the "/docs" directory (proposed by Yamil)
Autographed Evergreen in Action manuals
Next year's DIG meeting at conference

internet access
test servers
- EG 2.2?
- EG 2.3 - Indiana has a test server 2.3 RC1 available. Client download is at http://testing.evergreen.lib.in.us/updates/manualupdate.html