Attendees
Guests: Jesse Koennecke (PC); Kristin Martin (PC); Konstanze Sollner (Nuremberg); Martin Scholz (Nuremberg); Ingrid Schenker (Nuremberg) Ian Walls (ByWater)
Regrets
Discussion items
| Item | Who | Notes |
|---|
| Welcome new FOLIO Members | | Introduction of new FOLIO member FAU Nuremberg-Erlangen - Kontanze Söllner (konstanze.soellner@fau.de ), Schenker, Ingrid <ingrid.schenker@fau.de>; Scholz, Martin <martin.scholz@fau.de> They are evaluating and testing FOLIO as a possible replacement of their current system |
| DevOps Resources | | The FOLIO DevOps team will be losing a key member in FY23 losing 1 FTE. We need the community to identify how to replace the FTE and/or trim the requirements of this team. Encourage everyone to look at internal resources that could be given to the project. Leander mentioned they are applying for a grant that could be used for FOLIO development |
| FOLIO Scope Criteria Group | | Presentation by the Scope Criteria group; propose for evaluating new functionality/apps for FOLIO. Draft Presentation. Made up of representatives from the 3 councils Problem: no holistic review process for new apps; TC has a review process but PC does not; apps tend to come to PC at end of development; FOLIO releases getting large and unwieldy Charge : - Determine how FOLIO as a project will decide what code and new modules it is willing to accept into the project
- Determine way to decide whether new code brings enough benefit to be worth the cost
- Develop process to assess new modules that addresses functional and technical needs, and provides a blueprint for long-term support
- Provide contributors with a clear mechanism and understanding on how they can and should contribute
Have good definition of "module" but not of "app." Solutions: - Process that works under today’s flower release
- Way for PC and TC to engage earlier in the conversation about new modules
- Clear expectations regarding intellectual property rights, support, and framework to supply code
- The creation of “FOLIO approved” modules/apps
Remaining challenges: - FOLIO flower releases remain large and unwieldy
- Still need to develop mechanism to contribute module(s) that can be added by libraries but are not part of the core build
- May wish to create clear guidelines on “when should this be a new module” vs. “fit into existing module”
- Does not address existing “orphaned app” situations
Demonstrated flowchart of new module/app review process Created new document: Functional Criteria for FOLIO - Provides a high-level functional view of what belongs with the FOLIO workspace, based on work done early in the project
- How should the functional criteria (what an app or module does versus how it is created) fit into the review of new modules by the PC?
|
| Updates on other activities | CC members - please provide written updates. | To be read, not necessarily discussed: - Membership drive - A few renewals, meetings being scheduled, 2nd communication later this week.
- Treasurer
- FOLIO Resourcing Model
- Web Site - Design completed, development and copy finalizing over the next 3-4 weeks.
- Simeon - Pleased to report that paperwork to extend the FOLIO developer hosted at Cornell though December 2022 was completed between FOLIO and Cornell, and extension processed by Cornell. We should, however, try to do such extensions earlier, I'm grateful that the developer was willing to deal with the uncertainty associated with a renewal completed only 6 weeks from the term end date.
- Elections - Simeon - Saturday morning stats on election nominations: 7 nominations for 7 seats on the Community Council, 5 nominations for 5 seats on the Product Council, and only 4 nominations for 6 seats on the Technical Council. I went ahead and sent notifications extending the nomination process through Wednesday May 25.
|