Date

13 Aug 2019

Call-in Information

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

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Ralph O'Flinn 
2. Andrew Woods
3. Brian Lowe 
4. Don Elsborg 
5. María Amalia Flórez Huertas 
6. Huda Khan 
7. Benjamin Gross
8. William Welling

Agenda

1. Community updates
2. VIVO 1.11.0 release candidate planning
   1. Release candidate to be published: today?
   2. Update/Release 
      1. vivo-vagrant
      2. vivo-docker2
   3. Release Testing - 1.11.0
   4. Issues
      1. 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. Transition to Java 11? (pom.xml) (travis.yml)
4. Sprint planning
5. Community mailing lists
   1. VIVO profile for people who have left the University or are deceased
   2. Update the New VIVO 1.10 from VIVO 1.8.1
6.  In-review tickets
   1. 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.

Tickets

1. Status of In-Review tickets

   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. Received

   Click here to expand...

   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.

   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      1. (re-)Raises interest in reconsidering first-time, every-time, tdbconfig design

   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Should be low-hanging

   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      1. Where does this stand? What is needed to add more person identifiers to VIVO?

   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. Mike Conlon : thoughts on where this stands?

3. Bugs (1.11)

   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.

Notes 

Draft notes in Google-Doc  

Actions

Previous Actions