Date

21 Oct 2021

Call-in Information

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

• Join Zoom Meeting
  https://lyrasis.zoom.us/j/81398228834?pwd=SE0wdFN3NnFVbEhYVUhuM3BtQmVUQT09

  Meeting ID: 813 9822 8834
  Passcode: 728426

Attendees

 Indicating note-taker

1. Brian Lowe  
2. Dragan Ivanovic 
3. Georgy Litvinov 
4. Huda Khan 
5. Ralph O'Flinn 
6. William Welling  

Agenda

1. PRs on VIVO and Vitro

   1. https://github.com/vivo-project/Vitro/pulls and https://github.com/vivo-project/VIVO/pulls
   2. Other PRs out there in VIVO and Vitro that are legacy.
   3. On committers’ call, probably should go back through these to see which should be merged or not.  Need some finalized decisions
   4. Assignment of reviewers
2. Open VIVO issues
3. VIVO 2.0 architecture
   1. https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing

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

1. PRs on VIVO and Vitro
   
   Several PRs -Dragan
   
   Massive PR from Graham -Ralph
   Assignment: each review PR and determine if we should proceed with. -Ralph
   
   Maybe some should be thrown out - Ralph
   
   Should we have a set of criteria of include/disclude? -William
   
   
   PR rules for committers
   1. Number of approvals
   Small changes 1 approval
               Committer decision for whether 2 approvals are required
   
   Scope of exercise? -Bryan
   
   Not intended for approval or merge?
   
   First pass with a list to go over -Ralph
   Will send out by tomorrow -Ralph

Conclusion: 32 total open PRs. Some are linked between repositories. -Dragan

The PR branches needs to be reevaluated.

Included in list by Friday -Ralph

Failing of a GitHub action - Is it a problem in pull request or github action? -Dragan
Issue: may never build due to versions unavailable -Ralph

1. Open VIVO issues
   
   Situation is that there are many issues. -Dragan
   
   Can Brian, Huda, Ralph go through issues? -Dragan
   
   
   
   Support for certain institutions? -Dragan
   
   
   Should we review tags in GitHub?
   
   Assignee for non active contributors?
   
   Should we re-assign?
   
   
   
2. VIVO 2.0 architecture
   1. https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing

Draft notes on Google Drive

Actions 

•  Ralph O'Flinn first pass through PRs and sending out an email to other committers
• Brian Lowe Huda Khan Ralph O'Flinn to review GitHub issues assigned to them. Are you still interesting in those issues? Maybe it is even resolved meanwhile or not of interest for VIVO community (especially for issues opened 5 or more year ago). 
• Dragan Ivanovic to continue first pass and reviewing of GitHub issues
• All to read and provide feedback for   VIVO 2.0 architecture https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing