...
As of writing, the current stable release of Hyrax (https://github.com/samvera/hyrax/releases/tag/hyrax-v3.6.0) uses Fedora 4 as its back end for both file storage and metadata store. In recent community conversations, the Fedora has Community identified a number of Hyrax implementers that are hoping hope current development efforts would will lead to a migration path to Fedora 6 for Hyrax. To date, however, a development plan for Hyrax 4.x and Fedora 6 has not been documented. The Hyrax Fedora 6 Working Group will work with the Hyrax Product Owner and Tech Lead to identify the work necessary so that for Hyrax is able to use Fedora 6.
The specific objectives are listed below and . The objectives also provide examples of what work might need to be done. The examples listed in the objectives ; these examples are not exhaustive so the working group should feel free to identify additional work not included in the exampleswork or remove work based on its findings.
Identify and complete any pre-work to determine the scope of development. Working with the Fedora Tech Lead, Hyrax Tech Lead, and the Hyrax Product Owner to , identify any pre-work that should occur in order to determine the scope of development (e.g., a Fedora 4 to 6 migration of an example Hyrax / Fedora repository; set up a test Hyrax 4.x and Fedora 6 to determine viability; etc.). Work with existing community members that have engaged in Hyrax / Fedora 6 work that might help to clarify the scope of development (e.g., Emory’s work with Hyrax and Fedora 6; Indiana’s work with Avalon and Fedora 6; etc.).
Determine the scope of development. Working with the Hyrax Tech Lead, the Hyrax Product Owner, and the Fedora Tech Lead, identify the scope of development to ensure Hyrax 4.x works with Fedora 6 (e.g., the group should identify if their goal is to create a greenfield Hyrax 4.x and Fedora 6 or if the goal is to migrate an existing Hyrax 4.x and Fedora 4 repository to Hyrax 4.x and Fedora 6).
Create a high-level outline for the development work. Working with the Hyrax Tech Lead, the Hyrax Product Owner, and the Fedora Tech Lead, create a high-level outline for the development work (e.g., create high-level epics that can later be translated into sprints or be broken up into tickets).
Determine what infrastructure is needed to engage in the scoped development. Identify what infrastructure is needed to ensure that the scoped development is successful (e.g., should Nurax’s existing infrastructure be used or should separate infrastructure be utilized for this development work). If necessary, identify a funding source for additional infrastructure (e.g., request funding from the Samvera Board or request a partner institution host the infrastructure).
Deliverables & Timeframe
Outcomes document. Create an outcomes document based on any pre-work the group has engaged in. At minimum you should include what activities you engaged in and the lessons learned for that activity.
A scoping document. Create a one page document that outlines the problem we are trying to solve, the proposed solution for the problem, the risks associated with the work, and any work that is explicitly out of scope for the effort.
An outline of the development effort. This list should translate be able to translate into epics at a later date, so that these epics can eventually be broken down into tickets a development team might use to complete the work.
An infrastructure proposal. Create a one page proposal outlining what infrastructure is needed in order to complete development for Hyrax / F6 development. Include potential options for funding this infrastructure (if necessary).
Meeting Times & Communication Channels
...