Page tree
Skip to end of metadata
Go to start of metadata

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. New JIRA workflow
  2. Review and testing needed
    1. VIVO-1409 - Getting issue details... STATUS
    2. VIVO-1438 - Getting issue details... STATUS Mike Conlon
    3. VIVO-1459 - Getting issue details... STATUS
  3. Sprint topics (...or what comes out of the March 1st strategy meeting)
    1. Initial announcement (Planning and Sign-up page)
    2. Dates for both sprints:
      1. #1 weeks of April 23rd and 30th
      2. #2 weeks of May 21st and 28th
  4. Outstanding vivo-tech mailing list question
  5. Updates on Maven documentation from Don Elsborg? Is this worth tracking in Jira?  VIVO-1450 - Getting issue details... STATUS
  6. GitHub
    1. Please help create the canonical list of Git organizations

    2. Collecting VIVO GitHub repositories into three Git Organizations?
      1. Supported (vivo-project)
      2. community experiments (vivo-labs)
      3. archive (vivo-archive)
  7. What defines the 1.10 release?
    1. What remains to be done?

Draft notes in Google-Doc

Discussion items

  1. New JIRA workflow -- includes “Received” and “In Review.” No longer includes “Resolved.”

    1. Tickets do not automatically open.  They are marked “Received” to start.

    2. Once there’s a pull request, the ticket is marked “In Review.”

    3. Tickets previously marked as “Resolved” have been moved to “Closed”

    4. You may enter a ticket, assign it to yourself, and mark it as Open, and then “In Progress” when work begins.

  2. Tickets “In review”

    1. Suggestion:  Two reviewers, one of which is a committer, neither of which is the author review and approve.  With two reviews, the pull request can be committed.

    2. Options for committer.  

      1. Click “Merge”

      2. Click “Squash” and “Merge” to get the commits into one commit and then merge.  This might be the default.

      3. Surgically combine some commits into groups, merge groups

    3. Jim: Squash commit is useful for backing things out.

    4. Author might put a note in if there is a reason to keep the commits separate

    5. VIVO-1409 - Getting issue details... STATUS -- Jim, and John to review

    6. VIVO-1438 - Getting issue details... STATUS  -- has been reviewed twice.  Can be committed?  The group suggested yes.  Benjamin offered to commit.

    7. VIVO-1377 - Getting issue details... STATUS  – Mike will review, it might duplicate 1409

    8. VIVO-1459 - Getting issue details... STATUS  -- Brian, Kitio to review

    9. Mike and Andrew will review permissions in the repos to support reviewers.

  3. Sprint topics (...or what comes out of the March 1st strategy meeting)

    1. Initial announcement (Planning and Sign-up page)

    2. Dates for sprints:

      1. #1 weeks of April 23rd and 30th -- Javed will lead, supported by Ralph and Kitio

      2. #2 weeks of May 21st and 28th -- leaders TBA

    1. Comments on the Tech Initiatives document will be opened up after March 1.

    2. Partial commitment to the sprint is possible -- requires crystal clear communication about availability.

    3. Participation across time zones, asynchronous participation.  Need to work things out, set expectation

  4. Questions being answered on the mailing lists

    1. Could take one-two hours per day

    2. Pending question on Solr was documented in 1.8, but not in 1.9 (Maven)

  5. Maven documentation ticket

    1. Shell in progress https://jira.duraspace.org/browse/VIVO-1450

  6. Next release of VIVO.

    1. See https://jira.duraspace.org/browse/VIVO-1410

    1. Please add comments to the JIRA regardings blockers regarding the next release

  7. What are the official github organizations and repos?

    1. Are there other repos?

      1. https://github.com/vivo-project

      2. https://github.com/openrif

      3. https://github.com/OpenVIVO

      4. https://github.com/vivo-ontology-lab

      5. https://github.com/vivoconference

      6. https://github.com/lawlesst/vivo-vagrant

      7. https://github.com/gwu-libraries/vivo-docker

      8. https://github.com/VIVO-CA/

      9. https://github.com/VIVO-DE/

    2. Three kinds of repos? Official/Supported, Community things, archive

Action items

  • Mike Conlon will repair permissions in the repos to allow reviews

Recent JIRA Tickets

    1. Tickets created in the last 30 days:

       Click here to expand...

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    2. Tickets resolved in the last 30 days:

       Click here to expand...

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh

    3. Bugs

       Click here to expand...

      T Key Summary Assignee Reporter P Status Resolution Created Updated Due
      Loading...
      Refresh