2024-04-17 Formalization Working Group Meeting notes

• • Look at roadmap slide from EBSCO user group
    • Milestones specific EBSO. Eureka is the team name, includes all the POC work not just app formalization stuff
    • When the two road maps join is not sure, EBSCO will do work for their customers and also keep ball rolling in community. There are some timing aspects, still want community to adopt, nothing has changed there.
    • "Bugfest" on Eureka is aspirational. Oct 24 will probably more internal than community bugfest. Separate bugfest. Eureka for LC is the driving factor. Hosting/FOLIO at EBSCO.
    • There will be a conversation further down the road about adoption in the community. Driven by LC but believe they will be beneficial.
    • Can apps exist both pre & post Eureka - what is the impact on the cost of development?
      • Apps running in the PoC right now are running on Eureka and are the apps from Orchid
      • Movement of custom FOLIO developed tooling to off the shelf version
      • Eureka using more well established OSS projects
      • Questions re:Kong licensing. EBSCO believes the OSS version will work for FOLIO and it is running in the PoC.
        • Presume forking of those components in case of licensing changes
      • What conversations will there be at WC?
        • Will be some sessions, working on figuring what to do
      • Would like to see things shared more directly with the community and not just from the user group. Community wants to be kept informed.
      • Figure out how to navigate challenge of folks running FOLIO in two different ways
      • Apps will work in existing FOLIO or Eureka platform
      • Can the community and does it want to support both ways of operating FOLIO?
        • Is it sustainable to support both eureka and the current way?
        • Community test with lots of EBSCO help one configuration per bugfest right now. Is testing a second version all on EBSCO?
        • If the community will use both/fund both
        • Costs of the current platform need to be considered
          • Eureka brings in keycloak so FOLIO wouldn't have to spend resources on auth development
        • Need technical discussion to understand how much can pick and choose aspects of Eureka
      • Community needs to be able to decide whether Eureka should become the default platform, whether it is better to have both, to know what resources will be required of them if their system changes, need to understand what's happening.
        • Management summaries of what needs to be done so the community can understand the decision
        • Good steps so the transformation is going well for everyone in the community
      • TC needs more information
        • difference between formalization and Eureka as a whole
        • TC discussion next week is the starting point
      • Big technical change but not solely a technical decision
      • What are viable community options?
  • Jenn: added terminology decision to doc, posted to documentation group
  • Reminder of TC discussion of the Eureka work:
    Where: https://zoom.us/j/935492890 (password: "folio-lsp")
    When: Wednesday 4/24 - 11:00 AM - 12:00 PM ET
    Feedback is here: https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/122323803/Architectural+PoC+Preview+Feedback
    

Draft summary document: https://docs.google.com/document/d/1rc4xgJQsNFlXoHW6lAI7MbF8MzaWDb9QW2eryiiyNTo/edit

Draft of answered questions still to come

Notes:

Didn't get to today

Next steps

• Type your task here, using "@" to assign to a user and "//" to select a due date

Zoom chat:

00:03:25	Tod Olson:	Helpful!
00:06:35	Jenn Colt:	https://folio-org.atlassian.net/wiki/spaces/CC/pages/155353090/2024-04-17+Formalization+Working+Group+Meeting+notes
00:07:20	Charlotte Whitt:	https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1407743/Eureka+Team
00:13:34	Charlotte Whitt:	So LOC will be on Kong from the very beginning (and not  Okapi)?
00:13:55	vbar:	Yes, LoC will be on Eureka
00:15:05	Jenn Colt:	A reminder of the TC discussion next week on this work:
Where: https://zoom.us/j/935492890 (password: "folio-lsp")
When: Wednesday 4/24 - 11:00 AM - 12:00 PM ET
Feedback is here: https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/122323803/Architectural+PoC+Preview+Feedback (edited)
00:15:24	Charlotte Whitt:	Reacted to "A reminder of the TC..." with 🙏🏻
00:18:21	Marc Johnson:	IIUC there is no technical manifestation of apps without Eureka
00:18:38	Marc Johnson:	TC hadn’t had any of those conversations yet
00:21:24	Marc Johnson:	Many Open Source projects have closed variations
00:22:12	Marc Johnson:	Including tools that FOLIO already uses e.g. ES, PostgreSQL (Aurora)
00:22:13	Martin Scholz:	Replying to "Many Open Source pro..."

The question is whether the open source Version would be enough to effectively run Folio
00:23:18	Marc Johnson:	Could we possibly use the session at the TC next week to discuss the technical aspects of Eureka
00:23:30	Charlotte Whitt:	Reacted to "Could we possibly us..." with 🙏🏻
00:23:35	Marc Johnson:	Reacted to "Could we possibly us…" with 🙏🏻
00:23:58	Charlotte Whitt:	Yes - excellent suggestion Marc
00:24:55	vbar:	Replying to "Could we possibly us..."

We are already planning to use the TC Wednesday meeting for this  next week
00:25:37	Marc Johnson:	Reacted to "We are already plann…" with 👍
00:26:40	Kirstin Kemner-Heek:	Reacted to "Could we possibly us..." with 🙏🏻
00:27:11	Charlotte Whitt:	I remember Caitlyn’s statements too, Maccabee
00:38:29	Kirstin Kemner-Heek:	Very clear Kirstin
00:38:39	Maccabee Levine:	Reacted to "Very clear Kirstin" with 👍🏻
00:39:48	Charlotte Whitt:	Reacted to "Very clear Kirstin" with 👍🏻
00:42:25	Wayne Schneider:	I look forward to details on the exact scope of "Eureka" and its architectural foundation.
00:42:42	Kirstin Kemner-Heek:	Reacted to "I look forward to de..." with 👍
00:43:08	Charlotte Whitt:	Reacted to "I look forward to de..." with 💯
00:46:05	Marc Johnson:	That’s why I suggested it was the groups responsibility to facilitate that decision
00:46:07	Charlotte Whitt:	+1 Martin
00:46:26	Marc Johnson:	Much of the community is likely unaware of this challenge
00:46:37	Marc Johnson:	Reacted to "I look forward to de…" with 👍
00:46:42	Kirstin Kemner-Heek:	Reacted to "Much of the communit..." with 💯
00:48:01	Charlotte Whitt:	Reacted to "Much of the communit..." with 💯
00:51:01	Maccabee Levine:	Reacted to "Much of the communit..." with 💯
00:54:22	vbar:	App formalization  does not have to be exclusively tied to Eureka
00:55:45	Marc Johnson:	Replying to "App formalization  d…"
My understanding is that the concept of apps and the tooling are intrinsically part of Eureka and aren’t separate (at least today)

Is that understanding wrong?
00:56:32	Marc Johnson:	Replying to "App formalization  d…"
For example, okapi isn’t being extended to support apps
00:59:36	vbar:	Replying to "App formalization  d..."

Eureka has Manager Apps to bridge the gap between Apps and Modules. They could be used in an Okapi-based platform too
01:00:20	Marc Johnson:	Replying to "App formalization  d…"
Do they work without any of the other tooling of eureka?
01:00:35	Marc Johnson:	Replying to "App formalization  d…"
That’s probably a question for next week
01:00:35	Jenn Colt:	I understood!
01:01:41	vbar:	Replying to "App formalization  d..."

From last WOLFcon:
01:02:18	Kirstin Kemner-Heek:	And how can the TC get this Information?
01:04:22	Marc Johnson:	Replying to "App formalization  d…"
Sure, I assumed that was superseded by Kong replacing okapi
01:05:05	Marc Johnson:	Replying to "And how can the TC g…"
There is session scheduled for next week