Date

08 Dec 2020

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

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. William Welling 
2. Andrew Woods 
3. Bruce Herbert 
4. Ralph O'Flinn 
5. Brian Lowe 
6. Michel Héon 
7. Don Elsborg 
8. Huda Khan
9. Benjamin Gross

Agenda

1. Current community sprint outcomes?
   1. ORCID
   2. Kafka
   3. Messaging
2. Weill Cornell testing updates - Sarbajit Dutta
3. 1.11.2 patch release
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. Transition from JIRA to GitHub-Issues?
5. Working towards 1.12
   1. To be reviewed 
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Documentation needed
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   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? - Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. Tickets that should be close to merge
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
7. Post-i18n priorities
   1. VIVO-in-a-box
   2. Messaging
   3. Moving Scholars closer to core - next steps

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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Draft notes in Google-Doc 

Actions