Fedora Docs Team Meeting (2026-09-22)

Project Discussion
1

Hello everyone, this is the agenda for the Docs team meeting on Tuesday, September 22 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:

  1. Christian Strauf: Upload the list of wiki pages to the cleanup Forgejo issue.
  2. Petr Bokoc (pbokoc): Open an issue to propose new questions for the Release Notes section of the Change Proposal template and circulate it for discussion, likely involving FESCo.

Today’s agenda:

  • Join the new alerts channel!
  • Tickets/#63 - TWIF summary bot
  • Justin’s Captains update
  • Hristo’s updates (i.e. monitoring)

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 agenda, add a comment in this thread.

2

Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-09-22/fedora-docs-team-meeting-2026-09-22.2026-09-22-13.00.log.txt
HTML Log: Meetbot Logs
Text Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-09-22/fedora-docs-team-meeting-2026-09-22.2026-09-22-13.00.txt
HTML Minutes: Meetbot Logs

Key Discussion Points

  • New Alerts Channel: A new Matrix channel, #alerts-docs:fedoraproject.org, has been created for automated notifications like new issues, PRs, and build failures.
  • TWIF Summary Bot (Ticket #63): The team is divided on whether to use the AI-powered “This Week in Fedora” summary bot.
    • Concerns were raised about AI privacy, the uncurated nature of the LLM’s output, and the general necessity of the bot.
    • The main benefit cited was increased visibility for the Docs team.
    • The vote in the ticket is currently tied, and the discussion will continue there.
  • Build Failure Notifications: The notification script in the new alerts channel is too spammy, reporting successes as well as failures. The team agreed on a solution to disable action-run events at the org level and configure them per-repository as needed.
  • Beginner’s Guide Update: The guide is now compatible with the upcoming F45 release. A pull request is in progress to migrate the backup section from kbackup to Vorta.
  • CI/CD Improvements: The team discussed creating a CI workflow in Forgejo to build the documentation sites. This would run in parallel with the existing OpenShift builds and provide more accessible logs and build previews.
  • Collaborative Writing Tool (Ticket #26): There has been no success in getting the Cryptpad tool to work on OpenShift, potentially due to resource constraints.

Action Items

  • pbokoc: Merged the pull request (docs-fp-o/pulls/58) to clean up CI schedules.
  • hricky: Will adjust the organization-level webhook settings to reduce notification spam from successful builds in the alerts channel.
  • hricky: Will open an issue or start a draft to document the team’s scripts and CI/CD tools in the team documentation.
  • egret: Is creating a git cheat sheet for the team docs and will seek input from others.
  • smoliicek: Offered to help investigate a working Cryptpad deployment on OpenShift for collaborative writing.
3

By September 22nd, I should be able to provide an update on the AI/ML SIG Docs Captain ticket. I’ll be working on migrating AI Quick Docs into the AI/ML SIG Docs site in the next week or two.

1 Like