Wednesday, September 25, 10:30-11:50am. - Sched: https://wolfcon2024.sched.com/event/1eerY/folio-member-meeting

Session Description: FOLIO’s success as a community open-source project depends upon an engaged membership. We will provide a brief update on the current state of membership and resourcing. We will then discuss a number of current challenges and opportunities including: the FOLIO developer advocate role, shared infrastructure and DevOps support, evolution of FOLIO as a result of the application formalization process, and the roles and expectations of members. We will then facilitate a forward-looking brainstorming session before wrapping up with a discussion of next steps. This session is designed for decision makers and those providing supporting analysis and implementation project management. Representatives from all FOLIO member libraries, networks and vendors, as well as those interested in membership, are encouraged to attend.

Agenda (DRAFT)

• Moderation: Simeon

• Note taker:

• Recap of current state of membership and finances - 10 minutes - Kathleen Berry

  • FOLIO developer advocate (first few months experience, continuation question)

  • DevOps transition to Index Data - Mike

• Feedback - Attendees to select topics unconference style - 30 minutes - Simeon Warner

  • see list below

  • Blue sky thinking, Where should FOLIO go?

• Application formalization / Eureka - 15 minutes - Mike Gorrell

  • Advantages and risks

  • Managing the changes

• Making community open-source work effectively - 15 minutes - Kirstin Kemner-Heek

  • The role of membership

  • How should members meet and discuss?

  • Engagement desired and expected

    • Community actions? Pooled development, infrastructure management, …

• Next steps and followup - 10minutes - Kirstin Kemner-Heek , Simeon Warner

  • Regular FOLIO f2f and virtual meetings Discussion

  • Other actions

Topics to discuss (please add suggestions)

1. FOLIO membership fees/contributions and perks

   • A frank question - are there any plans to increase the yearly fees? Can you elaborate a bit on the personpower alternative? Can the hours be devided among several people/ SIG participations? Does it need to be a formal role?

   • What is the greatest benefit of FOLIO membership to your institution? What would you like to see as a benefit of membership? Are there other membership perks in other open source communities that you think are a good model for us to consider?

2. Member hopes and expectations

   • What members need/want from the community. How to encourage more FOLIO libraries to join as members.

   • Discuss members expectations and sound out how the members as whole group want to meet, exchange and interact in future -> set next steps to fulfill the result

   • Regarding engagement, I'd like to hear suggestions for getting members to actively participate (rather than simply attending/listening off camera) in their SIG's and/or Work Groups.

   • I'd be interested in understanding why institutions choose to become members and whether membership is meeting their expectations. If not, what could we do differently to make it a more worthwhile membership?

3. Shared infrastructure

   • Shared infrastructure, using anonymized datasets throughout development cycle, testing

4. Shared development

   • Perspectives of a Coordinated/shared development

Institutional initiative to share with other members (please add)

• …