Page Comparison

Welcome new CC members and onboarding

Mike Gorrell Simeon Warner

First Meeting of the new CC period

CC election details 2024 Community Council Election

Onboarding

• Community Council Calendar

FOLIO Developer advocate update

Patrick Pace (Unlicensed)

Patrick will provide an update of what he’s been working on/accomplished during his first few months.

• Knowledge collection

• Main focus:

  • Help developers

    • At incidental issues (one2one)

    • Work with service board

    • Slack intro

    • Work with TC

• Definition of own position

• Documentation with personal index

• Work with TC liason (Jeremy Huff so far)

• Confluence review and creating a documentation space

• Review of FOLIOs internal organization

• Review of used technology

• OneOnOne help

• Jira Service Management added to FOLIO environment (with Peter Murray)

• Email address “xxx@folio.org”

• Setting up a mentorship program: send out a survey → feedback still to be awaited

• Reports:

  • /wiki/spaces/DA/pages/290914337

  • /wiki/spaces/DA/pages/290979872

• Questions

  • What are the main aspects to be added to the developer advocates job description?

    • Connection to POs

    • OneTo One help : developer documentation is key

    • Prioritize what is most important if this position is for 6 month → sustainable documentation

  • What else?

    • Development of “tour to developers”

    • Contact to National Library of Australia

  • Can we install a regular update from the development advocate to the CC?

    • Action item: Yes, will be scheduled by chairs: next one in late August 2024

Co-Chair Selection

Mike Gorrell

We need to elect Co-Chairs.

Some words by Mike and Simeon on their perspectives as current/previous co-chairs.

• Intro by Mike, Simeon → strong support for the “co-chair” model

• Mike would be willing to step back and asks for volunteers to become co-chair

• We need to have two new co-chairs latest next year

Please consider self-nominating. We will elect Co-Chairs in our next meeting July 22nd.

What about the Liaisons to PC, TC

PC: Kirstin Kemner-Heek

TC: we need a new one! Action item!

Tri-Council App Form Group: Mike Gorrell

FOLIO officers: desciprtion of SMLLC functions on our goevranance model - FOLIO Governance Model

• FOLIO manager: Jesse Koennecke

• FOLIO treasurer: Kathleen Berry

• FOLIO secretary: Kirstin Kemner-Heek

AWS Costs review group: Tom Cramer - need a new representative!

App formalization group update

Mike Gorrell

Mike Gorrell attended the 26-June meeting of the group. Some updates:

1. The RFC For Application Formalization was approved by the TC in late June.

2. This RFC requires mgr-applications in order to implement ‘applications’.

3. mgr-applications is part of 'Eureka' - so it seems that Eureka is inevitable for all FOLIO adopters at some to-be-determined point in the future.

   1. Replacement of dependencies tree

   2. Introduction of side cars

   3. EBSCO initiative (LOC, …)

   4. Eureka shall be backward compatible

   5. FOLIO as a project will move to EUREKA

   6. App formalization has technical and functional aspects of how to bundle apps in future

   7. Providers can built their own definition of applications but the project appreciates the idea to have one default definition of application definition

   8. Group will work on a recommendation for PC to slice up the apps

4. This group will be making the first recommendation to the Product Council how the Applications should be defined. This is both a technical and functional question. In other words, some modules have dependencies on other modules such that you cannot arbitrarily combine modules in to Applications - so these dependencies form the technical portion of how modules can/should be combined (modules with dependencies on each other would necessarily be in the same Application). However it may make functional sense for modules to be grouped into an Application regardless of technical dependencies (Check Out and Check In are both part of Circulation even if there aren’t technical dependencies).

5. Product Council will maintain the recommended Application definitions (in terms of which modules make Applications).

6. Timing of the recommendation and the project's migration to Eureka is to be determined.

Questions/Comments:

• Involvement of the community about the process, communication, support → where are we (the CC) here?

  • Topic for WolfCon?

  • Discuss role to CC here

  • Same with EUREKA: major platform change: both scary and exciting

    • Find the right timeslot for this change

    • Sustainable and comprehensive documentation is key!

    • Documentation of the process done by community members

Backlog of topics to discuss

Action items to follow up with

Tri-council meeting followup

Simeon Warner Mike Gorrell

In https://folio-org.atlassian.net/wiki/x/aAMrAw and the associated spreadsheet

• Mike Gorrell, Ian Walls , Simeon Warner → Mike will reach out

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

Mike Gorrell (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

CC review as part of FOLIO Module Approval Process and possible MOU

Mike Gorrell Simeon Warner

From https://folio-org.atlassian.net/wiki/x/JgO8E

• AGREEMENT that CC chairs will coordinate with other co-chairs to ensure that we are informed and can bring items to the CC