Fedora Docs Team Meeting (2026-08-25)

Project Discussion
1

Hello everyone, this is the agenda for the Docs team meeting on Tuesday, August 25 2026 at 13:00 UTC. The meeting takes place on Matrix, in #meeting. A calendar event is available in Fedocal.

Agenda

AIs from last meeting:

  • All: Help with the cleanup of old Fedora Docs wiki pages. Instructions are in Forge ticket #43.
    • Christian is working on a script to try to automate this but ran into issues getting data from subcategories; he’ll continue working on it during the weekend. In the meantime, manual help redirecting articles is still welcome.
  • All: Check out the new work-in-progress site builder playground at Making sure you're not a bot!.

Today’s agenda:

  • Team-docs PR#63 - I’ll just merge this now, should be fine
  • pboy is working on frontpage updates (see the board). Progress should be visible on the stage.
  • pbokoc is writing a proposal for a better release notes process. The idea is to provide a set of questions with clear answers to each Change owner that would guide them into providing proper information, i.e. “Who does this change affect”, “What problem does it solve”, etc.

Plus, if there’s time, the usual “open floor” section where anyone can bring up other topics.

If you want to add a topic to the next meeting’s agenda, open a ticket somewhere in docs/ on Forgejo (typically the tickets repo) and add it to the Docs Team Meeting Planner project board, or ask someone in the Docs Matrix room to do it for you.

1 Like
2
  1. Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-25/fedora-docs-team-meeting-2026-08-25.2026-08-25-13.00.log.txt
  2. HTML Log: Meetbot Logs
  3. Text Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-25/fedora-docs-team-meeting-2026-08-25.2026-08-25-13.00.txt
  4. HTML Minutes: Meetbot Logs

Key Discussion Points

  • Wiki Cleanup: The effort to clean up the old Fedora Docs Wiki continues. A script is being developed to automate redirects, but manual help from volunteers is still welcome. Eli Ridge (egret) volunteered to assist.
  • Team Docs Repository: A long-standing pull request that was blocking contributions to the team-docs repository will be merged soon by Petr Bokoč (pbokoc), unblocking further work. There was a brief discussion on the module naming convention (ROOT vs. a named module).
  • “Contribute to Docs” Guide: The team discussed that the guide for contributing to documentation should be written with a general audience in mind, applicable not just to the Docs Team but to any Fedora team managing their own documentation.
  • Docs Frontpage Redesign: Peter Boy (pboy) is working on a redesign of the main documentation page to better highlight contributor documentation. A preview is available on the staging server. The team is seeking ideas for content and visual presentation.
  • Release Notes Process: Petr Bokoč (pbokoc) announced a proposal to improve the documentation process for Release Notes. The initial step will be to update the Change proposal template with clearer questions for Change owners about documentation impact. The long-term goal is to expand the scope of Release Notes with input from various SIGs.

Action Items

  • pbokoc: Open a ticket to track the improvement of the Release Notes process.
  • All: Everyone is invited to provide feedback and ideas on the docs front page redesign in these tickets:
    • For content and structure: #6
    • For visual presentation and styling: #52