Skip to end of metadata
Go to start of metadata


Call-in Information

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

To join the online meeting:



(star)  Indicating note-taker

  1. Don Elsborg 
  2. Andrew Woods
  3. Steven McCauley
  4. Huda Khan
  5. Benjamin Gross (star)


  1. Announcements
    1. Development velocity
    2. Gathering VIVO Scholars "questions from the community"
    3. Initial clean-up of legacy GitHub branches
  2. 2020 - VIVO Sprints
    1. VIVO-i18n - Canadian French Initiative
    2. Pre-sprint planning Doodle
    3. Dates: Apr 6th - 17th
  3. 1.11.1 maintenance release
    1. Remaining:
      1. Pull-request to merge release branch into `master` branch
    2. VIVO 1.11.1 Release Announcement
    3. GitHub maintenance branches
  4. Vitro JMS messaging approaches
  5. Incremental development initiatives
    1. VIVO-1688 - Getting issue details... STATUS
    2. VIVO-1443 - Getting issue details... STATUS
    3. Integration test opportunities with the switch to TDB
    4. Decoupling the "asset store"
  6. Vitro pull-requests
    1. VIVO-1658 - Getting issue details... STATUS  - looks good
    2. VIVO-1700 - Getting issue details... STATUS


  1. Status of In-Review tickets

     Click here to expand...

    T Key Summary Assignee Reporter P Status Resolution Created Updated Due


Draft notes in Google-Doc

  1. Announcements
    1. Development velocity - how do we increase? Should we decrease frequency of the dev meeting? Benjamin and Andrew are skeptical that would work. 5 hours freed up perhaps… Steve: Maybe the product direction document will encourage and focus activity. 
      1. Andrew shared draft product direction document with committers - bookmark and comment please (link
      2. There is activity from a few groups, mostly from Europe. We could/should support their efforts and get it into the core codebase. 
      3. Get more installations - make VIVO more appealing 
      4. Directive from VIVO leadership group technical director that we need to start moving the software forward. Does that manifest itself as the tech director spending time committing code instead of managing a team of devs?
    2. Gathering VIVO Scholars "questions from the community"
      1. Month or two out from a beta release
      2. They are trying to predict the questions that will come from the community. Any here? 
        1. What are the system requirements, specifically do I need more memory?
        2. Which versions of VIVO does this work with? Jena 2 vs 3? TDB vs SDB?
        3. If I already have an instance of VIVO running, what else do I have to do to get Scholars running on top? 
        4. Can it be installed without Docker without going completely crazy? 
        5. Can it be configured to work with a single Solr index instead of 2? 
        6. What are all the components that need to be installed?
        7. Is the beta release also of the Duke site itself, with the current VIVO data?
    3. Initial clean-up of legacy GitHub branches
      1. The initial cull has occurred 
  2. 2020 Sprint Planning - Dates: Apr 6th - 17th
    1. VIVO-i18n - Canadian French Initiative -
      1. Sprint prereqs: (Code in GitHub, GitHub diff/pr, How can the code be subdivided?) Andrew posted these as action items prior to sprint to support. 
  3. 1.11.1 maintenance release
    1. Remaining:
      1. Pull-request to merge release branch into `master` branch - basically updating pom files to show 1.11.2
    2. VIVO 1.11.1 Release Announcement - any comments?
    3. GitHub maintenance branches - Andrew thinks we should have a 1.11-rel-maint branch, not for the point releases. Benjamin - old versions had breaking changes in point releases which may have been an argument for keeping maint branches for point releases, but not anymore. Andrew - will check in with Ralph who is managing the releases
    4. Benjamin - why is Travis failing for VIVO with the 1.11.2 release? Andrew: Because it is expecting the existence of the Vitro artifacts with the 1.11.2 tag. One solution is for Andrew (or something else with permissions) to push the 1.11.2 artifacts to the sonotype repo. 
    5. Followup question - is it possible to build VIVO on your local machine without having Vitro downloaded already, such that it pulls from the repo during build time? 
  4. Vitro JMS messaging approaches
    1. Fundamentally we want to create messages to other processes outside VIVO can react to changes with VIVO
    2. Huda - did we talk about pulling out the search indexer from the core VIVO code during our fly-in? Andrew - we likely talked about it but not at this level of detail. Huda - Worked a bit on linked data notifications. The model is more or less the same. Don - don’t we also need a message publisher? Andrew - yes, it is required and is part of the second diagram. Andrew - impression of linked data notifications is there’s like an inbox for changes are stored. 
    3. What is the preference of the community between these two? What does it mean for somebody installing VIVO? They would have to install the consumer as well? 
    4. Don - Isn’t the current search indexer similar to what we’re describing in pattern 2, but it’s baked into VIVO? A melding of the approaches. 
    5. Benjamin - are there any performance concerns with using the messaging approach? Andrew - likely yes, especially with updating the triplestore from the inferencer if there isn’t a direct connection. 



  • No labels