Date

31 Aug 2021

Call-in Information

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

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• 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. Brian Lowe
2. William Welling 
3. Huda Khan  
4. Dragan Ivanovic 
5. Benjamin Gross 
6. Michel Héon 
7. Benjamin Kampe 
8. Matthias Lühr 

Agenda

1. A brief update about VIVO core development
2. Update/questions from implementers

Notes

Dragan: Trying out this new format.  First part to be devoted to central development/committer issues.  Second part of the meeting should be questions and comments and new issues arising for developers and implementers. 

Introductions:

Matthias Luhr: Implementing in VIVO.  Participated in last development sprint. 

Michel Heon: UQAM.  Needs to be VIVO leader inside UQ community.  Strategy: When making VIVO development, share that information with the VIVO community.  

Dragan: Want to make community bigger and motivate more people to participate in these meetings.  Some text document to react to might help motivate people to discuss.

1. A brief update about VIVO core development
   1. Logistics: When to have this meeting? Doodle poll was sent out, probably will be moved on Tuesday 9am or 10am ET. 
   2. Development priorities/tasks
      1. Michel:  We started the dev priorities spreadsheet; should finish this so that we know what is coming in versions 13, 14, etc.  
2. Update/questions from implementers
   1. Michel: Why are we moving JIRA to GitHub?
      
      1. Dragan: Software acquired.  Developers see benefits using GitHub.  There was no big problem with JIRA specifically.  
      2. William: JIRA is not broken but inefficient to have issue management in two separate places, linking GitHub issues back to JIRA.
      3. Dragan: Repo showing migration of issues from JIRA to GitHub - https://github.com/chenejac/VIVOTestMigrationJIRA/issues
      4. Michel: More flexibility with respect to project management in JIRA than GitHub.  Don’t particularly like JIRA (complicated) but is powerful.  Useful for geographically distributed team. 
      5. Benjamin (from chat): I'm not sure if we're really using the advanced features of Jira though.
      6. Brian: Atlassian offered free hosting for cloud service for open source.  New JIRA that Lyrasis has migrated to is now completely free.  

Draft notes on Google Drive

Task List

•  Dragan Ivanovic to work on priorities spreadsheet and open it for discussion at following meetings