Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes
1 minScribeAll

Craig McNally will take notes

*

Platform & Application Formalization

Vince

Background:


Notes:

  • A recap/summary of the previous session was provided.  No new questions
  • Questions raised at the last session were reviewed and discussed
    • It was acknowledged that we may need a transition period where we start with larger applications, and once we break apart the dependencies, refine these large applications into smaller, more ideal applications
    • Reiterated that applications are versioned.  If a module gets a version bump, so does it's application
    • The goal here is to bring the TC up to speed on technical topics discussed at University of Chicago a month or two ago.  WOLFcon will be a good opportunity for others to weigh in on both technical and non-technical aspects of these things.
      • The non-technical aspects do need to be considered when formulating technical designs
      • The introduction of applications requires a shift in how the project thinks about releases and related processes
  • An overview/introduction of the formalization of "platforms" was given
  • The "Platform" is the stack, e.g. Folio Core + Folio LSP + Folio LSP Extended = platform
  • We need to be careful about expanding the scope of this proposal, e.g. what goes into the extended tier?  
  • The idea is that this will help simplify the release process.  Most of the modules being introduced lately are specialized, on the fringe, etc. 
  • Extended Tier applications are confirmed to be compatible with a particular Platform/Platform version.
    • Bugfest tests Folio Core + Folio LSP 
    • Confirming compatibility falls upon the development teams providing the extended tier applications
      • How exactly does all of this work?  Probably deserves a dedicated discussion
  • Note that an application may belong to multiple platforms, but a given module can only belong to a single application.
  • More comments regarding the technical vs non-technical aspects of this discussion.

QuestionsAll
  • ...


Zoom Chat-

Marc Johnson 11:13 AM
The framing of service packs for the flower releases being a whole system change, is a non-technical policy and communication decision

Marc Johnson  to  Everyone 11:23 AM
What is the name for the fundamental building blocks of FOLIO, if it isn’t platform? Is it core?

Jenn Colt  to  Everyone 11:24 AM
This again seems not technical

Marc Johnson 11:26 AM
Indeed, most of the reason why folks want their modules in the flower release is marketing (There are some technical considerations for folks who don’t want to / can’t define their own module list)

Maccabee Levine 11:33 AM
Yes, this proposal may be fine from a technical perspective, but it likely creates marketing & product-definition problems for PC & CC
And testing problems per Julian below

Marc Johnson 11:36 AM
For me, I’d prefer we worked the other way round, go from the product challenge to the solution (which is both technical and non-technical)

Maccabee Levine 11:36 AM
That would match how we approve new modules, in that functionality has to be approved first

Jenn Colt 11:41 AM
I think it’s reasonable to propose that the technical aspects create new product options. But what to do with those options don’t seem like they should be part of the proposal.
I guess what to do is included as deciding to do those things provides justification for doing the technical thing, so perhaps I actually agree with doing it the other way around like you say.

Julian Ladisch (VZG)  to  Everyone 11:28 AM
People want modules being included into a flower release to get better testing by the community because it gets deployed to the snapshot and bugfest environments.

Jenn Colt  to  Everyone 11:55 AM
This seems to open a lot of conflict of interest potential which also requires governance input

Tobias Stumpp | University of Tübingen (for SWB/BSZ)  to  Everyone 11:55 AM
*This: Slide "Applicatino Stores and Marketplaces"
Virtual applications are currently both platform and environment dependent. Am I guessing correctly, the basis for an application store is a FOLIO runtime environment?
FOLIO runtime environment, so access to Docker/Kubernetes

Marc Johnson 12:01 PM
Yes, tooling specific deployment is a fundamental challenge with app stores for FOLIO

...