Versions Compared

Key

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

...

(star)  Indicating note-taker

  1. Brian Lowe     
  2. William Welling 
  3. Huda Khan (star)
  4. Georgy Litvinov
  5. Dragan Ivanovic  

...

  1. A brief update from VIVO leadership meeting
    1. representative of a committers' group
  2. Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
  3. 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
      1. https://github.com/rstoyanchev/jira-to-gh-issues  ←
      2. https://github.com/susinda/github-client
      3. https://github.com/hbrands/jira-issues-importer
    2. Adopt/customize https://github.com/rstoyanchev/jira-to-gh-issues for our solution
    3. Test/validate migration - https://github.com/chenejac/VIVOTestMigrationJIRA/issues - Action needed!!!
    4. Map JIRA (https://vivo-project.atlassian.net/jira/people/search) and GitHub accounts (https://github.com/orgs/vivo-project/people). The mapping is defined here: https://docs.google.com/document/d/1SKRMuky8x8m9CgOKtxs16LWFuuVfYlQR6LkjASBEzrI/edit?usp=sharing Action needed
    5. Add labels at https://vivo-project.atlassian.net/jira/ for distinction of VIVO and VITRO issues? Do we need this? If do, an action needed
    6. Run migration into the production (https://github.com/vivo-project/VIVO).
    7. Create GitHub issues templates ( https://github.com/vivo-project/VIVO) - An action needed
  4. Georgy's proposed architecture:
  5. View file
    nameArchitecture cur and new.pdf
    height250
  6. Decoupling Freemarker
  7. Indexing for Scholars

...