Date

Call-in Information

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

To join the online meeting:

Slack

Attendees

(star) Indicating note-taker

Discussion items

  1. Sprint topics
    1. Sprint dates - weeks of May 21 and 28?
    2. Removing 1.10 blockers?
      1. Roll-back Jena updates (Fedora example)?
  2. Maven discussion from last week
  3. Join the development team!
    1. Process
      1. create a JIRA
      2. fork
      3. create a branch
      4. make a minor PR
      5. review other's PRs and approve/request-changes
    2. Candidate tickets (everyone please take one)
      2.  - John Fereira
      4. Defining style guidelines (including non-Java files)
      5. Adding a GitHub "contributing" file
      6. Others?
    3. Thanks for leading the way, Benjamin Gross!
      1. Minor process question: Who commits changes? 
  4. Review and testing needed
    2.  Mike Conlon
  5. Are there salted hashes in Vitro/VIVO for passwords? If yes, documentation should be updated accordingly,

Notes

Draft notes in Google-Doc

  1. Sprint topics
    1. Sprint dates - weeks of May 21 and 28?

      1. Project strategy meeting taking place on 01/03/2018 (March 1st)

      2. The strategy meeting will define some priorities and might therefore influence the sprints following.

      3. Having some outputs from sprints at this stage on the project seems to be the top priority.

      4. Andrew is going to call for interest on end of April (2 weeks) Sprint leadership.

        • Making a successful sprint is more or less :

          • Institutional support is necessary

          • 1 call at the beginning

          • 1 retrospective call

          • And virtual stand ups through Slack

        • Leading a sprint does not necessarily require deep knowledge of VIVO code. Review, coordinating etc. is the main task.

        • Javed is taking the lead for April Sprint. Ralph can assist.

  2. Maven discussion from last week

    1. Lot of people might be having issues on using Maven. There should be a documentation on how to proceed on builds with their customizations.

    2. On VIVO Maven is used to build but also to deploy the application. There is a ticket on how we use Maven on the project cause for the moment the process is very developer oriented.

    3. There is a use case on a non developer person being able to evaluate the application without having to do developer’s modifications. Having a War file to drop in a application container and a setup a database

    4. The idea of having a vagrant or virtual machine with VIVO installed is proposed for that use case

    5. A pre-packaged VIVO is an executable jar file with Jetty inside is also a possibility. It would just require the user to have Java installed. An evaluation system using TDB for installation on a Mac has been developed for VIVO Camp.  Download, unzip, startup: https://drive.google.com/open?id=19jqP9jyiQpzxTeR_n401WIHsbWvRTXR7

  3. Join the development team!
    1. There is a need to clarify on what are the expectations from VIVO committer team members
    2. Process, We need more people taking this contribution process.
      1. review other's PRs and approve/request-changes

        • There a need of people engaging in this task.

    3. A committers list with their respective expertise needs to be created.


Action items

Recent JIRA Tickets

    1. Tickets created in the last 30 days:


    2. Tickets resolved in the last 30 days:


    3. Bugs