Date

14 Sep 2021

Call-in Information

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

• https://lyrasis.zoom.us/my/vivo1?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  Passcode: 351860

Attendees

 Indicating note-taker

1. Brian Lowe  
2. Dragan Ivanovic 
3. Georgy Litvinov
4. Benjamin Kampe
5. Matthias Lühr   

Agenda

1. Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
2. A roadmap to migration from JIRA to GitHub issues - https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
   1. Analyze available tools
      1. https://github.com/rstoyanchev/jira-to-gh-issues  ←
      2. https://github.com/susinda/github-client
      3. https://github.com/hbrands/jira-issues-importer
   2. Adopt/customize https://github.com/rstoyanchev/jira-to-gh-issues for our solution
   3. Test/validate migration - https://github.com/chenejac/VIVOTestMigrationJIRA/issues - Action needed!!!
   4. Map JIRA (https://vivo-project.atlassian.net/jira/people/search) and GitHub accounts (https://github.com/orgs/vivo-project/people). The mapping is defined here: https://docs.google.com/document/d/1SKRMuky8x8m9CgOKtxs16LWFuuVfYlQR6LkjASBEzrI/edit?usp=sharing Action needed
   5. Add labels at https://vivo-project.atlassian.net/jira/ for distinction of VIVO and VITRO issues? Do we need this? If do, an action needed
   6. Run migration into the production (https://github.com/vivo-project/VIVO).
   7. Create GitHub issues templates ( https://github.com/vivo-project/VIVO) - An action needed
3. Georgy's proposed architecture:
4. 
5. Decoupling Freemarker
6. Indexing for Scholars

Future topics

1. Prioritizing and planning post-1.12 development
2. Forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
3. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
4. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
5. 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 on Google Drive

Actions 

• All to validate result of JIRA to GitHub Issues migration tool before it is run into operation - https://github.com/chenejac/VIVOTestMigrationJIRA
• Dragan Ivanovic to correct wiki documentation - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
• Dragan Ivanovic to work on priorities' google sheet document

Previous Actions

• Brian Lowe to draft initial sketch of "VIVO2" in a Google Doc
• Huda Khan to review:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Brian Lowe to review:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
•  Ralph O'Flinn to review:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.