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
- Georgy Litvinov
- Ivan Mrsulja
- Benjamin Kampe
- Maxim Prokopenko
- Samantha Emerson
- B. Henderson
- Mei M
- Rishabh Tatiraju
- Kshitij Sinha
- Christopher P. Barnes
Agenda
- Questions/Issues/Pull requests/Announcements
- VIVO release candidate number 2
- email.replyTo property
- Permissions for vivo_home
- Dynamic API PR
- Dump-restore script
- Improvement of building process
- The sprint
- Plan for the next sprint
- continuation of the previous sprint or
- some other topic
- date
- May 22nd - June 9th, 2023 ???
- Plan for the next sprint
Notes
- VIVO release candidate number 2
Dragan: I announced the release of new release candidate. Ivan tested the candidate. Survey questions improved to be more self-explainable. Issue with rdfs:Literal.
- email.replyTo property
Dragan: one email is used for 2 cases, it needs to be split in installation
Georgy: Was it anticipated that these emails should receive something. Usually you can create email for vivo, technical email, and in email configuration you can specify that all incoming mail can be redirected to another account.
Dragan: I’m not sure, i will try to investigate further with the original comment author
- Permissions for vivo_home
Dragan: I received a message about not having permission to write something in vivo_home, in the end it was a problem with tomcat9 on Debian (default settings) but it has been resolved.
Brian: add something about this in documentation
Dragan: I will try to add a few sentences in documentation
- Dynamic API PR
Dragan: Big new PR merged in Dynamic API branch
- Dump-restore script
Dragan: i’m not sure where scripts should be located. Due to .gitignore it is not possible for bin directory to be created, we should think about this. Should it be packet somehow in vivo_home.
- Improvement of building process
Dragan: William worked on this pull request. Is it possible to find more information about installation of vivo instances around the world. Maybe make a google form so admins can enter data about upgrading, deployment etc. of their vivo instance.
- The sprint
Dragan: Maybe complete migration to Jena4, continue where the last sprint stopped. Sometime ago we created plan for releases and sprints, not accurate, only a rough plan, but maybe that can be an inspiration for the topic of next sprint. Maybe work on external graph, research how exactly we can realize that. Authorization roles, Georgy would like to work on that. Document about issues is created, everyone is welcome to add comments, especially new members if they think some feature needs to be included in their organisation (add priority if possible).
Dragan: Maybe move more in DynamicAPI branch, we will discuss about it more in the next DynamicAPI meeting. Around May 22. - June 9. should be the beginning of sprint. You should check your availability for that period and discuss it in the next weekly meeting.
Brian: Does it make sense to see what should we do in the meantime, continuously (week-to week), preferably on Jena4 transition and SPARQL endpoints.
Dragan: Everyone should think about this, it would be great if someone can make progress on those branches. It will be nice to know exact sprint start date around 3 weeks before. Everyone should check their agenda about this. Next week we return in the normal meeting time: 10AM Eastern time.
Task List
Previous Tasks
- Dragan Ivanovic to announce publishing VIVO 1.14.0 RC2
- someone to test RC2
- Ivan Mrsulja tested RC2
- Dragan Ivanovic to create survey for collecting standard practice in VIVO deployment process
- 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
