Date
Call-in Information
Time: 10:00 am, Eastern Time (New York, GMT-04:00)
Join Zoom Meeting
https://lyrasis.zoom.us/j/81398228834?pwd=SE0wdFN3NnFVbEhYVUhuM3BtQmVUQT09Meeting ID: 813 9822 8834
Passcode: 728426
Attendees
Indicating note-taker
Agenda
PRs on VIVO and Vitro
- https://github.com/vivo-project/Vitro/pulls and https://github.com/vivo-project/VIVO/pulls
- Other PRs out there in VIVO and Vitro that are legacy.
- On committers’ call, probably should go back through these to see which should be merged or not. Need some finalized decisions
- Assignment of reviewers
- Open VIVO issues
- VIVO 2.0 architecture
Future topics
- Prioritizing and planning post-1.12 development
- Forward-looking topics:
- frameworks: Spring / Spring Boot / alternatives
- Horizontal scalability
- Deployment
- Configuration : files / environment variables / GUI settings
- Editing / form handling
- Adding custom theming without customizing build
- Post-release priorities
- Ingest / Kafka
- Advanced Role Management
- Moving Scholars closer to core - next steps
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be
- Incremental development initiatives
- Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Tickets
Status of In-Review tickets
Notes
- 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
- 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? - VIVO 2.0 architecture
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