Date

25 May 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. Benjamin Kampe 
3. Georgy Litvinov
4. Sandra Mierz
5. Michel Héon 
6. William Welling 
7. Huda Khan  
8. Ralph O'Flinn 

Agenda

1. Announcements / updates
2. Mailing list / Slack discussion
3. RC1 issues to resolve:
   1. Need to decide correct behavior for: Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

5.  Testing / results: Release Testing - 1.12.0
6. VIVO WCAG 2 A/AA  accessibility audit results from Deque
7. Updates on Data Ingest Task Force discussions
8. Prioritizing and planning post-1.12 development
   1. https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing

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

• Michel currently only one testing. Hopefully more people will join.

• Issue: https://jira.lyrasis.org/browse/VIVO-1983  - profile editing will be saved to current language, instead of standard

• • Possible solutions?

• • Add language tags at label editing

• • Separate on Manage label page

• • Michel: should go with the approach easiest to implement for release (Ralph & Brian agree)

• Issue Not Yet Added : Security problem when new user is added (email sent includes code, always the same for every user), affects probably only internal accounts

• • Solution: don’t truncate code

• • Numbered release or Patch? 

• Monday release of RC2?
  • On Monday testing for RC1 ends, should we immediately put out RC2 or wait and fix issues from RC1 testing, so RC2 could potentially be *the*  release?

• • Georgy: should we meet on Thursday or Friday and review?

• • Meeting on Friday morning(US)/Friday afternoon(EU): Georgy & Michel available

• • See Slack for further details (will be communicated there)

Draft notes on Google Drive