Date

02 Dec 2020

Call-in Information

• https://lyrasis.zoom.us/my/vivo1

Attendees

 Indicating note-taker

1. Brian Lowe 
2. Benjamin Gross  
3. Ralph O'Flinn
4. Andrew Woods 
5. William Welling

Agenda

1. Patch release? 1.11.2
   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.
2. In-review
   1. Softballs
      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.
   2. 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.

Other topics

1. Vitro JMS messaging approaches
2. Architectural diagrams - discuss at a future date
   1. VIVO Components
   2. VIVO Ecosystem

Notes

1. Doug/TAMU will be upgrading to 1.10 (1.11?) over holidays
2. Investigate BlazeGraph (HTTP )
3. TDB recommendations
   • dump/restore feature exists in siteAdmin
   • Find triplestore that has direct integrations with Kafka
     • Persistent connections
4. Staging CI branch
   • Need to specify relationship between related PRs from multiple repos
   • Use develop branch that is being deployed at regular frequency (hourly?)
   • Process:
     • Team coordination into CI-branch
     • GitHub Actions ??
     • Build/deploy to persistent AWS server
5. Employ more stylechecks
6. Triage in-review tickets at committer meetings
   • Require a committer review quota?
7. Use semantic labels to indicate scope of a PR, e.g.
   • trivial patch
   • minor change
   • major change
8. Multi-tenancy for VIVO?
9. Move away from JIRA?
   • Handle completely in GitHub issues?
   • Issue-tracking: project at vivo-project org
   • Currently JIRA requires a JIRA account
   • We use Jira because Lyrasis uses it... we presumably used it in the past because Cornell used it. Benjamin totally agrees that jumping between Jira and Github is annoying, and some people have a tendency to post comments on Github vs Jira. The nice thing about moving to Github issues is that the issue is not inherently removed from the code.

Actions

• ...

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.