Happy Tuesday, Fedora folks! 
Here is a summary of the recent meeting of the Fedora Docs Team held on February 10, 2026. The Fedora Docs Team is responsible for maintaining the official documentation for the Fedora Project, ensuring that contributors and users alike have access to accurate, well-organized technical information across all Fedora Editions and Spins.
Topics discussed in this meeting:
- Updates from the CentOS Connect Docs Workshop and Fedora Council Strategy Summit.
- Streamlining contributor documentation and focusing on Forgejo as the primary git forge.
- A strategic review of the Quick Docs structure and content maintenance.
- Action item review and infrastructure migration updates.
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.
Executive Summary
The meeting focused heavily on sharing outcomes from the recent Fedora Council Strategy Summit in Tirana and the CentOS Connect workshop in Brussels. A major strategic shift was agreed upon regarding contributor documentation: to reduce maintenance burden and provide clearer direction, the team will deprecate documentation for GitLab and Pagure workflows in favor of a focused Forgejo-first approach.
The team also initiated a “jettison” phase for Quick Docs, led by @nielsenb. The aim is to audit and remove or relocate content that is outdated or better served by other sub-projects. This structural cleanup is intended to reduce the “friction” for new authors by providing a more curated and manageable content base. Additionally, a new Proof of Concept (PoC) was announced to treat Fedora Docs as an “upstream” for CentOS documentation, possibly starting with a comprehensive mail service tutorial. (More discussion was needed.)
Action Items
- @jflory7 Prepare a next meeting topic for opening up the contribution call for the Fedora Docs homepage project.
- @pbokoc Migrate the Fedora Docs “pages” repository from GitLab to Forgejo by the next team meeting on 24 February 2026.
- @pboy Edit the Forgejo issue for the Docs homepage task to describe the “three phases” approach to this ticket.
- @pboy Update Docs Team ticket about Quick Docs with 27 January discussion and next steps for the 24 February 2026 meeting.
- @pboy Follow up with Eli to see if they want to work on Ticket #1, regarding the improvement of the local authoring workflow.
- @nielsenb Add a new comment to Quick Docs #923 to audit which pages might fit into another Fedora Docs site, be owned by another team, or be retired altogether.
Detailed Meeting Log
Follow-up actions & announcements
The Fedora Council held its annual Strategy Summit in Tirana, Albania last week. Docs co-leads @pboy and @pbokoc presented on the Docs Initiative, discussing resource needs and strategic direction. Meanwhile, a Docs workshop at CentOS Connect resulted in a plan to use Fedora Docs as an upstream for CentOS in specific areas, potentially beginning with a mail service tutorial. This will likely require Fedora Linux release-based versioning for certain documentation sets.
Contributor documentation – how to proceed
The team discussed the complexity of maintaining multiple “how-to-contribute” guides for different git forges.
- !agreed: The team will drop GitLab and Pagure-specific pages to focus on the Local Authoring environment and the new Forgejo workflow.
- !idea: The Fedora Join SIG may be leveraged to help newcomers with basic git skills, allowing the Docs team to focus on documentation-specific tooling.
- @pboy will reach out to Eli to lead the refinement of the local authoring documentation (Ticket #1).
Quick Docs content structure – how to proceed
Quick Docs (QD) was identified as a “complex beast” that requires both structural reorganization and content updates.
- !info: The team discussed using categories and tags rather than a rigid navigation bar.
- The “jettison” phase: @nielsenb will lead an audit of QD to identify content that can be moved to other teams, retired, or kept. This is viewed as a prerequisite to meaningful restructuring.
Open Floor
The meeting room was yielded shortly after reaching the open floor due to time constraints. A brief mention was made regarding xmox.nl as a resource for mail server deployment before the meeting adjourned.
I’ll try and adapt my workflow to always include the next meeting date/time visibly in the post.