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
- Don Elsborg
- Andrew Woods
- Huda Khan
- Ralph O'Flinn
- Steven McCauley
- Benjamin Gross
- Mike Conlon
- Alexander (Sacha) Jerabek
Agenda
- Sprint planning - i18n
- Sprint dates: Apr 6th - 17th
- Sprint prerequisites
- Pre-sprint planning meeting: Mar 25th @10am ET (https://uqam.zoom.us/j/996861901)
- 1.11.1 maintenance release - announced!
- Moving VIVO forward
- Goals
- Decoupled application (headless option?)
- Easy to install
- Integration tests
- Informed team
- Sorting out the code
- Removing the cruft ("Legacy modules")
- Using community questions to lift the entire team
- Goals
- Vitro JMS messaging approaches
- Incremental development initiatives
- Integration test opportunities with the switch to TDB
- Vitro pull-requests
- - looks good
Tickets
Status of In-Review tickets
Notes
- Mike Conlon attended Semantic Web Standards Conference
- VIVO awareness is high; audience was not potential adopters (mostly tooling and standards)
- Attendees discussed challenges in reconciling databases
- Scholars update: demo is available
- Making progress on faceted search/browsing
- Styling updates, finalizing look and feel
- Tested with VIVO 1.10 and above
- Options for storing/uploading data
- Sprint planning
- Looking for a different approach and setup
- Meeting next wednesday 25th at 10 am - share ideas on moving forward
- 1.11.1 maintenance branches: GitHub policies
- How to use maintenance branches? Security patches
- Point releases should not introduce breaking changes
- Moving VIVO forward: accelerating development
- Code: easier to maintain, adopt, upgrade
- Decoupling the application
- Headless VIVO: what's below the neck?
- Local semantic extension, value of Vitro/admin layer
- Creating a JIRA ticket to replicate VIVO Solr collection via API
- Original developer team is mostly gone; work needed to make the code base more accessible
- Need to figure out the seams in the code, what can be split out into modules
- We need a conversation around removing features: Open Social, image editing
- JIRA ticket for identifying, splitting out legacy code into separate repos
Actions