We have some exciting updates to share about the progress on Fedora Forge:
Documentation Now Live
We’re pleased to announce that Fedora Forge documentation is now live and available on docs.fedoraproject.org!
The documentation includes:
-
Migration guides for moving repositories from Pagure, GitHub, and GitLab to Fedora Forge
-
Administrator documentation covering configuration, management, and maintenance
-
User guides for working with Fedora Forge features and workflows
-
Getting started guides for new users
This documentation suite should help both new and existing users make the most of Fedora Forge.
Soft Launch Progress
The Fedora Forge soft launch is actively underway! We’re pleased to report that several Fedora teams now have their organizations created and are beginning to explore the platform:
New Team Organizations:
-
Server - Supporting the Fedora Server Working Group
-
EPEL - Supporting the EPEL team
Upcoming Migration: The EPEL team is scheduled to migrate some repositories to Fedora Forge next week, marking one of our first significant repository migrations during the soft launch phase.
Want Your Team on Forge? Other Fedora teams and SIGs interested in getting their organization space created can follow our documentation:
How to Request a New Organization/Team
This guide walks through the complete process for requesting new organizations and teams, including all required information and the ticket filing procedure.
Current Status: Staging Environment
Please note: The staging environment (forge.stg.fedoraproject.org) is currently down due to a deployment issue we’re actively working on. This is related to a version detection problem during runtime that’s preventing proper deployment.
Tracking issue: #185 - Forgejo unable to determine correct version at runtime
We’ll update this thread once staging is back online. Once this deployment issue is resolved, both staging and production will be updated to:
-
The newest upstream version of Forgejo
-
Recent Fedora Forge-specific improvements and enhancements
Current Development Cycle
We’ve kicked off a new development cycle with focused work on several key areas:
Primary Goals:
-
Forgejo Actions/Runner: Implementing CI/CD capabilities to enable automated workflows for Fedora Forge repositories (this is our major focus this cycle) -
Deployment Pipeline Improvements: Streamlining our deployment process to reduce complexity and increase reliability -
User Documentation Expansion: Creating more user-focused guides and best practices -
UI Enhancements & Configuration: Implementing interface improvements and configuration updates based on user feedback
The team is particularly excited about the Forgejo Actions/Runner work, which is the start of the story of getting CI for your repositories on Fedora Forge.
You can follow our progress on the Current Project Board.
Get Involved
Questions or Issues?
-
File issues or feature requests: Fedora Forge Issue Tracker
-
Chat with the team: Join us on Matrix
Fedora Forge Team