Date

25 Aug 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. Rachid Belkouch
2. William Welling 
3. Benjamin Gross 
4. Brian Lowe 
5. Andrew Woods
6. Don Elsborg
7. Alexander (Sacha) Jerabek
8. Huda Khan

Agenda

1. 2020-08 - i18n Editing Sprint - working towards a merge to 'master'
   1. Decoupling dependencies on VitroRequest
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Need a close review of all files that have been touched in both 'master' and the 'sprint-i18n' branches
      
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Needs debugging
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Three unassigned bugs
   5. Two unassigned documentation tickets
2. VIVO 1.12.0 release timeframe

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
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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