...

1. Benjamin Gross 
2. Andrew Woods
3. Brian Lowe 
4. Ralph O'Flinn 
5. Huda Khan 
6. Michel Héon 
7. Alexander (Sacha) Jerabek  Mike Conlon
8. Don Elsborg

Agenda

1. Announcements
   1. Dev meeting change in frequency?
   2. Initial Selenium test framework verified

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1424

2. Performance testing different VIVO / triple store configuration - take #2 (no inferencing)
   1. Performance Testing

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1743

      2. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1744

3. 2020 Sprint Planning- VIVO Sprints
   1. VIVO-i18n - Canadian French Initiative
   2. Dates: Apr 6th - 17th
4. 1.11.1 maintenance release - security patch
5. Vitro JMS messaging approaches
6. VIVO Scholar - Docker setup
7. Vitro pull-requests

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1658

       - looks good

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1700

...

Draft notes in Google-Doc

1. Announcements:
   1. Discussion about frequency of meetings, would help to move development of software, move to bi-weekly or monthly in exchange for work to move the project forward.
   2. Rf: meetings serve to keep everything and everyone on track
   3. Mh: do we have a meeting to prepare the sprint?
   4. Aw: there is usually a kickoff, but ideally more meetings in advance to organize things before starting the sprint.
2. Selenium testing: 
   1. AW has tried this out with a plugin for a browser session with Vivo, Selenium generates Java (or Ruby) code based on activity and then gets dumped into testing code base, which you can then use to adapt and test. Testing can take some time however if you have to bring Vivo down and wipe it each time you run the test.. AW will document the process and see if it is interesting to implement to integrate into current Travis/Jira workflow. Can create the test in Chrome and then run in Firefox. Would help with dev work on i18n to make sure we don’t break anything. With its own GitHub repository.
3. Performance testing different VIVO / triple store configurations - take #2 (no inferencing)
   1. AW has documented ingest tests, which methods are taking the most amount of time, and then to determine if and how to optimize the calls. [discussion about various aspects of setting up the tests...indexing and inferencing turned off, lower startup costs,].Will give a clear picture of performance now so that as we make changes we have a baseline against which to compare. DE will spin up dockers and run tests with different configurations.
   2. See: Procedures and results being documented on the wiki: https://wiki.lyrasis.org/display/VIVO/Performance+Testing

Actions