Date

13 Jan 2022

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. Georgy Litvinov 
3. Ralph O'Flinn 
4. William Welling
5. Benjamin Gross
6. Dragan Ivanovic 
7. Huda Khan 

Agenda

1. Releases management
   1. Status
      1. Making VIVO 1.12.1 functional
         1. https://github.com/vivo-project/VIVO/pull/3611 
   2. Next steps
      
      1. We are switching to time-based publishing releases process, therefore we need
         1. Efficient process
         2. Well documented
         3. More members capable to do that as a backup solution if Ralph is not available
         4. Possible solutions
            1. Docker container for preparation of a release
            2. Pair deployment / preparation of a release
2. Improvement of contribution process
   1. Contributor License Agreements ???
      1. Do we want that?
         1. https://opensource.com/article/19/2/cla-problems
      2. Optionally?
   2. Contributing code with a fork, branches, and pull requests
   3. discourage large PRs
      1. Probably not always possible
      2. PR templates updated
         1. https://github.com/vivo-project/VIVO/blob/main/.github/PULL_REQUEST_TEMPLATE.md
         2. https://github.com/vivo-project/VIVO/wiki/Development-Processes

3. Moving forward reviewing PRs on VIVO and Vitro

   1. https://github.com/vivo-project/Vitro/pulls and https://github.com/vivo-project/VIVO/pulls
   2. Tiny and big PRs classification
      1. labels - small, middle, large PR
      2. assignments of labels done for 2021 PRs
   3. Assignment of reviewers
      1. done for 2021 PRs
      2. please, check and inform me if you are available and willing to perform review (and provide some estimation when that can happen)
   4. Using slack and core committers meetings for pre-reviewing discussion and reporting
   5. How to proceed with old PRs
      1. contributors are not active anymore in the VIVO community
      2. merging conflicts
         1. organization of repository might be changed
4. Add Spring/Spring Boot in VIVO
   1. There is some progress
   2. It should enable easy running and debugging of the VIVO application

Notes

Draft notes on Google Drive

Actions 

Previous actions 

• Ralph O'Flinn to resolve missing i18n directory issue in VIVO 1.12.1 release
• Dragan Ivanovic to update PR template to discourage large PRs or at least to ask contributor for reason why it is necessary to have large PR
• Dragan Ivanovic to help Ralph in resolving publishing releases issue. Also, to try to improve documentation. 
• Dragan Ivanovic to assign PRs to reviewers (committers)
• Later, we can improve contribution policy, including closing PR with inactive PR creators (who didn't responded on comments). We should also consider introducing Contributor license agreements in the process - link 
• All to read and provide feedback for   VIVO 2.0 architecture https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing