...

Attendees

 Indicating note-taker

1. Graham Triggs
2. Mike Conlon
3. Brian Lowe
4. Benjamin Gross
5. Tim Worrall
6. John Fereira
7. Muhammad Javed
8. Huda Khan
9. Ralph O'Flinn
10. Andrew Woods

...

1. 1.11 release progress/status

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1415

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1630

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1670

   4. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1287

   5. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1698

2. Moving to `master` instead of `develop` after this release?
3. VIVO Scholars task force - opportunities?

4. Where are we with Docker?

   1. Can folks spin up vivo-docker2?

Notes 

1.11

1. vivo-1415: Benjamin and Andrew to submit pull-requests based on code review
   1. Waiting on Graham Triggsto respond
2. vivo-1630: alessandro galassois back... hopefully this ticket can be merged/closed today/tomorrow
3. vivo-1670: Benjamin to submit pull-requests based on code review
   1. Waiting on Graham Triggsto respond
4. vivo-1287: some question about the extra annotations in this pull-request
   1. Would Don Elsborgbe will to remove them? Brian Lowehas thoughts on this topic
5. vivo-1698: awaiting a pull-request

Moving from `develop` to `master`

1. Yes, let's do this after the 1.11 release

VIVO Scholars Task Force

1. Review of the architecture
2. We like it... interest in supporting the pattern for the broader community

Actions

•  Type your task here, using "@" to assign to a user and "//" to select a due date

...