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
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
- Benjamin Gross
- Brian Lowe
- Ralph O'Flinn
- Andrew Woods
- Nicolas Dickner
- Michel Héon
- Don Elsborg
- Alexander (Sacha) Jerabek
Agenda
- Updates from vivoconference.org
- Add your input: VIVO Development Priorities - 2020
- Sprint updates - i18n - (scrum board)
- Criteria for merge to 'master'
- Selenium testing
- Renaming of 'master' branch? (reference)
- Bugs/Issues
- Mailing list (vivo-tech)
- Solr configuration needs updates:
- Potentially related:
- - Will potentially simplify i18n '.ftl' files
- Tickets to be reviewed
- Who is working on what? - Are there active tickets in-progress?
Future topics
- 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
- Updates from vivoconference.org
- Would be helpful to have additional time between presentations (back to back 15min sessions are tight)
- Potentially include input/evaluation survey in email request for improvements
- Add your input: VIVO Development Priorities - 2020
- Sprint updates - i18n
- Feature summary for the committers
- find . -name '*.java'|xargs grep -H UQAM
- Michel to look into making the list
- Goal to get to master at the end of the sprint
- Committers and reviewers should start looking at the i18n branches now so by the end of the sprint it will only be a simple merge request
- Best to get the merge completed sooner rather than later to get other requested sync’d
- Feature summary for the committers
- Criteria for merge to 'master'
- Sprint testing has been thorough and comprehensive
- Regression tests will provide assurances
Actions