Date
Call-in Information
Time: 11:00 am, Eastern Time (New York)
To join the online meeting:
https://lyrasis.zoom.us/j/84378615572?pwd=bGUxSjlyRTdjOGl5U1B6L0Yva3RQdz09
Meeting ID: 843 7861 5572
Passcode: 556561
One tap mobile
+16699006833,,84378615572#,,,,*556561# US (San Jose)
+19292056099,,84378615572#,,,,*556561# US (New York)Dial by your location
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
+1 253 215 8782 US (Tacoma)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 843 7861 5572
Passcode: 556561
Find your local number: https://lyrasis.zoom.us/u/kerqtGDrJ4
Slack
- https://vivo-project.slack.com
- Self-register at: http://bit.ly/vivo-slack
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
- Dragan Ivanovic
- Brian Lowe
- Michel Héon
- William Welling
- Georgy Litvinov
- Kevin Day
- Mark Vanin
- Ivan Mrsulja
- Benjamin Kampe
- Maxim Prokopenko
- Samantha Emerson
- B. Henderson
- Miloš Popović
Agenda
- Questions/Issues/Pull requests/Announcements
- VIVO release candidate number 2
- Webinars
- planned to start soon
- Time difference issue
- OpenVIVO
- The sprint
- February sprint completed
- Plan for the next sprint
Notes
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 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.
Does anyone in this group know who could be in charge of maintaining OpenVIVO.
Maybe we should consider creating a new instance to explore VIVO.
Last topic in the agenda is the February sprint. I think we have made some progress. I believe it was a more or less successful sprint with some results. On previous sprints we completed 60-70% of tasks, it is not the case now, but still it is a good progress.
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.
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.
Dragan: I noticed new people in the call. If you have any questions, please feel free to ask.
Maxim: Docker compose failed when we tried the latest VIVO and it freezes on downloading layers. Only docker space compose worked for us.
Task List
- Dragan Ivanovic to announce publishing VIVO 1.14.0 RC2
- someone to test RC2
- Dragan Ivanovic to create survey for collecting standard practice in VIVO deployment process
Previous Tasks
- Dragan Ivanovic to add columns in the project board for Priority and Difficulty.
- Sprint participants to read description of issues and think about their preferences.
- Dragan Ivanovic will contact Lyrasis admins to get an account for https://vivo.lyrasis.org/
- Dragan Ivanovic will fix issues with layout and French sample data and publication graph - https://github.com/vivo-project/VIVO/pull/3810
- Georgy Litvinov will fix the issue with faux data properties with xml literal range - https://github.com/vivo-project/Vitro/pull/363
- William Welling will review previously described issues
- Dragan Ivanovic will work on specification of tasks for the next sprint - https://github.com/orgs/vivo-project/projects/5 and https://github.com/orgs/vivo-project/projects/6
- Dragan Ivanovic to send a test email through contact form - https://vivo.lyrasis.org/contact/
- William Welling to complete review/testing of https://github.com/vivo-project/VIVO/pull/3805 and to summarize results in the PRs comments
- Dragan Ivanovic to review William's comments and check what should be fixed/resolved before merging of the the branch
- Georgy Litvinov to fix issues with Russian email templates
- Georgy Litvinov to fix issues with faux data properties
- All to think about organization/improvements of sample data, Dragan Ivanovic to add an item in the next week agenda for discussion
- Dragan Ivanovic in communication with Georgy Litvinov to write/update documentation for faux (data) properties
- Dragan Ivanovic to review and merge
- Brian Lowe to review https://github.com/vivo-project/VIVO/pull/3788 and https://github.com/vivo-project/Vitro/pull/341 preferably by end of the week (11/25/2022)
- Brian Lowe to review https://github.com/vivo-project/Vitro/pull/347
- Michel Héon to validate https://github.com/vivo-project/Vitro/pull/347 and test performance with remote Fuseki
- Anyone to validate https://github.com/vivo-project/Vitro/pull/348 and https://github.com/vivo-project/VIVO/pull/3797 preferably by end of the week (11/25/2022) - description how it should be validated provided in the PR description
- Benjamin Kampe to review https://github.com/vivo-project/Vitro/pull/349 and https://github.com/vivo-project/VIVO/pull/3795 preferably by end of the week (11/25/2022)
- Dragan Ivanovic to create PR in cooperation with Michel Héon for merging ttl files (labels' translations) into Vitro/VIVO repositories
- Dragan Ivanovic to ask Arif for more info on the reported issue - https://groups.google.com/g/vivo-tech/c/gmyQIMWbm_Y
- Dragan Ivanovic to open a ticket for https://groups.google.com/g/vivo-tech/c/wDblxLmeTjs. Done, ticket available at https://github.com/vivo-project/VIVO/issues/3772
- Dragan Ivanovic will redirect reporter of this issue https://github.com/vivo-community/vivo-docker2/issues/22 to https://github.com/vivo-project/VIVO#docker
- All to analyze the issue reported in the slack (https://vivo-project.slack.com/archives/C8RL9L98A/p1663253504895989) and check whether we should open a GitHub issue and add to the i18n redesign project board - https://github.com/orgs/vivo-project/projects/4
- Brian Lowe will respond on the email https://groups.google.com/g/vivo-tech/c/5AY9h15h4vc/m/OjqekVxlBgAJ?utm_medium=email&utm_source=footer&pli=1
- All to consider participation in the sprint and register via https://forms.gle/qLi1PhRrrpvUrrYRA
- Dragan Ivanovic to work on specification of tasks for the sprint - GitHub project board
- Michel Héon to work on the translation messages ontology
- Dragan Ivanovic will bring up with leadership group that we would like to set up task force for dynamic API
- Dragan Ivanovic will create infrastructure for the next sprint (slack channel, GitHub project board, wiki page, GitHub branch, GitHub issues, etc.)
- Michel Héon to work on the ontology for UI labels (in multiple languages)
- All to think about dates for the next sprint
- Dragan Ivanovic to resolve conflicts for https://github.com/vivo-project/Vitro/pull/311 and https://github.com/vivo-project/Vitro/pull/297
- Dragan Ivanovic to write script for preparing a release candidate - started at https://github.com/chenejac/VIVO-release-publisher
- All to test the release candidate - Release Testing - 1.13.0
- Dragan Ivanovic to publish VIVO 1.13.0 release (if there is no reported issue till 1st of September)
- Dragan Ivanovic to prepare presentation for demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to send reminder for the demo meeting - 2022-07-07 - Dynamic API demo meeting
- Dragan Ivanovic to open an issue for a reverse proxy (redirecting) - https://vivo-project.slack.com/archives/C8RL9L98A/p1651739159126489
- Dragan Ivanovic to contact Andrew Wood for resolving the issue with registration for the Slack channel
- All to consider participation in the sprint and if decide to participate to register for the sprint - link
- Dragan Ivanovic to send a require to add in the Leadership group agenda a topic for discussing Copyright owner in License
- All please help in filling this document - spreadsheet
- Dragan Ivanovic to create a draft version of a Google Spreadsheet document with labeled columns representing requirements and to share with committers
- Committers to review the structure of the document and to fill it with data for JS and CSS frameworks
