Date

12 Jan 2021

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

To join the online meeting:

Go to: https://lyrasis.zoom.us/my/vivo1
One tap mobile:
- US: +16699006833,,9358074182# or +19292056099,,9358074182#
Or Telephone:
- US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257
- Meeting ID: 935 807 4182
International numbers available: https://zoom.us/u/aeANHanzED

Indicating note-taker

TIB/UQAM - Kafka initiative updates - 2020-12-16 - Special Topic - VIVO Kafka Ingest
Community mailing list
1. Error when trying to link a person with a grant
2. Images are not displayed after migration
Advanced Role Management sprint - 2020 - VIVO Sprints
1.11.2 patch release
Transition from JIRA to GitHub-Issues?
1. Potential larger gains to be had with using GitHub Actions to push VIVO Docker images
Working towards 1.12
1. To be reviewed
2. Documentation needed
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? -
    1. Next steps?
Tickets that should be close to merge
Post-i18n priorities
1. VIVO-in-a-box
2. Messaging
3. Moving Scholars closer to core - next steps

Vitro JMS messaging approaches - redux
1. Which architectural pattern should we take?
2. What should the body of the messages be?
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
Incremental development initiatives
3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven