You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Mike Gorrell
Simeon Warner
Edwin Pretz
Christopher Spalding
Shawn Nicholson
Kathleen Berry
Kirstin Kemner-Heek
Boaz Nadav Manes
Maike Osters
Guests: Maccabee Levine , Ludwig Liebl ; Patrick Pace (Unlicensed) ; Kristin Martin Tom Cramer , Ian Walls
Regrets:
Item | Who | Notes |
|---|
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 |
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: 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: Questions
|
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. Please consider self-nominating. We will elect Co-Chairs in our next meeting July 22nd. What about the Liaisons to PC, TC? Note taking … (added by Kirstin) |
App formalization group update | Mike Gorrell | Mike Gorrell attended the 26-June meeting of the group. Some updates: The RFC For Application Formalization was approved by the TC in late June. This RFC requires mgr-applications in order to implement ‘applications’. 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. 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). Product Council will maintain the recommended Application definitions (in terms of which modules make Applications). Timing of the recommendation and the project's migration to Eureka is to be determined.
|
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
we discussed barriers to participation and ideas to increase participation in FOLIO. Discusses in 2024-03-11 Community Council Meeting Notes and agreed to have a group to come up with some talking points? |
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 |