Fedora Docs Team Meeting (2026-04-07): Welcome New Members, Beginner's Guide Updates, and Pagure Sunset

Project Discussion
1

Hey folks :waving_hand: This is a summary of the recent meeting of the Fedora Docs Team held on Tuesday, 7 April 2026. The Fedora Docs Team focuses on producing and maintaining official community and user documentation.

Topics discussed in this meeting:

  • New Member Tickets
  • Beginner’s Guide Status and Review
  • Forgejo Migration Status

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 Fedora Docs Team meeting covered organizational updates, documentation milestones, and infrastructure transitions. The team affirmed the standard onboarding process for new members, requiring three positive votes over a seven-day period for approval. The highly-anticipated Beginner’s Guide has been converted to AsciiDoc and is entering a seven-day proofreading phase before it will be published on Fedora Docs. Eventually, the team hopes to add this Beginner’s Guide to the Fedora Docs home page. Additionally, while GitLab repositories have largely migrated to Forgejo, the team faces an upcoming deadline at Flock 2026 to either migrate or archive twenty remaining Pagure.io Fedora Docs repositories.

Action Items

  • @hricky will share comments regarding Beginner’s Guide content styling and formatting with @cstrauf and @theprogram.
  • All Docs Team members will add any feedback on the Beginner’s Guide in its pre-publishing stage directly to Ticket #8 for the Docs Team or in the Matrix room, #docs:fedoraproject.org.

Detailed Meeting Log

Team News & Announcements

  • Justin Wheeler (@jflory7) attended SCaLE 23x in early March, presenting on the Fedora Docs community, and plans to share a written summary of the event.
  • The Beginner’s Guide repository was successfully created last week, following foundational assembly work by @cstrauf and @theprogram.

New Member Tickets

  • Several new member requests are currently open in the issue tracker, specifically for MatH, Christian Strauf, and Hristo Marinov.
  • The team reiterated the agreed-upon rule that tickets can be fully approved and new members added to the FAS group after seven days and at least three positive votes.
  • Petr BokoÄŤ (@pbokoc) noted that the existing tickets currently have sufficient votes and will process the additions on Friday unless issues arise.
  • The new member nomination form template is working effectively and is recommended for active contributors who are not yet formal group members.

Beginner’s Guide

  • The Beginner’s Guide has been fully converted to AsciiDoc and successfully builds using Antora.
  • The Docs Team formally agreed that the guide’s current language is suitable and that it should be linked directly from the front page of the Fedora Docs website to maximize visibility for new users.
  • The document is currently undergoing a seven-day proofreading period, with a target review deadline set for next Monday.
  • @pbokoc will perform a final review before the guide is officially published to the Antora builder repository.
  • Once the guide is published, Docs Team Ticket #8 will be closed, and all subsequent feedback or bug reports should be filed directly on the Beginner’s Guide Forgejo repository.

Forgejo Migration Status

  • Almost all GitLab repositories have been successfully migrated to the new Forgejo instance.
  • Three unpublished repositories remain to be deleted or archived, and the UI repository is pending a Forgejo runner before it can be migrated.
  • Currently, twenty published repositories on Pagure.io still need to be evaluated and migrated before the platform completely sunsets at Flock 2026.
  • @pbokoc will investigate the status of these older Pagure repositories after the upcoming Fedora 44 release to determine if they still have active maintainers or relevant content.
  • The team debated the necessity of creating a “docs-archives” organization to house dormant or historical repositories, as preserving the discoverability of active content remains a high priority.
  • A clear, formalized proposal is still needed regarding the long-term archiving strategy for older Pagure.io content.

Open Floor

  • @egret raised a time-sensitive question regarding the CommuniShift namespace for F44 draft sharing, but the meeting time expired before a full discussion could occur.
  • Participants were directed to continue this specific conversation in the team’s Matrix room for proper follow-up.