Happy Tuesday, Fedora folks! 
Here is a summary of the recent meeting of the Fedora Docs Team held on Tuesday, January 13th, 2026. The Fedora Docs Team is responsible for the creation, maintenance, and publication of the official documentation for the Fedora Project, operating under the guidance of the Fedora Mindshare Committee.
Topics discussed in this meeting:
- Reviewing 2026 priority areas: Contributor Guidance, Document Analysis, and Collaboration Workflow.
- Identifying task leads for major initiatives.
- Debate on documentation strategy: “Newcomer-friendly” vs. “Experienced Author” support.
- Migration of internal Docs Team documentation to Forgejo.
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
This meeting served as “Part Two” of the 2026 Docs Team Kick-off. The primary objective was to move from high-level topic discussion to identifying specific “task owners” for three key areas: Contributor Guidance & Tooling , Document Analysis & Maintenance , and Collaboration Workflow.
The team discussed the philosophy of contributor documentation. While @nielsenb advocated for keeping barriers low for newcomers to encourage quick fixes, @jflory7 proposed focusing first on the “Experienced Fedora Contributor” persona—ensuring that existing maintainers have robust support and workflows before optimizing for total newcomers.
By the end of the meeting, volunteers were identified for two key pillars. @yukih volunteered to assist with documenting tooling and contributor guidance. @nielsenb volunteered to lead an initial analysis of the Quick Docs repository to prioritize content updates. Additionally, the team leadership committed to migrating the internal Fedora Docs Team documentation from Pagure to Forgejo by the end of January.
Action Items
- @jflory7, @pboy, @pbokoc: Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM).
- @nielsenb: Open a new ticket on Quick Docs repo with an initial analysis of content needs, challenges, and state of affairs so we can prioritize content updates and request help from authors later in 2026. Due: 2026-01-27 (next Fedora Docs Team meeting).
Detailed Meeting Log
Agenda & Action Items
- The meeting began by reviewing the proposed agenda, which included Contributor Guidance, Local Authoring Tools, Document Analysis, and Collaboration.
- The group decided to review these topics holistically rather than one by one, with the specific goal of assigning leads to these initiatives.
- Action Item Check-in: There was a reminder of the ongoing call for help from the previous meeting, encouraging attendees to reflect on areas of passion to volunteer for.
Reviewing Priorities & Task Leads
The Three Pillars
The work for 2026 was categorized into three main buckets:
- Contributor Guidance & Tooling: Documenting the Forgejo workflow, improving local authoring tools, and technical tasks like ARM support.
- Document Analysis & Maintenance: Auditing Quick Docs and Administration Guides for age and accuracy.
- Collaboration Workflow: Finalizing Git branching strategies and evaluating real-time editing tools.
Tooling Discussion
- @yukih noted that documentation for setting up a local Forgejo instance is in progress but questioned if it is necessary for all contributors.
- @pboy emphasized that while we shouldn’t “repeat the internet” regarding basic Git usage, the specific Git workflow for Fedora Docs is a barrier for many writers and requires specific documentation.
- @jflory7 suggested a “Resource Guide” approach—linking to external standard git docs while focusing Fedora documentation on our specific “plumbing” (e.g.,
antora.yml, publishing requests).
Persona Debate
- @jflory7 argued for prioritizing support for experienced Fedora contributors (role models/maintainers) first. The rationale is to stabilize the “end” of the contributor rollercoaster so that when people do contribute, the infrastructure is ready for them.
- @nielsenb expressed concern that if the “quick fix” process has hurdles (like forking in Forgejo), casual contributors will be deterred.
Assignments & Open Floor
- Tooling Lead: @yukih volunteered to help document the tooling and contributor guidance.
- Migration Task: The team realized the internal Fedora Docs Team documentation has not yet been moved to Forgejo. @jflory7, @pboy, and @pbokoc took an action item to complete this migration in January.
- Content Analysis Lead: @nielsenb volunteered to perform a “quick analysis” of the Quick Docs repository to identify content states and needs. This analysis will be submitted as a ticket on the repo by the next meeting.