...

Agenda

1. Community questions
   1. Updates? "Site admins" unable to add People (email)Error when trying to link a person with a grant
2. Don Elsborg : Explore using the i18n files to store local institutional RDF label and description changes.
3. Current community sprint updates?
   1. ORCID
   2. Kafka
   3. Messaging
4. 1.11.2 patch release

   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

5. Working towards 1.12
   
   1. To be reviewed 

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

      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-1944

   2. Documentation needed

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

   3. 1.12 release planning
      1. Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
      2. Sprint to test merge of sprint-18n into master: week of Jan 25th
      3. 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
      4. Do we want the `war` install in 1.12? -

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

6. 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

7. Post-i18n priorities
   1. VIVO-in-a-box
   2. Messaging
   3. Moving Scholars closer to core - next steps
   Moving Data Ingest Task Force forward

Future topics

1. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
2. Renaming of 'master' branch? (ZDNet, BBC)
   1. Guidance from GitHub 
   2. DSpace has done it
   3. Fedora has done it
   4. Samvera is doing it
3. 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-1751

   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

...