Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Notes

Dragan: We continue our work on VIVO REST API, it is one of the most active VIVO development part at the moment. There is some progress, some issues were found and already fixed.
Long delay after login has been resolved. My question: have you tried it at the University of Florida?

Michael: We haven’t tried to fix it. It is on our list of things to check.

Dragan: It is merged to the main branch. 

Michel: I am going to check it. When will the next 1.14 release be ready?

Dragan: Hopefully soon, it might be released after this Thursday or in upcoming weeks.

Dragan: Publication claiming has been added to VIVO documentation, it was documented in release notes before that.

Dragan: Last week a vulnerability was found and it is already fixed and merged into the main branch. It relates to javascript code that could be provided as url and then executed in browser.

Dragan: We created release candidate 5 and tested it. There is one result for RC1 that Ivan did and Milos prepared results for RC5. It looks like features work as expected. It is great that we have VIVO tested with Windows and Linux. Hopefully we will release a new VIVO soon.

Also some discussions started about the next minor release. Hopefully Dynamic API will be part of VIVO 1.15.  We also have some pull requests that might also be part of 1.15 release. There is also improvement with attribute based access control, audit module. Also we might update jena to version 4.X. Also William prepared PRs to fix VIVO deployment. Also code style has been defined and included in the process of application building. It is going to be turned off for existing classes by default and part by part exclusions list is going to be reduced.

Besides that I am not sure we have now some implemented features, like “Restore forgotten password”.

Hopefully we will start reviewing pull requests and merging them in September.
Once we discussed that we could adapt only one theme and fix it in accordance to accessibility guidelines. 

Dragan: Next week we will have a regular meeting and then switch to biweekly meetings during the summer.

Draft notes in Google Docs

Task List

  •   

Previous Tasks 

...