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
- William Welling
- Andrew Woods
- Brian Lowe
- Ralph O'Flinn
- Michel Héon
- Huda Khan
- Alexander (Sacha) Jerabek
- Benjamin Gross
- Don Elsborg
- Santhosh Kumar Gopalan
- Nicolas Dickner
Agenda
- Announcements
- TIB/UQAM - Kafka initiative updates - 2020-12-16 - Special Topic - VIVO Kafka Ingest
- Community mailing list
- Error when trying to link a person with a grant
- Any additional thoughts on
- Images are not displayed after migration
- Any news, Benjamin Gross?
- Can we create custom roles in Vivo
- Sounds like "Advanced Role Management"
- Tomcat Garbage Collection & Memory Usuage
- Error when trying to link a person with a grant
- Advanced Role Management sprint - 2020 - VIVO Sprints
- 1.11.2 patch release - likely not going to happen
- Working towards 1.12
- To be reviewed
- Benjamin Gross / Brian Lowe : any final comments?
- Ready for merge
- Very small change
- Any further discussion before merge?
- Documentation needed
- Bugs to be fixed
- 1.12 release planning
- Email of schedule to vivo-community
- Code freeze once i18n tickets are merged into the sprint-i18n branch (Jan 20th)
- Sprint to test merge of sprint-18n into master: week of Jan 25th
- 1.12 release candidate #1: Feb 1st
- Two week RC-1 testing period
- For each subsequent RC-2 (if required), adding another two weeks to the schedule
- Do we want the `war` install in 1.12? -
- Next steps?
- To be reviewed
- Tickets that should be close to merge
- Post-i18n priorities
- VIVO-in-a-box
- Messaging
- Moving Scholars closer to core - next steps
Future topics
- Vitro JMS messaging approaches - redux
- Which architectural pattern should we take?
- What should the body of the messages be?
- Renaming of 'master' branch? (ZDNet, BBC)
- Guidance from GitHub
- DSpace has done it
- Fedora has done it
- Samvera is doing it
- 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
Actions