...
- Dragan Ivanovic
- Brian Lowe
- Michel Héon
- Georgy Litvinov
- Mark Vanin
- Ivan Mrsulja
- Benjamin Kampe
- Maxim Prokopenko
- Samantha Emerson
- B. Henderson
- Mei M
- Rishabh Tatiraju
- Kshitij Sinha
- Christopher P. BarnesMiloš Popović
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.
...