Date
...
| Time | Item | Who | Notes |
|---|---|---|---|
| 1 min | Scribe | All | Craig McNally is next, but it might be tricky since I will likely be fairly engaged in the conversation. Tod Olson is out (I think) Jason Root will take notesReminder: 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. |
| 60 min | Eureka Adoption | All |
|
| Notes | Craig: What happens if the adoption gets pushed further to another FOLIO release? List of modules for an RFC? - impressive list Julian points out there are 2 decisions here: Do we adopt for Sunflower even though it's technically past that deadline? The approved technology stack is already approved for Sunflower Is there an overlap period for supporting both Okapi/Eureka? SSO/login modules have completely changed in Eureka Marc Johnson: Does the community approve adopting Eureka in the first place? Do we have a special process for this? Points out Ebsco is a large contributor to the community technically The assumption - At some point if Eureka is adopted by the community at large, is it a given that Okapi envs will stop being supported by the community at large? There are a set of decisions that need to be made - Community support? Adoption? Need a transition plan? How do we structure these decisions? Multiple options on the table: Support Eureka and Eureka only from Sunflower. Combined support from Sunflower until a future release. Support Okapi for more long term with transition plan Next steps? Experience in early adopter program? Craig: Cost implications for supporting both Okapi/Eureka Several back-end modules for login no longer needed in Eureka Over time less code that needs to be maintained, management users and tokens handled at a higher level Concrete action items? Jen: Isn't the community technically supporting both at the moment? We are making a decision for the whole community here Is it true that development is supported with Okapi on Sunflower? Or after? Is the early adopter program an actual program? Vince: Lots of effort to test both environments Development could shift to primarily Eureka environments in Rancher New modules have a different workflows, and a different permissions model on the management level New development is being done on Eureka, if it needs to be tested on Okapi - but who would be addressing these issues? Another way is not to do that, and support the other way around Jason: Putting the cart before the horse - still need to vote on adoption or not Asks about what development resources would be shifted or different with Okapi vs Eureka We need to decide if there's a transition plan, because some have stated you can just run on Okapi? Who in the community would support this? Not many outside of Ebsco who have exp. with running the platform right now Kristin: Needs to be able to organize their platforms Points out that this platform is currently only running on AWS infra - no "local" or "non-AWS" examples out there Will Eureka be supported for local installations? Adoption needs to be planned securely and sustainably Locally needs to be vetted for local installations by the community Mark V: The more people that start getting involved in the early adoption, the better off we'll be Overall chicken in egg scenario: Community is blocked on adoption until TC agrees, but community doesn't have experience to help in deciding to adopt Craig, Mark and Vince will come up with narrowed options based on discussion. | ||
| Background | Slack conversations:
RFC in preparation: Relevant dates:
| ||
| - | Zoom Chat |
...