What do we mean when we say "looking at the impact on the Product Council from the re-architecting proposal or vision that was presented by Vince at WOLFCon 2023."
What is the state of the proposed path to Apps, Platform, Auth/Security...
Vince proposal seeks to address the "monolithic" problems of FOLIO to formally define Apps, Platform, Auth/Security...
Vince makes the problem statement: "Folio is stuck in a mode of monolithic releases which are ever increasing in size"
Problems from the PC perspective (draft suggestions only):
- Hard for PC to fulfil it's responsibilities in regards the 'product' where we lack a definition of what the "product" is
- Includes the time necessary for App / Module evaluation issue as well as the issue that this has not proved particularly effective so far
- e.g. Translation app "approved" but not part of product - functionality was desirable but implementation was not accepted by
- OA app approved but failed TC evaluation
- Lists app not approved by PC but already going through TC evaluation
- Includes the time necessary for App / Module evaluation issue as well as the issue that this has not proved particularly effective so far
- Overhead of a "Flower release" - on the product and the wider community (testing)
- Ever growing "product" as it's hard to rule out functionality that is useful to at least one library
- Overhead for hosting institutions and service providers in managing and upgrading Folio installations
RFC for Tech Council Review
Should this be part of the product? Current options are Yes or No. Does this give us more options? Yes - core, No - this should never get close to FOLIO, Yes - extended, etc...
Problem statements: What are challenges we currently see with the Product? What impact will these changes have on these challenges? 5-10 of these?
- Releases
- Large overhead of a Flower release
- Balance between stability vs new functionality
- Deadlines for release cause bottlenecks especially in relation to new modules
- Overhead for hosting institutions and service providers in managing and upgrading Folio installations
- Product functionality
- Ever growing "product" as it's hard to rule out functionality that is useful to at least one library
- Struggle to have a definition of the 'product' that the "Product Council" is responsible for
What stage are we at?
General discussion of how to move forward?
This proposal is the way to move forward? RFC could be rejected or accepted?
Not agreement at TC as to how to best move forward.
What is PC role in process?
What is the right way to approach this large architectural question?
Releases are big large process to put releases together.
- Product side - take a look at how we do releases going forward.
Deliverables:
- List of questions - some may come from TC, some from PC, some from other channels
- What is PCs role(s) in a project to implement this
- Is there code already written as if this is in place?
- Are we reacting to something already in motion, or are we recommending a path forward?
- Present to PC prior to Tri-Council (by October 5)
To Do:
Jesse - gather recordings and slide decks - some may need to be edited from a longer multi-session video.
Jesse - Set up meetings - weekly at least until October same time slot 8:30 Eastern - Monday
- Get FOLIO Zoom link
Add to Questions and Problem Statements above
Recommendations for our group: Read back-and-forth in TC Slack: https://folio-project.slack.com/archives/CAQ7L02PP/p1694016217856909