Fedora Docs Team Meeting (2026-07-14)

Project Discussion
1

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

  • @pbokoc: Configure repository settings to enforce new PR/forking guidelines (restrict direct pushes, require one review for merges) across all docs/* repositories.
    • Not done yet, sorry
  • @hricky: Write a formal proposal for the docsbuilder.sh refactor and re-label ticket #19 as a meeting topic when ready for team discussion.
  • @robinshepheard: Comment on ticket #50 to formally volunteer for the Docs Captain liaison role for the Kernel/Booting and Multimedia topics.
  • All: Review the new comment from Brett in ticket #49 regarding CI infrastructure.
  • All: Help wanted to liaise between the Docs Team and the Kernel/Booting and Multimedia teams as part of the Docs Captains pilot.
    • We do have volunteers for all 3 areas now, @pbokoc to support @robinshepheard (if he’s still interested) with Kernel/Booting docs

Today’s agenda:

  • Docs Captains - The “Docs Captain” roles in various SIGs will require a point of contact on the docs team, someone who will be available to help and answer questions. @jflory7 has proposed two - a docs sponsor and a docs lead.
  • Reporting site build failures - currently when something goes wrong with one of our repos, the site silently fails to build, and sometimes it takes days for anyone to notice - and error logs are only accessible to a couple of people, so if noone with access is around, the problem may be difficult to diagnose. We need to set up a monitoring system that would 1) ping Matrix on build fail, and 2) make the build log available publicly.
  • Quick Docs restructuring (also see the board) - There’s a ton of work to be done on the Quick Docs revamp.

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.

2 Likes
2

  1. Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-14/fedora-docs-team-meeting-2026-07-14.2026-07-14-13.00.log.txt

  2. HTML Log: Meetbot Logs

  3. Text Minutes: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-14/fedora-docs-team-meeting-2026-07-14.2026-07-14-13.00.txt

  4. HTML Minutes: Meetbot Logs

  5. Meeting ended at 2026-07-14 14:00:23 UTC

Key Discussion Points

  • Pagure Shutdown: With Pagure.io shutting down on July 31, 2026, the team is focused on migrating the last two documentation repositories. Team members are reminded to migrate any other personal or team repos from Pagure.
  • Team Docs Restructuring: The team-docs repository is undergoing a major restructuring. Team members are asked to avoid working on it until PR#63 is merged to prevent significant merge conflicts.
  • Fedora Docs Captain Pilot: The team is launching a pilot program for a “Fedora Docs Captain” role to decentralize the documentation workload.
    • The pilot involves three groups: Kernel, Multimedia, and the AI/ML SIG.
    • The proposed structure involves pairing a subject-matter expert from a SIG/WG with an experienced “Fedora Docs Team Sponsor” and a “Fedora Docs Team Lead” to drive the documentation work.
    • The team is looking for volunteers to fill these sponsor/lead roles for the pilot groups.
    • The pilot’s progress will be evaluated around the Fedora 45 release.
  • Build Monitoring and Incident Reporting: The team discussed the need for automated monitoring of the documentation site builds. The goal is to get automatic notifications and public error logs when a build fails, which would eliminate the need for manual reporting procedures.
  • UI/UX Enhancements: A large-scale project has been initiated to improve the UI/UX of the documentation site, particularly for knowledgebase-style pages. Team members are encouraged to review the project board, contribute ideas, and claim issues.

Action Items

  • @pbokoc: Prioritize enforcing the new PR/forking guidelines.
  • @pbokoc: Follow up with RobinSheps regarding the docs lead role for the kernel/booting team.
  • @hricky: Take ownership of the issue regarding monitoring and incident reporting for docs site builds (#53).
  • All: Review the progress on the docsbuilder.sh proposal in PR #46.
  • All: Review the proposal for roles within the “Docs Captain” pilot program and provide feedback in the ticket (#50).
  • All: Review the UI/UX enhancement epic (#51) and its associated project board, provide feedback, and volunteer for tasks if able.