2024-04-18 Board Meeting Agenda & Minutes
Attendees
@Karen Cariani
@Jeremy Friesen regrets
@Kirsten Leonard regrets traveling
@Kate Lynch
@Alicia Morris regrets
@Robin Ruggaber
@david.schober
@tamsin woo
Ex-officio:
@Heather Greer Klein
@Esmé Cowles
Agenda
Changes to the agenda
Connect 2025
Selecting dates:
Week of October 20-24 or 27-31
Discussed next steps with Alberto
Selected week of Oct 20-24, 2025
Partner meeting reflection/discussion/next steps
Energizing, and the regional meetings are a good outcome
Increase discussion went well
A lot of unease around lack of capacity
Next in person Board meeting will be at Princeton meeting
Discussion/next steps: Encouraging contributions from adopters/not-yet-Partners
Financial contribution information on the website, with a menu of other ways to contribute
Development fund(s)?
Specific fundraising?
General outreach message as well as specific, personal outreach to those who can’t yet commit to Partnership
Clover has gotten fairly wide exposure outside of the Community - there is benefit from the tooling we are creating to ask for contributions from users of those tools, who will not be solution bundle users. Should be thinking of adopters to approach for Partnership, so they can also be heard.
Try to onboard them into the current model and get them connected, and not assume they can’t participate.
Want to offer a smaller on ramp, but not change our Partnership model. Start talking to these other adopters, doing outreach.
IIIF doesn’t build software, so it is a great opportunity to build on that interest and momentum. Collective Access using Clover, potentially Ex Libris using Serverless IIIF?
Special Election next steps
Developed list of individuals for direct outreach.
Hyrax Tech Lead next steps
Out of leads for the role. Can we offer training? Can we re-think the role entirely? Can we combine it with a Hyku Tech Lead?
Could we do targeted onboarding/training session, a Hyrax camp? Using the tech lead reimbursement money in the budget to get the dev community bootstrapped. Could we offer it for maintenance working group, a 3 day dev congress with a commitment to the MWG?
We pay for the training and onboarding, with a commitment to then participate in the MWG? Seems like a nice trade.
We need a post-Hyrax-5 developer rally - some way to gather developers who have not been participating/have not ever participated but who rely on Hyrax, to re-introduce community contributions and involvement
Heather will collect more information and bring to discussion at both the finance subcommittee and next Board meeting
If we have no tech lead in place over the summer:
Need to make sure Slack questions are answered/PRs reviewed; this is part of the tech call
HMWG would need to do calls for developers, otherwise maintenance could not happen. Could doing this for specific work on a maintenance roadmap help us build our bench?
Developer Congresses would need volunteer dev lead(s) for Hyrax features
Other Updates
Potential Partners list
Princeton regional meeting update - October 14th-18th
DevOps meeting happening as well, some good overlap of folks who could go to both.
Blacklight might be a meeting on the Friday
Considering offering a Product Owner train-the-trainer training, counter-programmed to the Dev Congress
Date of next Board meeting: May 16th