| 5min | Updates on RFCs, PoC, etc | Craig, others | - 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
|