...

1. William Welling 
2. Andrew Woods 
3. Brian Lowe
4. Ralph O'Flinn 
5. Michel Héon 
6. Huda Khan
7. Alexander (Sacha) Jerabek
8. Benjamin Gross
9. Don Elsborg
10. Santhosh Kumar Gopalan

Agenda

1. Announcements
2. TIB/UQAM - Kafka initiative updates - 2020-12-16 - Special Topic - VIVO Kafka Ingest
3. Community mailing list
   1. Error when trying to link a person with a grant
   2. Images are not displayed after migration
4. Advanced Role Management sprint - 2020 - VIVO Sprints
5. 1.11.2 patch release - likely not going to happen

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

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

6. Transition from JIRA to GitHub-Issues?
   1. Potential larger gains to be had with using GitHub Actions to push VIVO Docker images
7. Working towards 1.12
   1. To be reviewed 

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

         1. Benjamin Gross / Brian Lowe : any final comments?

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

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

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1944

   2. Documentation needed

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

   3. 1.12 release planning
      1. Email of schedule to vivo-community 
      2. Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
      3. Sprint to test merge of sprint-18n into master: week of Jan 25th
      4. 1.12 release candidate #1: Feb 1st
         1. Two week RC-1 testing period
         2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
      5. Do we want the `war` install in 1.12? -

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

         1. Next steps?
8. Tickets that should be close to merge

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

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

9. Post-i18n priorities
   1. VIVO-in-a-box
   2. Messaging
   3. Moving Scholars closer to core - next steps

...