Skip to end of banner
Go to start of banner

2025-01-08 Eureka Adoption

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Attendees 

Discussion items

TimeItemWhoNotes


1 minScribeAll
Maccabee Levine is next

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.


QuesneliaRamsonsSunflowerTrillium
EBSCO Primary development platformOkapiOkapiEurekaEureka
EBSCO Bugfixing forOkapi and EurekaOkapi and EurekaEurekaEureka
Community Bugfixing forOkapi and EurekaOkapi and EurekaEurekaEureka
Community Testing (bugfest) - EBSCO hostedOkapi and EurekaOkapi and EurekaEurekaEureka
Community Testing (bugfest) - CommunityXXXX
Support for CSPs (critical issues only)

Quesnelia/Okapi
Quesnelia/Eureka

Poppy/Okapi

Ramsons/Okapi
Ramsons/Eureka

Quesnelia/Okapi
Quesnelia/Eureka

Sunflower/Eureka

Ramsons/Okapi
Ramsons/Eureka

Trillium/Eureka

Sunflower/Eureka

Option

Running Sunflower modules
under Ramsons Okapi is
possible but not officially
supported.

Ramsons and Okapi support
ends on Trillium GA.


TimeItemWhoNotes
60 minEureka Adoption AllDraft report on adoption and timeline of the Eureka platform

Notes


Background

Slack conversations:

RFC in preparation:

Relevant dates:

  • Sunflower OST acceptance: Sept 27, 2024
  • Sunflower scope deadline: Sept 27, 2024
  • January tri-council meeting: Jan 13, 2025
  • Sunflower API freeze? Jan 24 2025
  • Sunflower module acceptance deadline: Jan 24, 2025
  • FOLIO support period is the next release (currently in development) and the two latest GA (General availability) releases: PC Supports long-term release and regular release recommendations
  • RFC public review timebox: 1 month
-Zoom Chat


17:04:27 Jenn Colt: https://folio-org.atlassian.net/wiki/spaces/TC/pages/676855870/Draft+report+on+adoption+and+timeline+of+the+Eureka+platform
17:09:43 Wayne Schneider: platform-complete is also technically a yarn platform and performs the function of a reference UI build platform.
17:10:05 Wayne Schneider: Oh, I see, platform-lsp fills that?
17:16:46 Julian Ladisch: OpenAPI documentation: https://github.com/folio-org/mod-scheduler/tree/master/src/main/resources/swagger.api
17:17:09 Wayne Schneider: Actually the Okapi timer is a little more flexible than that FWIW (doesn't really matter at this point)
17:20:28 Tod Olson: I think useful to include the non-code repositories for completeness, even if there's an explicit statement that we don't need formal review for those.
17:20:39 Craig McNally: Reacted to "OpenAPI documentatio..." with 👍
17:21:26 Marc Johnson: Reacted to "I think useful to in…" with 👍
17:22:09 Ingolf Kuss: Reacted to "I think useful to in..." with 👍
17:23:20 Day, Kevin: I agree with Marc's statement about referencing the ~OKAPI~ Eureka functionality.
17:29:40 Tod Olson: Agreed w/ @Craig McNally , the other councils are looking to TC for guidance on Eureka.
17:34:00 Craig McNally: No, that would be human readable IDs
17:34:04 Craig McNally: ;)
17:34:14 Tod Olson: Reacted to "No, that would be hu..." with 😆
17:37:27 Wayne Schneider: FWIW regarding community devop -- not sure more information will be available by early January. We have internally addressed next steps and are planning to engage Eureka pretty deeply in the new year.
17:52:26 Tod Olson: Also hard to quantify say "reduced" in this context without measurements to refer to.



  • No labels