Date

07 Oct 2021

Call-in Information

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

• Join Zoom Meeting
  https://lyrasis.zoom.us/j/81398228834?pwd=SE0wdFN3NnFVbEhYVUhuM3BtQmVUQT09

  Meeting ID: 813 9822 8834
  Passcode: 728426

Attendees

 Indicating note-taker

1. Brian Lowe  
2. Dragan Ivanovic 
3. Georgy Litvinov
4. William Welling  

Agenda

1. 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
      - https://github.com/rstoyanchev/jira-to-gh-issues (adopted as solution)
      - https://github.com/susinda/github-client
      - https://github.com/hbrands/jira-issues-importer
      - done
   2. Adopt/customize https://github.com/rstoyanchev/jira-to-gh-issues for our solution
      - Done - https://github.com/chenejac/jira-to-gh-issues
   3. Test/validate migration
      - https://github.com/chenejac/VIVOTestMigrationJIRA/issues
      - I didn't receive any complaints from the group, therefore I suppose this is done as well
   4. Map JIRA (https://vivo-project.atlassian.net/jira/people/search ) and GitHub accounts (https://github.com/orgs/vivo-project/people ).
      - Done - The mapping is defined here: https://docs.google.com/document/d/1SKRMuky8x8m9CgOKtxs16LWFuuVfYlQR6LkjASBEzrI/edit?usp=sharing  
   5. Add labels at https://vivo-project.atlassian.net/jira/ for distinction of VIVO and VITRO issues?
      - Should discuss if we need this
      - I think we shouldn't spend our time on this, because I don't see some benefits of splitting issues per projects. I think we should migrate everything under the VIVO repository, but enable reporting new bugs/issues for all four repositories (VIVO, VITRO, VIVO-languages, VITRO-languages) in the future. Whatever we decide now for the migration, I am quite sure some new issues in the future will be reported in wrong github repository.
   6. Run migration into the production (https://github.com/vivo-project/VIVO ).
   7. Create github issue templates
      - Done, please check - https://github.com/vivo-project/VIVO/issues/new/choose

Future topics

1. Prioritizing and planning post-1.12 development
2. Forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
3. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
4. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
5. Incremental development initiatives
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

1. Migration to GitHub

We should move issues to VIVO repository first. From Dragan’s point of view it is logical to have issues in this repository. In other repositories it could be confusing for users.

Where should we open issues after that? 

For the people it is hard to understand where the issue belongs - to VIVO, Vitro, Vitro-languages or VIVO-languages. 

William: We could transfer issues to other repositories on Github later.

Dragan: The point is when a user reports some bug you should describe your environment. Can you check Github standard templates for bug reports and feature requests?

Brian: If there is no activity in issues of current repositories users could think that repositories are archived and not supported.

Conclusions:

• Migrate issues to VIVO
• Not open issues for other repositories for now (Vitro, VIVO-languages, Vitro-languages). For now keep issues in VIVO repository only.
• We should change wiki pages about issues

2. Side note about Vitro and VIVO relation

William: Why are VIVO and Vitro in separate repositories? The application shouldn’t define the dependency.

Dragan: Reengineering of VIVO is an interesting question. 

VIVO is one application for Vitro in the research domain.

By and large most people don’t understand the distinction. 

Questions from William:

How many people are using Vitro?

How many applications also depend on Vitro?

William: It is very difficult to coordinate the build of VIVO and Vitro.

Ontologies and templates should have their own library. 

Instead, dependencies look strange.

3. Discussion about VIVO 2.X architecture. 

We could shape the idea of new architecture in committers group for two weeks and then move discussion to the developers group.

Draft notes on Google Drive

Actions 

• Dragan Ivanovic to run tool for migration of JIRA issues to GitHub issues correct wiki documentation 

Previous Actions

• 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.