Date

Call-in Information

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

Attendees

(star)  Indicating note-taker

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

Agenda

  1. Sprint branches
    1. Do we need branches for ongoing sprint?
    2. What about VIVO 1.14.0 release publishing which is in process
      1. New GitHub feature - managing a merge queue, can this help for some linked issues/features?
  2. License
    1. At the beginning of the file, not by using JavaDoc
  3. Code style
    1. VIVO specific one vs Google Java code style
      1. Maximum length of lines is 120 / 100 characters
      2. 4-space / 2-space indents

Notes

  1. Decision is to use the main branch as base branch for PRs in the February 2023 VIVO sprint due to the fact that we don’t have one big feature we are developing in this sprint, so no need for feature branch.
  2. A simple comment at the beginning of each source file probably should just point to the LICENCE root file. At the moment, VIVO LG is discussing what should be changed in the LICENSE file in order to transfer copyright ownerships from Cornell university to Lyrasis. VIVO LG should be also consulted for a simple comment line at the beginning of each source file.
  3. We should develop our own code style. Moment for alignment of the existing codebase with VIVO code style should be carefully selected. 
  4. Upgrading of Jena 3 to Jena 4 is an important issue, Brian would like to help in this issue.

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.