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

===Date: Friday, September 12, 2014===

  * Focus on new 2.7 features
   * http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_hack-a-way
====== DIG hack-a-way 2013 - Agenda/Goal Ideas ======


===Date: Friday, November 15, 2013===

===Agenda/Ideas===
  * Docs Bitesize Bugs (helpful for newcomers to practice on)
    * [[https://bugs.launchpad.net/evergreen/?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=documentation+bitesize+&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search|Documentation Bitesize Bugs on Launchpad]]
    * Update any doc to conform with the [[evergreen-docs:dig_style_guide|DIG AsciiDoc Style Guide (rough draft)]]
    * Rewrite pieces of the [[http://docs.evergreen-ils.org/dev/_floating_groups.html|Floating Groups]] doc for readability
    * Add screenshots to the [[http://docs.evergreen-ils.org/dev/_floating_groups.html|Floating Groups]] doc
    * Update old screenshots in various sections (**TODO:** add specific sections)
      * [[http://docs.evergreen-ils.org/dev/_installing_the_staff_client.html|Chapter 7. Installing the Staff Client]]
  * Proofread Berklee intern documentation conversions
     * Consider new way to organize the very large "Cataloging" section  --- //[[director@hagerstownlibrary.org|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): [[evergreen-docs:dig_style_guide|DIG AsciiDoc Style Guide (rough draft)]]
  * Fix documentation bugs reported on Launchpad, IRC, or mailing list  --- //[[director@hagerstownlibrary.org|Ruth Frasur]] 2013/11/09 10:38//
    * search for the term "documentation" , "docs" in logs/list
    * [[https://bugs.launchpad.net/evergreen/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=documentation+&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on|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
    * [[evergreen-docs:2.4_needs|2.4 documentation needs]]
    * [[evergreen-docs:2.5_needs|2.5 documentation needs]]

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

===Test Servers===
  * Equinox Test Server (information available in [[community_servers:]] page)

====== DIG hack-a-way 2012 - Agenda/Goal Ideas ======

===Date: October 5th, 2012===

===Agenda/Goal ideas===
   * 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


===Requirements===
   * 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