2026-04-07 Release Management & Commmunication WG meeting notes

 Date

Apr 7, 2026

 Participants

• @Autumn Faulkner @Charlotte Whitt @Thomas Trutt @Tod Olson

• Regrets: @Jeremy Huff @Jennifer Eustis

• Guest: @ERICA GILSON

Agenda

• Discussion with Erica: PC and release communication

  • Welcome Erica!

  • Brief background of group’s work & goals

  • Our questions:

    • Blogs, news releases, LinkedIn – current ownership?

    • Content approval workflow

      • Press releases for each new flower release will need to be vetted

    • Potential access for PC?

      • Yes – this would be doable. Probably best for more informal information sharing like LinkedIn, blogs, etc.

  • Erica’s questions/thoughts

    • Establishing a cadence for content would be very helpful; EBSCO can plan on what support/resources would be needed

    • Erica will coordinate with Rachel Fadlon on a general plan for outreach/marketing

  • Should there be one centralized page for FOLIO community updates?

    • Erica thinks this would be helpful and could prevent empty feeds

    • Group agrees this is a good idea

    • Smaller news items, posts, tips, etc. could all be in one spot; this accommodates all the levels of FOLIO expertise and positionality

    • Links out to FOLIO wiki, etc., would be helpful –

    • Conference reporting! Interesting sessions could be recycled through a central page

    • Same for regional FOLIO events, like GVSU and Chalmers are holding this spring/summer

    • Include non-English posts! → possibly filtering to ensure English posts are the majority?

• Next steps → tabled till next meeting

  • Sub-groups for creating recommendations

  • 3 distinct areas:

    • Establish long-term comms strategy and content sources

      • Envision alternative to release digest

        • Coordinate with POs re: notes on functionality

        • Pilot for Trillium

      • What types of content, how often, from whom, on what channels

        • Blogs, social posts, news, newsletters…

        • Release announcements, sprint demos, new features with each release, conference reports, tips & tricks from implementers…

        • Determine a (non-overwhelming!) content schedule across all of these

      • Draft plan for Rachel and Erica at EBSCO for centralized updates on folio.org

        • Refine plan with PC

    • Develop new governance and infrastructure for comms oversight

      • Who owns what? Who plans and gathers content specified by newly established comms strategy?

      • Coordinate with CC & RMS

        • Important Q – how to integrate DIP communication into the plan

      • Establish a content queueing and review process

      • Establish permanent PC roles and processes accordingly

    • Logistics for increased PC involvement with release management

      • Workflow and tracking infrastructure for all dev processes that should receive PC review

      • More formalized PC/RMS interactions

      • Establish permanent PC roles and processes accordingly

• Meeting scheduling

  • Weeks 1 and 3 going forward?

  • Will put a poll on Slack

Action items