2026-05-05 Release Management & Commmunication WG meeting notes

 Date

May 4, 2026

 Participants

• @Autumn Faulkner @Charlotte Whitt @Thomas Trutt @Jeremy Huff @Jennifer Eustis

• Regrets: @Tod Olson

Agenda

• Communications strategy alignment

  • Question from Caitlin – dealing with a lot of outreach & coordination efforts in different areas – is there a way to unify/consolidate these?

  • My idea – turn FOLIO wiki home page into the official “front page” for FOLIO community updates, and EBSCO can pull from this content on a predetermined basis

    • PC release tracking

      • Priorities & endorsements – upcoming releases

      • Release notes (replace release digest) – for most recent release and next immediate release

        • PO notes on functionality by app/module

        • Sysadmin config/update specs

    • CC member updates

    • Future DIP process

    • SIGs → reports, year in review?

      • aggregated list of important/recent discussion topics

    • News & blog posts

      • Sprint demos from developors

      • Session reports & presentation materials (WolfCon but other regional events)

    • Social accounts

      • Transfer to community ownership

    • Quick resource guide

      • Communication channels

      • Governance structure

      • Latest council notes

      • Development basics

      • Jira basics

  • Hope to achieve:

    • More centralized news/updates delivery for community, less digging in wiki

      • Reduce learning curve for new adopters

    • More baked-in exposure? Not sure how many folks use the home page as a landing but that’s something we could encourage if/when this gets revamped

    • Easier management of info for those contributing

    • Sustainable, consolidated process

  • Thoughts & ideas

    • Ownership of folio.org needs to be transferred to and governed by CC

      • Reach out to Kristin M. about possibilities?

    • Replace SIG reports with a couple sentences added to PC agenda each month in “News & Updates” section; compile these for home page

    • Who is our audience? Which site serves which demographic?

      • folio.org is for prospective implementers and a gateway to the more detailed information on the wiki

      • wiki is for current implementers but also a good starting place for prospective implementers

    • Missing information in wiki in general, like lack of ERD for database architecture

• Next steps if we want to move forward

  • Autumn presents idea to PC

  • Autumn & Jennifer take idea to CC/TC

  • Discuss ownership of home page with Peter Murray

  • Ensure ownership of folio.org content – set up liaison on the community side for Erica/Rachel

  • Get UX and Accessibility guidance!

Action items