00:09:29 Jenn Colt: https://folio-org.atlassian.net/wiki/spaces/TC/pages/676855870/Draft+report+on+adoption+and+timeline+of+the+Eureka+platform 00:14:45 Wayne Schneider: platform-complete is also technically a yarn platform and performs the function of a reference UI build platform. 00:15:06 Wayne Schneider: Oh, I see, platform-lsp fills that? 00:21:48 Julian Ladisch: OpenAPI documentation: https://github.com/folio-org/mod-scheduler/tree/master/src/main/resources/swagger.api 00:22:11 Wayne Schneider: Actually the Okapi timer is a little more flexible than that FWIW (doesn't really matter at this point) 00:25:30 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. 00:25:41 Craig McNally: Reacted to "OpenAPI documentatio..." with πŸ‘ 00:26:28 Marc Johnson: Reacted to "I think useful to in…" with πŸ‘ 00:27:11 Ingolf Kuss: Reacted to "I think useful to in..." with πŸ‘ 00:28:22 Day, Kevin: I agree with Marc's statement about referencing the ~OKAPI~ Eureka functionality. 00:34:42 Tod Olson: Agreed w/ @Craig McNally , the other councils are looking to TC for guidance on Eureka. 00:39:02 Craig McNally: No, that would be human readable IDs 00:39:06 Craig McNally: ;) 00:39:16 Tod Olson: Reacted to "No, that would be hu..." with πŸ˜† 00:42:29 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. 00:57:28 Tod Olson: Also hard to quantify say "reduced" in this context without measurements to refer to.