@Kristin Martin, @Maccabee Levine , Ludwig Liebl, @Ian Walls
Regrets: @Edwin Pretz ; @Kathleen Berry
Discussion items
Item
Who
Notes
Item
Who
Notes
FOLIO Developer Advocate
@Mike Gorrell
Hiring group has agreed to extend an offer. We are working with the co-chairs (who coordinate this role’s work) to nail down starting date, process for offer letter, etc. Hope to have them in place sometime in April.
Person would be employed directly by FOLIO (not OLF) - this is a new approach and a new responsibility to the treasurer.
What else does FOLIO need in regard to HR? OLF is offering support.
Employment for 6 month, 0,4 FTE, more details here:
FOLIO System Administration and DevOps
@Simeon Warner
Per previous discussions (12-Feb-2024, 27-Nov-2023 ,https://folio-org.atlassian.net/wiki/spaces/CC/pages/53018625 ) Index Data will be moving away from some of the DevOps support that they’ve handled forever. We discussed how to deal with the DevOps work in the community in two areas: General System Administration and CI/CD work. ID had estimated 8-12 hours per week for the System Administration work. Because of skill-sets Index Data approached EBSCO about taking on the CI/CD work that has not gotten the needed attention. EBSCO is not able to take those on with current resources.
In last meeting https://folio-org.atlassian.net/wiki/spaces/CC/pages/53018625 EBSCO (Christopher) and Index Data (Mike) agreed to do a written up quote of what would be possible to offer to share in advance of our 2024-03-11 meeting. Plan is to vote at this meeting.
Index Data paper:
EBSCO paper: withdrawn
Comments on the proposal:
From treasurer: budget can support this → Simeon will doublecheck
Folio might need a new story: Mike, Boaz, Edwin, Christopher have had 2 meetings, a 3rd is following shortly → addressing the questions → a document will be shared by the end of the week
Pure Customers → what kind of engagement can we hope for?
A story for different ways to approach the community? Libraries, networks and service providers are coming in through different paths and with different expectations and options
It's about empowerment. libraries are empowered to make FOLIO be what they want it to be, either directly or through a proxy like a service provider. And, libraries are empowered to choose WHO they want to work with as a service provider; unlike in a proprietary model, vendors have to compete for business around the same product
Restart onboarding efforts? How to approach new members / new customers?
How can the community figure out how institutions can participate?
How can we activate the existing members in the first place?
…. & plenty of non-member
As Tom said, it’s hard because we don’t have specific things that we ask them for, nor specific benefits we highlight based on what we ask them do do.
Address FOLIO using institutions and ask for their motivation? Why do they choose FOLIO?
Do we have a set of tasks at hand to offer for institutions that articulate interest in engagement?
Kristin: when you say “mentoring” is that how people / institutions can plug into the project? Or how they can build their internal capacity and savviness on library systems stuff? Or both?
Christopher: EBSCO is addressing their customers
Feels like we have 3 related but distinct problems in this area:
What do we as project need from community members
Who are the organizations that might be community members
How will community members benefit
… and who in the Community drags this forward and ongoing….
I think it’s helpful to tease these apart, Mike - And like your definitions.
+1 to Kristin — we don’t have a community project without an engaged community
Kristin’s point during the 3C noting people rolling off councils with the need for next generation
I think Maccabee said those things originally at the Tri-Council meeting.
How can we address the 3 defined points? How are they connected to the new story?
Volunteers to come up with some talking points?
Mike (as part of that group), Ian W., Simeon → Mike will reach out
Other business?
From @Kristin Martin - New FOLIO Modules approval process calls for potential MOU -
“Once the module(s) are approved by the Technical Council, the module contributors will need to reach out to the Community Council, who will, at their option, supply the MOU detailing their commitment. The FOLIO SMLLC will supply MOU and store the final results. The Community Council will manage the renewal of the MOUs as appropriate. “
Thoughts by the CC?
Secure long-term support and sustainability
Complex topic - connected to discussion on participation in FOLIO
CC might want to have a deeper discussion - awareness, that this is a complicated discussion
I think an MOU or some sort of device to force an integration / sustainability conversation is a good idea.
idea: 'sign off' process from 1-2 other institutions than the initial writer, who basically say "yeah, we see this, it makes sense, and we could modify/development it if we had to"
Can FOLIO officers drive a workflow for a “sign off process” to come to MOU’s in the end?
Pick up institutions that are coming to PC/TC or others → invite to CC → prepare MOU’s → come to agreement and introduce to community?
We have examples, like BAMA team
…. we need to continue the discussion - time was over.
First two candidates were rejected. Third candidate was interviewed the week of Feb 19 and the committee is deliberating. We confirmed with the treasurer that our current budget estimate for FY25 support both the developer advocate and possible CI/CD staffing