...

1. Dragan Ivanovic 
2. Georgy Litvinov 
3. William Welling 
4. Kevin Day 
5. Michel Héon 
6. Brian Lowe 

...

1. Goals:

   1. Surface any fundamental issues

2. Sprint logistics / scheduling

   1. Daily stand-up report in Slack - #sprint-feb-2023
   2. A bi-daily meeting (Monday, Wednesday, Friday) at 10am Eastern Time (4pm CEST)
3. Tools and resources 
   1. Branches
      1. https://github.com/vivo-project/VIVO/tree/semantic-web
      2. https://github.com/vivo-project/Vitro/tree/semantic-web
      3. https://github.com/vivo-project/VIVO/tree/infrastructure-improvements
      4. https://github.com/vivo-project/Vitro/tree/infrastructure-improvements
   2. Dev environment... please take as first task to establish this

4. Tickets

   • https://github.com/orgs/vivo-project/projects/5
   • https://github.com/orgs/vivo-project/projects/6
5. Tracks

Notes 

Dragan informed the participants about created branches and project boards.

Firstly, discussion about https://github.com/orgs/vivo-project/projects/6 project board tickets was done:

• Tickets are grouped in tracks.
• The issue https://github.com/vivo-project/VIVO/issues/3698 can be resolved in two ways:
• By documenting solution with using AJP proxy for reverse proxy
• By introducing optional runtime property base url, and using that property for making email absolute links (if the property exists).
• The issue https://github.com/vivo-project/VIVO/issues/3062 might be resolved by using VIVO third-tier build project - https://github.com/vivo-community/vivo-custom-webapp
• We should check whether the issue https://github.com/vivo-project/VIVO/issues/3744 still exists. It should be a smoke test warning.

Discussion about https://github.com/orgs/vivo-project/projects/5/ project board tickets:

• Tickets are grouped in tracks.
• The issue https://github.com/vivo-project/VIVO/issues/3824 
• We might try to speed up http communication by using some contemporary libraries
• Frequency of firing SPARQL queries should be optimized (all requested data for one page in one SPARQL query instead of many SPARQL queries)
• We might consider using Solr for fetching information in some cases
• Upgrade to Jena 4 (https://github.com/vivo-project/VIVO/issues/3829) requires using JDK 11+
• Should we use JDK 11 or JDK 17. The last one is long term solution, but it might be a problem for some existing VIVO instances set up at some server infrastructures

Georgy also suggested two additional issues which might be topic in this sprint. Dragan suggested that everyone check descriptions of all project boards’ tickets, provide feedback if something is missing or should be additionally discussed, and think about their preferences to participate in resolving some issues. We will continue discussion in the next two days, and after that start assigning tasks and implementation. 

Draft notes on Google Drive

...