Page Comparison

...

What is the state of the proposed path to Apps, Platform, etcAuth/Security...

Vince proposal seeks to address the "monolithic" problems of FOLIO to formally define Apps, Platform, etc...RFCAuth/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
• 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 
• Product functionality

What stage are we at? What 

General discussion of how to move forward?

...

 - Product side - take a look at how we do releases going forward.

To Do:

Jesse -gather recordings and slide decks - some may need to be edited from a longer multi-session vide

Recommendations for our group:  Read back-and-forth in TC Slack: https://folio-project.slack.com/archives/CAQ7L02PP/p1694016217856909