Date

17 Mar 2020

Call-in Information

Time: 11:00 am, Eastern 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. Don Elsborg 
2. Andrew Woods
3. Steven McCauley
4. Huda Khan
5. Brian Lowe
6. Ralph O'Flinn
7. Benjamin Gross 

Agenda

1. Sprint planning - i18n
   
   1. Sprint dates: Apr 6th - 17th
   2. Sprint prerequisites
   3. Pre-sprint planning meeting: Mar 25th @10am ET (https://uqam.zoom.us/j/996861901)
2. 1.11.1 maintenance release - announced!
   1. GitHub maintenance branches
3. Moving VIVO forward
   1. Goals
      1. Decoupled application (headless option?)
      2. Easy to install
      3. Integration tests
      4. Informed team
   2. Sorting out the code
      1. xxx
   3. Removing the cruft ("Legacy modules")
      1. https://github.com/vivo-project/Vitro/tree/master/legacy
      2. https://github.com/vivo-project/VIVO/tree/master/legacy
   4. Using community questions to lift the entire team
      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.
      3. Problem when saving labels
4. Vitro JMS messaging approaches
5. Incremental development initiatives
   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.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Integration test opportunities with the switch to TDB
6. Vitro pull-requests
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - looks good
   2. 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.

Notes 

Draft notes in Google-Doc

Actions