| | | 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
|