Date

25 Feb 2020

Call-in Information

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

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Benjamin Gross 
2. Andrew Woods
3. Brian Lowe 
4. Ralph O'Flinn 
5. Huda Khan 
6. Steven McCauley
7. Michel Héon
8. Alexander (Sacha) Jerabek 
9.  Nicolas Dickner
10. Rachid Belkouch

Agenda

1. Announcements
   1. VIVO Triple Store Roadmap Proposal - communication with community regarding moving forward with the plan
   2. Symplectic's Harvester... now open source, what next?
2. 2020 Sprint Planning
   1. VIVO-i18n - Canadian French Initiative
3. Performance testing different VIVO / triple store configuration
   1.   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Fuseki as alternate triple store
4. Pruning legacy Vitro/VIVO GitHub branches

   In an effort to reduce the number of abandoned or out-dated branches in the VIVO and Vitro GitHub repositories, we will be taking a multi-phased approach at pruning branches:
   
   - All branches that predate the VIVO 1.6 release will be removed (i.e. all branches from 2013 and before)
   - Of the remaining branches, those with no commits ahead of the 'master' branch will be removed
   - Of the remaining branches, detailed review of branch content will determine whether the branch should be removed/retained
   - Release maintenance branches will be retained
   
   If you have an interest in ensuring that any of the branches in Vitro or VIVO are retained, please let that be known.

5. 1.11.1 maintenance release - security patch
6. Vitro pull-requests
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - looks good

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Draft notes in Google-Doc

Actions