Date
Call-in Information
Time: 11:00 am, Eastern Time (New York, GMT-04:00)
Attendees
Indicating note-taker
Agenda
- A rapid approach for VIVO in a Box - link
- Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
- Organizing developers and committers calls
- JIRA vs GitHub issues
- "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
- 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. "
- https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
- 1.12.1 point release
- https://github.com/vivo-project/Vitro/pull/245 unit test fix
- release branch
- Cleaning up CI issues on main
- 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
Notes
- A rapid approach for VIVO in a Box - link
- Corrections of wiki pages - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
Dragan:
Work on Jira Wiki pages
MySQL is no longer default? In 1.12 is TDB
Link in license to wrong branch
Organizing developers and committers calls
- Organizing developers and committers calls
Georgy:
Try not to change developer meeting time.
Need to have known time for new developers/implementers.
Propose to make meetings one after another.
Dragan:
Developer/Implementer calls should be two way. Update from committers and feedback/ideas from non-committers.
Developers call each Tuesday for the first 30+ minutes. Will be followed, if time permits, by committer call. If the committer call requires more time a meeting will be scheduled for that Thursday.
What time should we have for the meeting?
Bryan: can times alternate from week to week?
Dragan will send out a doodle pool to see if there is any interest in certain times.
- JIRA vs GitHub issues
- "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
- 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. "
- https://docs.google.com/spreadsheets/d/1Cl-aCe1he0DPwd1gScjx2Oi80lUX8W_3nE4UlzpEwI0/edit?usp=sharing
Dragan:
pros/cons?
Semi automatic migration from JIRA to GitHub with experts to separate between Vitro, VIVO, languages.
- 1.12.1 point release
- https://github.com/vivo-project/Vitro/pull/245 unit test fix
- release branch
Waiting on release 1.12.1 for merging.
- Cleaning up CI issues on main
- Automatic snapshots https://github.com/vivo-project/Vitro/pull/242
Should we have the snapshots published on main of each repo. VIVO currently has this integration but often depends on Vitro, VIVO-languages, and Vitro-languages being published.
Dragan:
Any form of assignment to peer review?
Self assigned and sometimes influenced.
Any current sprint?
Not currently, waiting for a list of issues to be groomed.
- Language for mapping to JSON objects
Brian:
Allow for common entity shape for ingest and retrieval side. How to map to graph/sub graph for individual/list views/forms? N3 with bound variables used for forms and mapped in/out?
Dragan:
Could open up for wider adoption to afford use without knowledge of semantic web technologies.
Apache Marmotta LDPath syntax https://marmotta.apache.org/ldpath/language.html
JSON-LD framing: https://www.w3.org/TR/json-ld11-framing/
RMLMapper - https://github.com/RMLio/rmlmapper-java , example: https://github.com/RMLio/rml-fno-test-cases/tree/master/RMLFNOTCAB0007-JSON
Actions
- Dragan Ivanovic to create a doodle poll with time slots options for Tuesday developers/implementers calls
- Dragan Ivanovic to correct wiki documentation - https://docs.google.com/spreadsheets/d/19mSk6xSRm-ogCJisMZ6ao2X2Qi8Z9T3TxZjBzVVr8yk/edit?usp=sharing
- Dragan Ivanovic to draft a roadmap (methodology) for migration from JIRA to GitHub issues
Previous Actions
- Brian Lowe to draft initial sketch of "VIVO2" in a Google Doc
- Huda Khan to review:
- Brian Lowe to review:
- Ralph O'Flinn to review:
