Date

27 Apr 2021

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?pwd=a2Q3RUVKVkN2dkNHV3FUaFRtLzhGdz09
  • Passcode: 351860

• 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. Brian Lowe
2. Georgy Litvinov 
3. Michel Héon 
4. Nicolas Dickner 
5. William Welling 
6. Huda Khan
7. Benjamin Gross 

Agenda

1. Development issues for RC1 are cleared.  Only documentation / test procedure updates remain.  Blocker issues:
   

   1. 1. 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. RC1 testing
   1. Making it easy
   2. Simplifying first pages of documentation / "Quickstart" installation guide with Docker
   3. Submitting test results without needing wiki access:
      1. Draft Google forms courtesy William Welling: https://docs.google.com/forms/d/e/1FAIpQLSe3xKY5QbzMoZ6fzkaxZMz8_oSGtkVGSYWMNBk_hjVaUtp1Qg/viewform
3. Any "final" initial feedback on VIVO in a Box before next Leadership meeting: https://docs.google.com/document/d/1lfTzXSXrtpRVT3CVWAj55XOou94kIg7QJ2NrHPQewUM/edit?usp=sharing
   1. Reference slides: 
4. Other topics?

Future topics

1. Forward-looking topics:
   
   1. frameworks: Spring / Spring Boot / alternatives
   2. Horizontal scalability
   3. Deployment
   4. Configuration : files / environment variables / GUI settings
   5. Editing / form handling
   6. Adding custom theming without customizing build
2. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
3. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
4. 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. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

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 on Google Drive