Dates

• July 14 - 16

Participants

1. Andrew Woods
2. William Welling
3. Don Elsborg
4. Brian Lowe

Tickets

• JIRA Scrum Board
• All i18n tickets

Goals

1. Prepare for beta release of i18n functionality
   1. Become familiar with i18n updates
   2. Resolve top-priority JIRA tickets 
   3. Merge `i18n-sprint` branches into their respective `master` branches
      1. https://github.com/vivo-project/VIVO/tree/sprint-i18n
      2. https://github.com/vivo-project/Vitro/tree/sprint-i18n
      3. https://github.com/vivo-project/VIVO-languages/tree/sprint-i18n
      4. https://github.com/vivo-project/Vitro-languages/tree/sprint-i18n
   4. Update documentation
      1. User documentation - As a user, how do I use the new i18n functionality?
      2. Adding a new language documentation - How do I bring a new language to the suite of available VIVO languages?
      3. Configuration and Activation documentation - As a site administrator, how do I configure and enable one or more available VIVO languages?
      4. Upgrade documentation - As a site administrator, how do I upgrade my site and data to use the new i18n functionality?

Current Issues

1. Homogenize design for filtering languages between frontend and backend approaches
2. Upgrading... reorganization of firsttime/everytime
3. Resolution on split-out of language files:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Stand-up Reports