/
2024-01-03 Formalization Working Group Meeting notes

2024-01-03 Formalization Working Group Meeting notes

Jan 24, 2024

Date

Recording: https://recordings.openlibraryfoundation.org/folio/councils-co-chairs/2024-01-03T13:00/

Attendees


Goals

Discussion items

TimeItemWhoNotes
5minUpdates on RFCs, PoC, etcCraig, others
  • All code moved over!
  • Jira moved over! - still working on some cleanup.

Kristin - take second look at the app spreadsheet from Vince next time?

  • Implications for definition of 'app'

Have we decided?

  • this solution is being implemented broadly 'as is'?
  • initial technical-driven grouping?
  • group will deal with communication, policy, governance, day one policies?
  • aspirational view is helpful? initial grouping is not a magic bullet for the release issues, work on individual modules will be necessary


Links to existing groupings of modules into applicationsCraig

The super simplified set of applications:  See https://github.com/folio-org/application-descriptors/tree/master/Poppy

  • There are just 3 applications here:
    • app-platform-minimal - foundational/core stuff which is always needed
    • app-platform-complete - everything else, aside from edge modules
    • app-edge-complete - the edge modules
  • The naming of these is a little unfortunate - the word "platform" probably shouldn't be present in any of these.  
  • These are based on the (pre-)poppy versions of modules, I believe from around the time Poppy Bugfest began.  They will be updated to the Poppy GA versions of modules at some point.

The "dependency driven" set of applications: 

  • See https://github.com/folio-org/application-descriptors/tree/master/Orchid. 
  • See also:
  • The goal here was to group the modules into smaller chunks while still maintaining composability, i.e. allowing for some applications to be optional, as opposed to all applications always being required.
  • These groupings prioritized dependencies and composability over logical/business boundaries.
  • It's likely that these groupings make very little sense to non-technical audiences.
  • These are based off the Orchid SP6 versions of modules.

The "aspirational" or ideal set of applications/module groupings have not been formed yet, but a reasonable starting point might be the analysis Vince B. did a couple years ago and shared with the community:  


 Discussion of council questions

Action items

  •