...

1. Brian Lowe
2. Dragan Ivanovic     
3. Benjamin Kampe     
4. Georgy Litvinov 
5. Dominik Feldschnieders 
6. Ralph O'Flinn Benjamin Gross 
7. William Welling 
8. Michel Héon 
9. Veljko Maksimovic
10. Huda Khan  
11. Naveen Sadhu
12. Matthias Lühr 
13. Andreas Czerniak

Agenda

1. Announcement(s) 
   1. JIRA has been moved in read-only mode, issues were migrated to GitHub issues. Please report all new issues at https://github.com/vivo-project/VIVO/issues
2. The new issues/questions
   1. https://vivo-project.slack.com/archives/C8RL9L98A/p1633128258060400 
      1. https://docs.google.com/document/d/1P6e5I1uKZXekmnnxreZ1Tgky3-qToUDMSs3AH2jzHDA/edit?usp=sharing
3. Discussion about priorities for further development of VIVO - https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
   1. The topic will be i18n
      1. Leftover i18n tasks - nonblockers from 1.12 (vocabulary services / form improvements)
         1. https://github.com/vivo-project/VIVO/issues/3541
         2. https://github.com/vivo-project/VIVO/issues/3540
         3. https://github.com/vivo-project/VIVO/issues/3527
         4. https://github.com/vivo-project/VIVO/issues/3522
         5. https://github.com/vivo-project/VIVO/issues/3507
         6. https://github.com/vivo-project/VIVO/issues/3466
         7. https://github.com/vivo-project/VIVO/issues/3475
      2. Move i18n properties from resource bundles to ontology / (editable) RDF
      3. Find solution for syntax differences between languages that does not require template customization per language 

Notes

1. Announcement(s) 

JIRA has been moved in read-only mode, issues were migrated to GitHub issues. Please report all new issues athttps://github.com/vivo-project/VIVO/issues

2. 1. During migration, not always possible to capture the links but Dragan has tried to add links manually where possible.
   2. We can check to make sure we should not be able to add/edit/assign issue

3. The new issues/questions

1. Have Naveen with us. Reported issue on slack and discussed issue with Brian. 

2. JIRA has been moved in read-only mode, issues were migrated to GitHub issues. Please report all new issues athttps://github.com/vivo-project

   .slack.com

   /

   archives/C8RL9L98A/p1633128258060400 

   VIVO/issues

4. The new issues/questions

   1. https://docs.google.com/document/d/1P6e5I1uKZXekmnnxreZ1Tgky3-qToUDMSs3AH2jzHDA/edit?usp=sharing 

   2. Using VIVO 1.10.
   1. When subject is being added to academic article, its inverse property is not being added (i.e. subject “subjectAreaOf” academic article on the subject entity)
   2. Use harvester transfer tools to populate models
   3. Inverse relationships are not being added
   4. Populates sometimes but it doesn’t for the articles
   3. Brian: When loading data for add/remove rdf, inferred triples do show up.
      1. Not bringing up additional inferences that were expected
   1. Ran inference from VIVO site admin to recompute inferences?
1. Not bringing up additional inferences that were expected
5. 1. Naveen: Considering adding some debug messages to track what is going on
   2. Huda: Error messages in log when doing recompute through site admin?
   1. Naveen: No. Vivo.all.log looks clean.
   2. Huda: Debug might be the best option.  Also assuming statements are being 
   3. Naveen: Is there something about the harvester?
   1. Brian: Not familiar enough with that tool, but if you’re querying for the triples that should be causing the inference and finding them, unclear why inference is not being added then
   4. Brian: Can we get RDF that is being added so we can try it out?
   1. Naveen: Will try debug and can continue discussion on slack
   5. Huda: Maybe add single statement through harvester and query for which graphs statement is present in and then do the same through rdf add directly through VIVO to check if there is a difference in which graphs have the statement
   PRs on VIVO and Vitro
1. Have Naveen with us. Reported issue on slack and discussed issue with Brian. 

2. https:/

   /github.com

   /vivo-project

   /Vitro/pulls and https://github

   .slack.com/

   vivo-project

   archives/

   VIVO

   C8RL9L98A/

   pullsRalph: Branch rel-1-12 alpha

   p1633128258060400 

6. PRs on VIVO and Vitro

   1. Has main fixes for this to be buildable in GitHub
   2. About to generate snapshot
   3. At that point, everything should work in GitHub and become base for next release
   4. Other PRs out there in VIVO and Vitro that are legacy.
   5. On committers’ call, probably should go back through these to see which should be merged or not.  Need some finalized decisions
1. https://github.com/vivo-project/Vitro/pulls and https://github.com/vivo-project/VIVO/pulls
2. Ralph: Branch rel-1-12 alpha

7. Discussion about priorities for further development of VIVO -https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing

The topic will be i18n

8. 1. Leftover i18n tasks - nonblockers from 1.12 (vocabulary services / form improvements)

9. https://github.com/vivo-project/VIVO/issues/3541

10. 1. 1. Analyze whether we want to include this in milestone 1.13/1.14 or postpone for later phase
       2. Ralph: Are we deciding that these are important for a release or roll them as we go?
       3. Dragan:Classify when we should plan on working on these.  Before we start working, we can then discuss blocking issues.
       4. William: For scheduling, need a better sense of sprint schedule
       5. Dragan: Estimation of human resourcing and complexity of problem
       6. Dragan: Sprint cycles: 2-3 weeks. Does that matter?
       7. William: Need a board where people identify which issues are priorities/need to be worked on
       8. Ralph: On sprints, did them successfully with i18n endeavour.  Two things that made it successful: Strong backer with Michel’s group and also well-scheduled in advance.  Allowed people to schedule well in advance.
       9. Dragan: Working towards a bigger goal instead of just specific bugs?
       10. Ralph: Bigger goal helps but don’t want to prevent people from working on smaller goals
       11. Dragan: Bugs as well during sprints?
       12. Ralph: both
       13. William: In context of larger sprint goals, but fine to work on bugs.  Also, scheduling is important
       14. Ralph: Even if just saying bug fix but introducing higher level topic later, need to get on schedule
       15. Dragan: Number of sprints and number of releases? 
       16. William: Not good to align sprint with release.  Releases should be on a schedule i.e. time-based
       1. Hard to do regular sprints because don’t have allocated effort
       2. Still, a regular schedule means people can anticipate when to ask for time 
       17. May be beginning to agree on: two week sprints every two months
       18. Michel: Testing sprint schedule at UQaM.  1 week sprint is too short.  First week = appreciate what we have to do inside sprint.  Two weeks = no time to test what was done.  Best range = Three weeks, but problem is that’s too long. Three weeks between sprints.  Two weeks = active, next week = retrospective. 
       19. Now voting on three week sprints instead

    1. https://github.com/vivo-project/VIVO/issues/3541

    2. https://github.com/vivo-project/VIVO/issues/3540

    3. https://github.com/vivo-project/VIVO/issues/3527

    4. https://github.com/vivo-project/VIVO/issues/3522

    5. https://github.com/vivo-project/VIVO/issues/3507

    6. https://github.com/vivo-project/VIVO/issues/3466

    2. Move i18n properties from resource bundles to ontology / (editable) RDF

    3. Find solution for syntax differences between languages that does not require template customization per language

1. The topic will be i18n

2. Note, migration from JIRA to GitHub assigns the person who migrated the issues as creator.  The first line in the description will indicate original reporter of issue.  Issue will also link to original read-only JIRA issue.

...