Originally published at: Fedora Operations Architect Weekly – Fedora Community Blog
This weeks report is coming to you on Flock-eve! Looking forward to meeting many of our projects contributors here at Flock and I hope you all enjoy the sessions, whether you’re here in person or joining us remotely on Matrix 
We do have some general news items to share with you though, so read on for this weeks updates.
Events
Flock to Fedora is here! You can join the event from Matrix where sessions from Wednesday 7th & Thursday 8th August will be live streamed. If your timezone makes it hard for you to join us, all of our sessions will be available to watch back on the Fedora YouTube channel after the event.
Devconf.us is also right around the corner and registration is open for folks attending.
Fedora Linux 41
We are now past all change proposal submission dates, so here are some important dates for changes to be completed by, along with other key dates and milestones. The full schedule can be found on the release schedule.
- August 13th – Changes need to be Testable
- August 13th – Mass branching
- August 27th – Changes need to be Complete
- August 27th – Beta Freeze starts
- September 17th – Beta Release (Early Target)
- October 15th – Final Freeze
- October 22nd – Final Release (Early Target)
- November 19th – F39 EOL
Fedora Linux 42 Development
Change proposals for F42 are starting to come through, so here’s a reminder of deadlines for those of you who have a change you would like to propose.
- December 18th – Changes requiring infrastructure changes
- December 24th – Changes requiring mass rebuild
- December 24th – System Wide changes
- January 14th – Self Contained changes
Hot Topics
Git Forge Replacement
The git forge replacement investigation is focusing on the dist-git use cases the projct has and will be comparing GitLab and Forgejo as a replacement. Project hosting, etc is an important piece of this puzzle, but we are intentionally breaking the investigation down to dist-git first as this is at the core of our build and release ability for Fedora. The investigation is active right now, and the initial deadline to have the investigation completed by is October 25th 2024 (after F41 release). We are hoping to have a release-party talk that walks through the investigation in early November, and a decision made by Fedora council and other major stakeholders on what dist-git replacement is best for the project to adopt. We are initially leaning towards this decision being made by the end of the year and the next phase wil be to then to develop a proof of concept using the new git forge and create a migration plan. This phase is targeted for early next year, 2025, and it is super important you submit your user stories to the ARC team now for dist-git. They have a matrix room set up for folks to join and instances of both forgejo and GitLab deployed in CommuniShift and will be rolling out testing plans for the user stories when doing the comparison. Help will both be wanted and needed from the fedora community in the coming weeks to compete this essential investigation.
Submit your user stories to the ARC repository, and if you would like more context, check out the short talk that the team also gave a at the F40 release party. They have a talk scheduled for Flock too this week, so if you do miss it, be sure to catch the recording on the Fedora YouTube channel after the conference finishes.
Help Wanted
Test Days
Keep an eye on the events calendar for other upcoming test days for Fedora Linux 41.
Packages
Please take a look at the latest Orphaned Packages list and adopt one (or two) if you can.
Package reviews are also needed and greatly appreciated.