You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Call-in Information

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

Attendees

(star)  Indicating note-taker

  1. Brian Lowe  
  2. Georgy Litvinov 
  3. Ralph O'Flinn 
  4. William Welling (star)
  5. Benjamin Gross
  6. Dragan Ivanovic 
  7. Huda Khan 

Agenda

  1. Releases management
    1. Status
      1. Urgent action is needed to make VIVO 1.12.1 functional
    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
  2. 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 mostly done for 2021 PRs
      3. Should we discourage large PRs in the future?
        1. Probably not always possible
    3. Assignment of reviewers
      1. mostly 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
    6. Accepting and merging part of commits 
      1. https://github.com/vivo-project/VIVO-languages/pull/99
      2. Any strategy already defined or previous experience
        1.  https://code-maven.com/merge-one-commit-from-a-pull-request
  3. VIVO 2.0 architecture
    1. https://docs.google.com/document/d/1z51mkqlAopQ2rLkitHiQVwRojijnPM9pB8tQelW-lSA/edit?usp=sharing
    2. Presentation of VIVO 2.0 to Leadership group is expected
      1. at high level of abstraction

Notes

Draft notes on Google Drive

Actions 

Previous actions 

  • No labels