...
Indicating note-taker
...
- A brief update from VIVO leadership meeting
- representative of a committers' group
- Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
- A roadmap to migration from JIRA to GitHub issues - https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
- Analyze available tools
- Adopt/customize https://github.com/rstoyanchev/jira-to-gh-issues for our solution
- Test/validate migration - https://github.com/chenejac/VIVOTestMigrationJIRA/issues - Action needed!!!
- 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
- 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
- Run migration into the production (https://github.com/vivo-project/VIVO).
- Create GitHub issues templates ( https://github.com/vivo-project/VIVO) - An action needed
- Georgy's proposed architecture:
View file name Architecture cur and new.pdf height 250 - Decoupling Freemarker
- Indexing for Scholars
...