Date

02 Feb 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?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• 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. Brian Lowe
4. Huda Khan 
5. Benjamin Gross 
6. Nicolas Dickner
7. Georgy Litvinov
8. Ralph O'Flinn
9. Michel Héon 
10. Benjamin Kampe 

Agenda

1. Open email threads
   1. Error after installation (no MySQL, no attachment)
   2. VIVO 1.11.1: People page is empty (incomplete triples)
2. Sprint updates
   1. Release blockers:
      1. Needing additional testing/review
         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.
            1. vivo-custom-webapp PR-3
      2. Needing to be worked / resolved
         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.
         5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Tickets that will hopefully have PRs in the next day or two:
      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.
   3. All tickets that are targeted for the i18n Beta must be resolved and merged this week
   4. Merge of `sprint-i18n` to `main` at the beginning of next week (week of Feb 8th)
   5. 1.12 release planning
      1. 1.12 release candidate #1: Feb 15st
         1. Two week RC-1 testing period
         2. For each subsequent RC-2 (if required), adding another two weeks to the schedule
3. Renaming of vivo-community branches from `master` to `main` (reference)
4. Potential patch releases?
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
5. Tickets that should be close to merge
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. Post-i18n priorities
   1. VIVO-in-a-box
   2. Ingest / Kafka
   3. Advanced Role Management
   4. 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