...
Dragan: The fist announcement regarding release candidate 2, which contains two fixes and two small contributions: removal of dependency and introducing a flag to enable/disable Web of Science.
Dragan: We have some period for release candidate testing. My idea is to make the release cycle shorter (until 24 of March). If everything is correct we will release 1.14.0. If there are no issues with the plan, then I will make an announcement tomorrow. The only problematic part for testing through TIB VIVO instance is using flag to enable/disable the web of science.
Another announcement related to webinars. Yesterday there was a lyrasis meeting to run a series of webinars. There were idea to organize VIVO ontology webinars and other topics.
I would like to investigate the way VIVO is installed, that would help us to review William’s PR to deploy VIVO. I am not sure when webinars should start, will see when they start.
Dragan: Always in March and October we have issues with period when Northern America and Europe have different time changes.
Another issue in our agenda is regarding OpenVIVO. I am not sure if any of you have tried it. It was intended to be an instance to explore VIVO. This was working in the past, it might be ORCID API has changed.
...
First we should discuss the license issue with the leadership group.
I am not sure how we are going to apply with the existing codebase.
The most important one is decoupling VIVO build from installation, but we should invest some time into testing it. It is for sure better than the current situation, but anyway I think it is a step forward. Dragan would like to investigate the way VIVO is installed, that would help us to review William’s PR to deploy VIVO.
We worked on two tracks and Michel worked on testing performance with external graph usage.
Kevin started working on migration to Jena 4, basically that’s what was implemented in the current sprint.
I hope it Dragan hopes the next sprint might be used to create new REST endpoints and create new graphical elements for endpoints. Implement an engine to read notation and visualize forms. Georgy is not sure sprints are the best way for further work on dynamic api. Michel suggested to continue working on semantic features in the next sprint and to try to complete what we started.
Mark: Will we continue to use Java 8 after the 1.14 release?
Dragan: No, after the 1.14 release we plan to increase minimal version to Java 11.
...