...

1. Brian Lowe  
2. Dragan Ivanovic 
3. Georgy Litvinov
4. William Welling
5. Huda Khan
6. Benjamin Gross    

Agenda

1. A roadmap to migration from JIRA to GitHub issues - https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
   1. Analyze available tools
      - https://github.com/rstoyanchev/jira-to-gh-issues(adopted as solution)
      - https://github.com/susinda/github-client
      - https://github.com/hbrands/jira-issues-importer
      - done
   2. Adopt/customize https://github.com/rstoyanchev/jira-to-gh-issues for our solution
      - Done - https://github.com/chenejac/jira-to-gh-issues
   3. Test/validate migration
      - https://github.com/chenejac/VIVOTestMigrationJIRA/issues
      - I didn't receive any complaints from the group, therefore I suppose this is done as well
   4. Map JIRA (https://vivo-project.atlassian.net/jira/people/search) and GitHub accounts (https://github.com/orgs/vivo-project/people).
      - Done - The mapping is defined here: https://docs.google.com/document/d/1SKRMuky8x8m9CgOKtxs16LWFuuVfYlQR6LkjASBEzrI/edit?usp=sharing 
   5. Add labels at https://vivo-project.atlassian.net/jira/ for distinction of VIVO and VITRO issues?
      - Should discuss if we need this
      - I think we shouldn't spend our time on this, because I don't see some benefits of splitting issues per projects. I think we should migrate everything under the VIVO repository, but enable reporting new bugs/issues for all four repositories (VIVO, VITRO, VIVO-languages, VITRO-languages) in the future. Whatever we decide now for the migration, I am quite sure some new issues in the future will be reported in wrong github repository.
   6. Run migration into the production (https://github.com/vivo-project/VIVO ).
   7. Create github issue templates
      - Done, please check - https://github.com/vivo-project/VIVO/issues/new/choose

...

Draft notes on Google Drive

Actions 

•  All to validate result Dragan Ivanovic to run tool for migration of JIRA issues to GitHub Issues migration tool before it is run into operation - https://github.com/chenejac/VIVOTestMigrationJIRA
•  Dragan Ivanovic to correct wiki documentation - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
•  Dragan Ivanovic to work on priorities' google sheet document
• issues correct wiki documentation 

Previous Actions

•  Brian Lowe to draft initial sketch of "VIVO2" in a Google Doc
•  Huda Khan to review: 

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

•  Brian Lowe to review: 

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

•   Ralph O'Flinn to review: 

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