...

1. Alexander (Sacha) Jerabek  
2. Rachid Belkouch
3. Michel Héon
4. Andrew Woods
5. Christian Hauschke
6. Joachim Dornbusch
7. Matthias Lühr
8. Nicolas Dickner
9. Maxence Gévaudan
10. Ralph O'Flinn

Agenda

1. Team roles - continue conversation, starting with "Testing" from 2020-04-01 - i18n Editing pre-sprint meeting 
   1. Developer
   2. Documentation / Installation
   3. Testing
   4. Translation
2. Status of work in-progress
   1. Pre-sprint i18n GitHub Branch Clean-up
      1. Pending response to comment: vitro-pr-150
      2. ? AddReviewerRoleToPersonGenerator.java
   2. Split of VIVO/Vitro-languages by language (need updated README.md)
      1. https://github.com/vivo-project/Vitro-languages/tree/sprint-i18n
      2. https://github.com/vivo-project/VIVO-languages/tree/sprint-i18n
   3. Tickets needing review

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1759

   4. Flagging UQAM updates (Vitro commit, VIVO commit)
3.  Logistics
   1. i18n Slack channel
      1. Virtual "stand-up" - see template below, daily/first-thing
   2. GitHub processes
      1. Moving from 'sprint-i18n-whitespace' to 'sprint-i18n' 
      2. Pull-request with JIRA and description
      3. Review in GitHub, indicate "approval" ..or otherwise
   3. Sprint retrospective meeting: Apr 17th @10am ET (same time as this call)
   4. Using JIRA

...

[VIVO i18n Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Blockers:
  {brief textual description}

Notes 

Roles

Documentation

1. And how to add new languages - Sacha/Rachid
2. How to install with existing languages - Sacha/Rachid
3. How to use the features - Christian
   1. 1.12: how an end-user will work with the i18n features

Testing

1. UQAM will be testing French
2. Christian/Matthias will be testing German following the patterns defined by UQAM
3. Test approach (3-phase)
   1. create a list of problems with the i18n branch
   2. fix bugs / create tests
   3. verify functionality
4. Sacha to create test plan

Actions

•  All: Adding names to roles in the sprint page.
  

...