Date

06 Mar 2018

Call-in Information

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

To join the online meeting:

• Go to: https://duraspace.zoom.us/j/823948749
• Or iPhone one-tap :
  • US: +14086380968,,823948749#  or +16468769923,,823948749#
• Or Telephone:
  • Dial(for higher quality, dial a number based on your current location):
  • US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
  • Meeting ID: 823 948 749
• International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Slack

• https://vivo-project.slack.com
  • Self-register at:  https://goo.gl/forms/JxQFkut4TYj4Ehww1

Attendees

 Indicating note-taker

• Jim Blake
• Andrei Tudor
• Christian Hauschke
• Ralph O'Flinn
• Benjamin Gross
• Kitio Fofack 
• Mike Conlon  
  
• Brian Lowe 
• John Fereira
• Robert Nelson
• Tim Worrall
• Steven McCauley
• Andrew Woods
• Martin Barber
• Huda Khan

Discussion items

1. Tickets discussed last week
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      
      1. Reopened, pending response to GitHub comments
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
2. FYI, steps in closing JIRA tickets
   
   1. Squash-merge in GitHub
      1. Ensure that merge commit comment does not include trivial notes (e.g. Removed whitespace)
      2. Ensure that merge commit contains link to JIRA ticket (e.g. Resolves with <link-to-jira-ticket>)
   2. Close JIRA ticket
      1. Change status to Fixed
      2. Add link to GitHub commit in JIRA comment
      3. Select next release for appropriate project for Fix Version
3. Review and testing needed
   
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      
      1. Was Closed, moved to In-Review
      2. Pull requests have not been reviewed/merged
         
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      
      1. Was Closed, moved to In-Review
      2. Pull requests have not been reviewed/merged
4. Outcomes from March 1st project strategy meeting
   1. Product Evolution task force
   2. Vision and Mission task force
   3. Governance and Organization task force
   4. Defining the Community task force
   5. Resources task force
5. What defines the 1.10 release?
   1. What remains to be done?
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. Cloning a VIVO installation
   1. Moving your VIVO Instance
   2. Backup and Restore
7. ...

Draft notes in Google-Doc

Discussion items

Action items

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

Recent JIRA Tickets

1. 1. Tickets created in the last 30 days:

      Click here to expand...

      type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   2. Tickets resolved in the last 30 days:

      Click here to expand...

      type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
      Unable to locate Jira server for this macro. It may be due to Application Link configuration.

   3. Bugs

      Click here to expand...

      type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
      Unable to locate Jira server for this macro. It may be due to Application Link configuration.