Date
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
- Self-register at: http://bit.ly/vivo-slack
Attendees
Indicating note-taker
Agenda
- Maven profiles / building VIVO-language and Vitro-languages without explicit step
- Keep 'i18n' profile or make automatic? https://github.com/vivo-project/VIVO/pull/245
- Supporting search boosts in the future?
- Speeding up / simplifying our processes: how do we turn out releases more quickly?
- Moving Scholars closer to the core : continuing discussion from last committers' meeting
- Prioritizing future development items: https://docs.google.com/spreadsheets/d/103P9P4v6yUBSb5BnVaK40NoGx1fIYyL8uaHKUubZWbE/edit?usp=sharing
- VIVO in a Box current document for feedback:
Future topics
- Prioritizing and planning post-1.12 development
- Forward-looking topics:
- frameworks: Spring / Spring Boot / alternatives
- Horizontal scalability
- Deployment
- Configuration : files / environment variables / GUI settings
- Editing / form handling
- Adding custom theming without customizing build
- Post-release priorities
- Ingest / Kafka
- Advanced Role Management
- Moving Scholars closer to core - next steps
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be
- Incremental development initiatives
- Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven
Tickets
Status of In-Review tickets
Notes
- Unable to release today? Unable to release before the conference?
- Maven profile update to afford sibling language directories without explicit step. -Brian
- 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?
- Likely; William and George will review and Michel will message with confirmation of working for him
- Pending Ralph’s availability
- How does the maven defaults profile work? -Brian
- Is search boosting still supported?
- Index time boost no longer supported
- How to apply runtime boost in VIVO?
- What query parser to use DISMAX or EDISMAX?
- Boosting fields or additional boost query?/
- Approaches
- Compute separate relevancy field at index time? -Brian
- Access boost configuration at query time to build boost query?
- What are existing VIVO defaults for boosting? -Georgy
- How to improve the release process?
- PR management and throughput
- Level of discretion
- 1 review for minor issues
- 2 reviews for major issues
- Can we have more regular sprints?
- Who plays the role of product owner? -George
- What intervals could make sense for regular sprints?
- How to manage long term support and back ported fixes? -Georgy
- Quality assurance process
- Continuous snapshot deployment
- How to simplify the QA process? -Michel
- Good tool to test and facilitate merging of community development. -Michel
- Separate responsibility of continuous deployment/integration with feature development. -Michel
- Continuous deployment for translations?
- Improvement/centralization of translations to facilitate additional translations. -Georgy
- PR management and throughput