Hey folks! 
Here is the summary of the April 21, 2026, Fedora Docs Team meeting.
As a core part of the Fedora Mindshare branch, the Docs Team ensures that Fedora’s official documentation is accurate, accessible, and well-maintained. Today’s meeting focused on modernizing our build infrastructure on Forgejo, managing the archiving of legacy documentation, and sustaining our growing community.
Note: AI (Google Gemini) was used to summarize the Meetbot-generated HTML log of the public meeting. I edited the AI-generated output before making this Fedora Discussion topic. If you notice mistakes, please provide a correction as a reply to this topic.
Links to Meeting Logs
Executive Summary
The team made significant strides in resolving lingering infrastructure challenges following the migration to Forgejo. A primary focus was placed on removing legacy GitLab and Pagure references across our repositories (docs/tickets#19). @korora volunteered to work on this. To address the fragmentation of the docsbuilder.sh scripts and the missing Containerfile, the team is exploring the use of Forgejo’s native container registries to host the Antora build images. Hristo (@hricky) has volunteered to lead this investigation. Additionally, the team successfully bypassed a SHA256 git repository compatibility issue (docs/docs-fp-o#23) thanks to a workaround discovered by @venefilyn, which involves pre-fetching the repositories before the build step.
As Pagure approaches deprecation, the team reached a consensus on establishing a dedicated docs-archive Forgejo organization. This “Docs Graveyard” will preserve historical documentation (including legacy DocBook files) in a read-only state without cluttering our active repositories.
Finally, the community continues to grow and engage. We officially welcomed two new team members, @mwinters and @egret. We also highlighted the upcoming Fedora 44 Release Party this Friday, and the opening of nominations for the 2026 Fedora Heroes recognition program.
Action Items
- @korora: Work on removing references to GitLab and Pagure in the Docs template repository. Provide an update at the next Docs Team meeting.
- @hricky: Test out container registries on Forgejo. Explore how to build containers and publish them in Forgejo container registries via a Forgejo Actions CI pipeline. See if it is possible to locate the Containerfile used to build the custom Fedora Docs UI kit, and if this can be imported into Fedora Forge.
- @venefilyn: Open a Pull Request against the Fedora Docs Antora builder README to add a note about the workaround, so we don’t forget later how we solved this problem / why we pre-fetch the repositories
- @jflory7:
Post a meeting summary on Fedora Discussionand ticket updates for all discussed tickets in today’s meeting
Detailed Meeting Log
Announcements
The meeting kicked off with several exciting community updates:
- F44 Release Party: @pbokoc announced a quick 15-minute talk about the Docs Community Initiative at the upcoming Release Party on Friday (1300-1600 UTC). Attendees are encouraged to RSVP.
- New Members: We officially welcomed Michael Winters (@mwinters) and Eli Ridge (@egret) to the Docs team.
- Fedora Heroes: @jflory7 shared that nominations are open for “Nominate Your Fedora Heroes: Mentor and Contributor Recognition 2026.” Winners will be announced at Flock, and contributors can submit nominations via Fedora Magazine.
Action Items from Last Week
@pbokoc noted that the Beginner’s Guide is still not linked from the frontpage due to CSS untangling. He took an informational action item to complete this soon. @jflory7 noted that it has been great to see the progress made on the Beginner’s Guide.
Ticket: docs/docs-template#18
The team briefly discussed docs/docs-template#18, a freshly opened ticket regarding the Docs template repository. Jocelyn (@korora) volunteered to take this on, as it is relatively straightforward.
Ticket: docs/tickets#19 (Removing GitLab/Pagure References)
This proved to be a substantive topic. @pbokoc requested help fixing the references primarily in the template repository to establish a “known good” setup before propagating the changes elsewhere. @korora took an action item to lead this effort.
However, @cstrauf pointed out that the biggest underlying issue is the missing Containerfile, which builds the custom Fedora Antora styles. @pg-tips and @venefilyn located previous Dockerfiles, leading to a broader discussion about where to host and build the container images now that we are on Forgejo.
@cstrauf noted that fragmentation in the docsbuilder.sh script across various repositories is causing chaos, suggesting that the build system and containers be moved into a submodule. To eliminate this fragmentation, @jflory7 issued a call for a volunteer to explore building containers natively using Forgejo Actions and container registries. @hricky stepped up to take this investigation on, with an update aimed for the May 5th meeting.
Docs Graveyard (Archiving Legacy Content)
@pbokoc announced a plan to handle the large volume of old documentation currently hosted on Pagure. To prevent cluttering the main docs Forgejo organization, he proposed creating a second organization named docs-archive. @jflory7 strongly supported this (+1), emphasizing that every old repository should be archived there with no write activity permitted, aside from potentially updating README files to explain the archive status.
Ticket: docs/docs-fp-o#23 (SHA256 Compatibility)
The team reviewed docs/docs-fp-o#23 concerning SHA256 support in the Antora builder. @venefilyn discovered that the build scripts fail with SHA256 repositories but identified a simple workaround: pre-downloading/fetching the git repositories circumvents the compatibility issue entirely. The team agreed this resolves the immediate problem. @venefilyn took an action item to submit a PR to the README documenting this workaround so the team doesn’t forget why the pre-fetch step exists.
Open Floor
- Inventorying Documentation: @cstrauf asked if there was a formal process for taking inventory of existing docs to determine if they need updating or archiving, or if it remains “best effort.” @pg-tips noted they have done this for Quick Docs and the SysAdmin guide. The team agreed to put this topic on the agenda for the May 5th meeting to formalize a review process.
- Local Authoring Guide: @korora and @egret shared that they are making steady progress on the local authoring guide, converting it to AsciiDoc. They expect it to be ready for team review very soon.
- Closing: @theprogram jokingly thanked the “Master Controller” (a TRON reference), wrapping up the meeting exactly on time.