Versions Compared

Old Version 2

changes.mady.by.user Michel Héon

Saved on

compared with

New Version Current

changes.mady.by.user Dragan Ivanovic

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

(star)  Indicating note-taker

  1. Brian Lowe
  2. Georgy Litvinov
  3. William Welling 
  4. Huda Khan (star)Alexander (Sacha) Jerabek 
  5. Dragan Ivanovic 
  6. Sandra MierzBenjamin Gross 
  7. Michel Héon 
  8. Benjamin Kampe 
  9. 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