Date

19 Aug 2021

Call-in Information

Time: 11:00 am, Eastern Time (New York, GMT-04:00)

Indicating note-taker

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. "
Merging developers and committers calls?
1.12.1 point release
1. https://github.com/vivo-project/Vitro/pull/245 unit test fix
2. release branch
Cleaning up CI issues on main
1. Automatic snapshots https://github.com/vivo-project/Vitro/pull/242
Language for mapping to JSON objects
Georgy's proposed architecture:
Decoupling Freemarker
Indexing for Scholars

Brian Lowe to draft initial sketch of "VIVO2" in a Google Doc
Huda Khan to review: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Brian Lowe to review: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Ralph O'Flinn to review: Unable to locate Jira server for this macro. It may be due to Application Link configuration.