...

1. Don Elsborg 
2. Andrew Woods
3. Steven McCauley
4. Huda Khan
5. Brian Lowe
6. Ralph O'Flinn
7. Benjamin Gross 

Agenda

1. Sprint planning - i18n
   
   1. Sprint dates: Apr 6th - 17th
   2. Sprint prerequisites
2. Announcements
   1. ...
3. 2020 Sprint Planning
   1. VIVO-i18n - Canadian French Initiative
   2. Pre-sprint planning meeting: Mar 25th @10am ET (https://uqam.zoom.us/j/996861901)
   3. Dates: Apr 6th - 17th
4. 1.11.1 maintenance release - announced!
   1. GitHub maintenance branches
5. Moving VIVO forwardCode clean up, "Legacy" files: 
   1. Goals
      1. Decoupled application (headless option?)
      2. Easy to install
      3. Integration tests
      4. Informed team
   2. Sorting out the code
      1. xxx
   3. Removing the cruft ("Legacy modules")
   1. 1. https://github.com/vivo-project/Vitro/tree/master/legacy
      2. https://github.com/vivo-project/VIVO/tree/master/legacy
   Recent community issues
   1. Using community questions to lift the entire team

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

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

      3. Problem when saving labels
6. Vitro JMS messaging approaches
7. Incremental development initiatives

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

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

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

   4. Integration test opportunities with the switch to TDB
8. Vitro pull-requests

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

       - looks good

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

...