Here you can find the strategic priorities for the Fedora Program for a rolling 18-24 month period. This roadmap serves to focus all efforts, both technical and non-technical, for the Fedora program team, Governance Group, Committer and Tech Teams and any associated Working Groups.

The roadmap was developed and tasks prioritized following a year-long strategic planning phase by Fedora Governance in 2022-2023. The Technology Working Group supplemented the strategic planning work and was formed to identify and understand community wants and needs for Fedora. The output of the WG included a Technology Survey, which was done in collaboration with the Research and Innovation Division at Lyrasis, and served to lay the ground work for the prioritization of the following projects.

View Community Roadmap Here

On Going Efforts

1. Continued Migration Support

The Fedora Program team is committed to continued migration support to assist all users getting to Fedora 6.x.

Available Resources:

• • IMLS Migration Toolkit
  • Fedora 4-6 Migration Documentation
  • Community Support via Slack and Google Group Listserv's

2. Hyrax Fedora 6 Working Group Participation

The Fedora Program team participates n the Hyrax Fedora 6 WG as stakeholders in an effort to ensure that all users who wish to deploy Fedora and Samvera have a pathway to achieve this goal. The WG Scope and Deliverables can be found on the Samvera wiki here.

• • This WG hopes to complete the defined deliverables by the end of the 2024 calendar year. 

Prioritized Projects

1. Fedora 6.x Performance Testing - (Present - June 2025)

In collaboration with partners at the Texas Advanced Computing Center at the University of Texas at Austin, this work focuses on specific performance testing of repository infrastructure involving Fedora 6.x, and architecture design in a High Performance Computing (HPC) environment.

Specific Deliverables Include:

• • Fedora 6.x performance results for pre-defined data profiles
  • Optimizations/bug fixes identified through testing
  • Recommendations on infrastructure, architecture and hardware configurations to optimize performance in HPC environment
  • Development of benchmarks specific to repository performance
  • Accurate metrics on speed, performance and scalability of Fedora 6.x
  • Cost analysis of data management related to this work

Estimated time to completion: ~ 12 months with 0.5 FTE resource

2. Dependency Updates for Fedora - (July 2024 - July 2025)

This work will see major dependency updates for fcrepo core and associated components. The API will not change in this work, so this will not be considered for a major version release of Fedora and instead will be tagged as a point release.

Initial Dependencies to Address:

• • Spring
  • Java
  • Velocity
  • Postgres
  • ActiveMQ
  • Jetty
  • Plus any additional nested dependencies

Estimated time to complete: ~12 months with committer investment only

3. Documentation Updates & Improvements (May 2024 - on-going)

This work will be focused on identifying and making improvements to wiki technical documentation. The proposal is to organize documentation sprints to tackle sections in manageable chunks and work through these sprints as needed.

Efforts will be focused on:

• • Navigation and ease of access/search of commonly used pages
  • Priority given to Fedora 6.x documentation onward
    • Will not be attempting to resolve issues in documentation not related to the LTS version (Fedora 6)

Estimated time to complete: Unknown (on-going process)

4. HTML UI Improvements (July 2025 - unknown)

This work will involve an evaluation of the largely out-dated HTML UI to understand how implementers are using it and how they envision being able to use it in the future. There are several known issues and feature requests for the UI, so this work would address those elements in one focused effort.

Feature Considerations:

• • OAI-PMH integration
  • Admin-style dashboard views which could include the following:
    • metrics tracking
    • snapshot repository statistics
  • VPAT and Security/Accessibility compliance considerations
  • New feature requests (ie. transaction capabilities)

Estimated time to complete: Unknown at present