Date

22 Jun 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. Michel Héon 
5. William Welling

Agenda

1. Maven profiles / building VIVO-language and Vitro-languages without explicit step
   1. Keep 'i18n' profile or make automatic? https://github.com/vivo-project/VIVO/pull/245
2. Supporting search boosts in the future?
3. Speeding up / simplifying our processes: how do we turn out releases more quickly?
4. Moving Scholars closer to the core : continuing discussion from last committers' meeting
   1. "win/win" opportunity: Scholars and VIVO both eliminate some complexity
   2. converting Scholars SPARQL queries to VIVO DocumentModifiers
   3. replacing URIFinders with fast, reliable Solr lookups 
5. Prioritizing future development items: https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
6.  
7. VIVO in a Box current document for feedback:

Future topics

1. Prioritizing and planning post-1.12 development
2. 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
3. Post-release priorities
   
   1. Ingest / Kafka
   2. Advanced Role Management
   3. Moving Scholars closer to core - next steps
4. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be
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. 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

1. Unable to release today? Unable to release before the conference?
   1. Maven profile update to afford sibling language directories without explicit step. -Brian
   2. Should Add self-activating profiles for building Vitro-languages and VIVO-l… by brianjlowe · Pull Request #245 · vivo-project/VIVO (github.com) be before release?
      1. Likely; William and George will review and Michel will message with confirmation of working for him
   3. Pending Ralph’s availability
   4. How does the maven defaults profile work? -Brian
2. Is search boosting still supported?
   1. Index time boost no longer supported
   2. How to apply runtime boost in VIVO?
   3. What query parser to use DISMAX or EDISMAX?
   4. Boosting fields or additional boost query?/
   5. Approaches
      1. Compute separate relevancy field at index time? -Brian
      2. Access boost configuration at query time to build boost query?
   6. What are existing VIVO defaults for boosting? -Georgy
3. How to improve the release process?
   1. PR management and throughput
      1. Level of discretion
      2. 1 review for minor issues
      3. 2 reviews for major issues
   2. Can we have more regular sprints?
      1. Who plays the role of product owner? -George
      2. What intervals could make sense for regular sprints?
      3. How to manage long term support and back ported fixes? -Georgy
   3. Quality assurance process
      1. Continuous snapshot deployment
      2. How to simplify the QA process? -Michel
      3. Good tool to test and facilitate merging of community development. -Michel
      4. Separate responsibility of continuous deployment/integration with feature development. -Michel
      5. Continuous deployment for translations?
      6. Improvement/centralization of translations to facilitate additional translations. -Georgy

Draft notes on Google Drive