Hello everyone, this is the agenda for the Docs team meeting on Tuesday, June 30 2026 at 13:00 UTC. The meeting takes place on Matrix, in #meeting. A calendar even is available in Fedocal.
Agenda
https://forge.fedoraproject.org/docs/tickets/issues/46 - We’re going to be asking all contributors to use PRs made from forks to make changes from now on - there’s a lot of us now, sometimes a lot of PR traffic, so we need to keep a handle on things
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.
Thanks for preparing the agenda for tomorrow, @pbokoc! This looks good to me. I am happy to own Ticket #50 in the discussion.
Also, it would be good to find some time to triage this ticket for discussion. It has a lot to do with some of the recent conversations on Matrix about the CI pipeline for Fedora Docs. I believe @brettweir:matrix.org was looking into for the entire docs/docs-fp-o pipeline, not just on the individual repo level.
Honestly, while #50 is important, I think there is more to discuss and collaborate on in #49 than #50 right now. In the next few weeks, I anticipate being able to spend more time on the Docs Captain role, since I am hoping to support the Docs Team here with the AI/ML SIG.
Project Organization: A large number of new issues have been created in the Quick Docs and Tickets repositories related to project organization and the Docs Initiative. Team members are encouraged to review and comment.
PR/Forking Guidelines: The team reached a consensus on new contribution guidelines for repositories in the docs/* organization.
Contributions should normally be submitted as a pull request from a fork.
Direct pushes to the main branch will be restricted to repository/content owners and should only be used for urgent fixes.
A minimum of one review will be required before a pull request can be merged.
Docs Build Process: The effort to build the Antora container image within a Forgejo pipeline is complex. In the short term, the team is focusing on improving the local docsbuilder script. For the long term, it was suggested the team align with the Fedora Forge Team’s workflow, which uses Konflux and Quay.io for container builds.
CI Infrastructure: A new, detailed comment from Brett regarding the team’s CI infrastructure was posted in ticket #49, which members are encouraged to review.
“Docs Captains” Pilot Program: A pilot program is being established to create “Docs Captains”—liaisons between the Docs Team and other Fedora SIGs/WGs.
The initial focus is on Kernel/Booting, Multimedia, and the AI/ML SIG.
A key goal is to have subject-matter experts take ownership of relevant documentation to ensure it stays current.
The need for better documentation of content ownership and points of contact was highlighted.
Documentation Security: Red Hat Product Security has raised concerns about some documentation. The team is awaiting a specific list of documents from them before taking action.
Action Items
@pbokoc: Configure repository settings to enforce new PR/forking guidelines (restrict direct pushes, require one review for merges) across all docs/* repositories.
@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.