...

1. A rapid approach for VIVO in a Box - link
2. Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
3. Organizing developers and committers calls
4. JIRA vs GitHub issues
   1. "Andrew: have meeting with Tim Donahue of DSpace project. DSpace has already done a similar transition.  Will ask for feedback/advice." 2020-12-08 - VIVO Development IG
   2. Slack comment (Dragan Ivanovic) "Some of the reasons are listed here: https://spring.io/blog/2021/01/07/spring-data-s-migration-from-jira-to-github-issues#background. However, that migration might raise some issues due to different structure of JIRA issue and GitHub issue cataloguing records. Moreover, Brian already mentioned at the last developers' call that we have two GitHub projects (VIVO and VITRO), and just one JIRA tracking repository, therefore it wouldn't be always clear whether some JIRA issue should be mapped to a VIVO or VITRO GitHub issue. Also, I am not sure what will happened with notifications for people who opened the issue at JIRA at the moment when the mapped GitHub issue is closed or commented. I think we should discuss this question at the next committers call and make decision. "
   3. https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
5. 1.12.1 point release
   1. https://github.com/vivo-project/Vitro/pull/245 unit test fix
   2. release branch
6. Cleaning up CI issues on main
   
   1. Automatic snapshots https://github.com/vivo-project/Vitro/pull/242
7. Language for mapping to JSON objects
8. Georgy's proposed architecture:

9. View file
   name Architecture cur and new.pdf height 250

10. Decoupling Freemarker
11. Indexing for Scholars

Notes

Draft notes on Google Drive

Actions

•  ...

Previous Actions

...