Skip to end of banner
Go to start of banner

2024-03-11 Community Council Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Attendees

Guests:

Regrets: Edwin Pretz ; Kathleen Berry

Discussion items

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 ,2024-02-26 Community Council Meeting Notes ) 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 2024-02-26 Community Council Meeting Notes 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 double

  • EBSCO is appreciating the alternative offer

Result: Acceptance of Index Data's offer by CC

Tri-council meeting followup

Simeon Warner Mike Gorrell

In https://folio-org.atlassian.net/wiki/x/aAMrAw and the associated spreadsheet we discussed barriers to participation and ideas to increase participation in FOLIO

Comments:

  • What next actions might be appropriate?

  • 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?

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?

Backlog of topics to discuss

FOLIO Developer Advocate

Mike Gorrell

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

Action items to follow up with

Community communication norms

Tom Cramer Ian Ibbotson (Use this one) Christopher Spalding 

From 2023-08-25 Meeting notes

  • idea about changing the ask on SIG's!  Information and discussion in the SIGs and a transport of summaries to upper levels

  • asking how communication flows across the project, new people don't know, need some guidance for the project

  • no update

Application and Platform Formalization WG

Ian Ibbotson (Use this one) (liaison to CC)

Notes folder: Application and Platform Formalization Proposals WG

Outreach and Marketing WG

Boaz Nadav Manes 

WG charge from 2023: WG charge from 2023: https://docs.google.com/document/d/1ZTOUOhwUtWaEjywKkS0cA41t1h0Wzhv_F9FR5Cyhqzk/edit

  • No labels