Date

17 Jan 2023

Call-in Information

Time: 10:00 am, Eastern Time (New York, GMT-04:00)

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
    

Attendees

 Indicating note-taker

1. Dragan Ivanovic 
2. Georgy Litvinov  
3. Brian Lowe   
4. Huda Khan 
5. William Welling 

Agenda

• Questions/Issues/Pull requests/Announcements
  • The issue with calendars
  • The support link
    • https://github.com/vivo-project/VIVO/issues/3809
  • PRs
    • https://github.com/vivo-project/VIVO/pull/3808
    • https://github.com/vivo-project/Vitro/pull/360
• The i18n redesign sprint
  • Documentation needs update - Internationalization
• The VIVO community and developers engagement meetings
  • VIVO demo meeting
    • VIVO 1.14.0
• Publishing VIVO 1.14.0 release
  • We will start that after merging of i18n branch into main branch 
    • architecture improvements
      • archiving VIVO-languages and Vitro-languages
    • i18n improvements
    • performance improvements
    • faux data properties
• The next sprint
  • When
  • The topic

Notes

1. New PRs
1. PR-360 Regression fix
   Georgy: We might merge it after merging i18n-redesign in Vitro repository
2. Dragan: I am going to review this PR at the beginning of the next week
2. Calendars
1. Dragan: I will investigate inaccuracy in calendars invitations.
2. William: I got that invitation from vivo-survey@gmail.com
3. Dragan: Who could be that person?
3. New issues
1. Dragan: Christian opened an issue about broken support link in vivo web interface. This link is in ftl file and now it doesn’t work.
   I will try to find out if that can be fixed. I am not sure if this approach is good at all.
4. Documentation for i18n
1. Dragan: I started working on the documentation. 
2. I had one specific question: there was i18nChecker, is it possible to suggest alternatives for that?
3. Dragan: Adding new languages now is simplified. You just have to replace language tags and translate the labels.
5. Dragan: A month ago we started discussion about new vivo release demonstration. Will see how successful it would be. VIVO instances registry might be updated soon. Once we are ready for release I am going to announce pre release meeting.
   We might organize meetings with users each month.
6. Georgy: Can I prepare a couple of PRs for fixes in custom entry forms?
   Dragan: We don’t have a strict schedule, so that shouldn’t be a problem.
7. Dragan: I hope we will be able to publish a new release soon.
8. Questions for the next sprint:
   1. 13.02.23 - 24.02.23  ?
   1. Preparation for Jena upgrade (our Jena version is outdated), also it might be nice to clean up SDB code
   2. Ingestion and exporting of the data
   3. External triple store performance improvements (Michel)
1. When?
2. Main topic?
9. Improve vivo-solr repository: 
1. Make it appear in pinned repositories
2. Have synced release or move it is configuration into main repositories.

Draft notes in Google Docs

Task List

Previous Tasks 

• 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
  • https://github.com/vivo-project/VIVO/issues/3698
• 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