Draft report on adoption and timeline of the Eureka platform

Table of contents
Introduction
Implications of Eureka adoption
Eureka adopter support
Timeline
Next steps for councils
Next steps for hosts and implementers
Next steps for EBSCO

Introduction

The community has two key questions to answer:

Does the community adopt Eureka?
On what timeline does the community make Eureka the official FOLIO release?

Implications of Eureka adoption

Changes
- Move from module based platform to application-based platform
- 0005-application-formalization
- 0010-eureka
- Change in maintenance through deprecation of homegrown modules:https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Deprecations
Benefits
- https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Benefits
Challenges
- Uncertainty of non-FSE providers ability to adopt for Sunflower
- Incomplete documentation
- RFC process not completed

Eureka adopter support

Existing support
- End-user early adopter program has begun
- Some documentation exists on the Wiki
Planned support
- Hosting early adopter program will begin in January with GBV and potentially others
Gaps in support
- Additional operational and development support will be needed

Timeline

Sunflower: EBSCO shifts support from Okapi to Eureka
High level requirements/milestones for adoption of Eureka by the community
- People in the community beyond EBSCO/FSE who are confident in operating Eureka
- Developer documentation for working in the Eureka platform
- Replace current platform definition
- Add hosted reference environments that support Eureka
High level requirements for the community to support Okapi after EBSCO shifts to Eureka
- Community support for Okapi-based bugfest environment
- Community support for Okapi-based CSPs
- The Ramsons release of Okapi could try to be used to run the Sunflower modules
How long does the community support Eureka? Does the community shift from Okapi to Eureka in Sunflower?

Timeline if the community transitions in Sunflower:

	Quesnelia	Ramsons	Sunflower	Trillium
EBSCO Primary development platform	Okapi	Okapi	Eureka	Eureka
EBSCO Bugfixing for	Okapi and Eureka	Okapi and Eureka	Eureka	Eureka
Community Bugfixing for	Okapi and Eureka	Okapi and Eureka	Eureka	Eureka
Community Testing (bugfest) - EBSCO hosted	Okapi and Eureka	Okapi and Eureka	Eureka	Eureka
Community Testing (bugfest) - Community	X	X	X	X
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.

Next steps for councils if Eureka is approved

Technical council
- Determine how to approve the large number of modules in time for Sunflower, or agree to approve as a package: https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#New-Components
- Update module approval processes to account for application formalization
Product council
- Support SIGs and POs in implementation of application formalization
Community council

Next steps for community dev ops

Have internally addressed next steps and are planning to engage Eureka pretty deeply in the new year
Gap analysis and further investigation

Next steps for hosts and implementers

Next steps for EBSCO

Continued knowledge transfer to community dev ops teams
Onboard additional hosts into early adopter program