2024-04-18 Board Meeting Agenda & Minutes

Owned by Heather Greer Klein
Apr 22, 2024
2 min read

 

Attendees

@Karen Cariani

@Jeremy Friesen regrets

@Kirsten Leonard regrets traveling

@Kate Lynch

@Alicia M. Morris regrets

@Robin Ruggaber

@david.schober

@tamsin woo

Ex-officio:

@Heather Greer Klein

@Esmé Cowles

Agenda

  1. Changes to the agenda

  2. Connect 2025

    1. Selecting dates:

      1. Week of October 20-24 or 27-31

      2. Discussed next steps with Alberto

      3. Selected week of Oct 20-24, 2025

  3. Partner meeting reflection/discussion/next steps

    1. Energizing, and the regional meetings are a good outcome

    2. Increase discussion went well

    3. A lot of unease around lack of capacity

    4. Next in person Board meeting will be at Princeton meeting

  4. Discussion/next steps: Encouraging contributions from adopters/not-yet-Partners

    1. Financial contribution information on the website, with a menu of other ways to contribute

    2. Development fund(s)?

    3. Specific fundraising?

    4. General outreach message as well as specific, personal outreach to those who can’t yet commit to Partnership

    5. 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.

    6. Try to onboard them into the current model and get them connected, and not assume they can’t participate.

    7. Want to offer a smaller on ramp, but not change our Partnership model. Start talking to these other adopters, doing outreach.

    8. 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?

  5. Special Election next steps

    1. Developed list of individuals for direct outreach.

  6. Hyrax Tech Lead next steps

    1. 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?

      1. 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?

      2. We pay for the training and onboarding, with a commitment to then participate in the MWG? Seems like a nice trade.

    2. 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

    3. Heather will collect more information and bring to discussion at both the finance subcommittee and next Board meeting

    4. If we have no tech lead in place over the summer:

      1. Need to make sure Slack questions are answered/PRs reviewed; this is part of the tech call

      2. 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?

      3. Developer Congresses would need volunteer dev lead(s) for Hyrax features

  7. Other Updates

    1. Potential Partners list

    2. Princeton regional meeting update - October 14th-18th

      1. DevOps meeting happening as well, some good overlap of folks who could go to both.

      2. Blacklight might be a meeting on the Friday

      3. Considering offering a Product Owner train-the-trainer training, counter-programmed to the Dev Congress

  8. Date of next Board meeting: May 16th