Date

Call-in Information

Time: 10:00 am, Eastern Standard Time, or 4:00 pm, Central European Time

Attendees

(star)  Indicating note-taker

  1. Dragan Ivanovic (star) 
  2. Georgy Litvinov   

Agenda

  1. VIVO 1.15.0
    1. https://github.com/vivo-project/VIVO/milestone/30
    2. Open PR
      1. I forgot my password
        1. https://github.com/vivo-project/Vitro/pull/421
        2. https://github.com/vivo-project/VIVO/pull/3916
        3. Georgy to review
      2. Avoid lock on graph uri update in RdfServiceSparql
        1. https://github.com/vivo-project/Vitro/pull/424
        2. Ivan to review
      3. Individual access objects
        1. https://github.com/vivo-project/Vitro/pull/433
        2. https://github.com/vivo-project/VIVO/pull/3930
        3. Ivan to review
      4. Search sort options
        1. https://github.com/vivo-project/Vitro/pull/431,
        2. https://github.com/vivo-project/VIVO/pull/3928
        3. Milos to review
      5. robots.txt
        1. https://github.com/vivo-project/VIVO/pull/3936
        2. https://github.com/vivo-project/Vitro/pull/438
    3. Wiki documentation
      1. Extended search
      2. I forgot my password
      3. ABAC
        1. Authorization
      4. Audit tool
        1. The VIVO audit module
      5. SPARQL Update API 
      6. Wilma theme
      7. Private individual page
        1. Private individual pages
      8. Release note
      9. Installation

Notes

I forgot my password

Georgy and Dragan discussed concerns about a system's security and potential issues related to memory usage. They also discussed the implications of a potential attack on the system's captcha and the need for alternative options to mitigate this risk. 

Improvements in code reviewing

Georgy and Dragan discussed the importance of thorough code reviews and testing before integrating new features. They agreed on the need to address issues and resolve them before moving forward. They also discussed the current state of code reviews, where reviewers often focus on syntax checks rather than detailed testing and fully understanding of the implemented approach. Georgy emphasized the importance of manual testing and code review to identify potential issues before release. Dragan agreed but expressed concerns about their team's capacity to handle this. They suggested the need for a template for reviewer responses and the potential involvement of other team members, such as librarians, in the review process, at least for testing purposes. 

Enlarging the team

The idea of including non-technical VIVO customers (librarians, managers) in weekly meetings to ensure better collaboration and understanding of the software's features and needs was proposed. Change in naming (branding) meeting might be useful, as well as changing in dissemination channels (#general slack channel, mailing lists). Dragan thinks we are really missing the in-person VIVO conference for community engaging. 

Draft notes on Google Drive

Actions

Previous actions 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.