Hey folks! 
Here is the summary of the May 5, 2026, Fedora Docs Team meeting, which wrapped up a few minutes ago. As a core part of the Fedora Mindshare branch, the Docs Team ensures that Fedora’s official documentation is accurate, accessible, and well-maintained.
Today’s meeting focused on organization-wide issue label standardization, project board migrations for better triage, and updates on the local workflow authoring guide.
Topics discussed in this meeting:
- Standardizing organization-wide issue labels (docs/tickets#40)
- Updating outdated
docsbuilder.shscripts (docs/tickets#19) - Consolidating the Local Workflow Article (docs/tickets#14)
Note: AI (Google Gemini) was used to summarize the HTML log of the public meeting. I reviewed and corrected the AI-generated output before posting.
Executive Summary
Following the recent release of Fedora Linux 44, Justin Wheeler (@jflory7) announced that nominations for community elections (including Council, FESCo, Mindshare, and EPEL) open on May 7. The team also officially welcomed Jocelyn Gould (@korora) as the newest Docs Team member. Looking ahead, the Docs project board will be migrated to the organization level on Forgejo to unify triage across all docs/* repositories.
A major focus of the meeting was standardizing issue labels across the organization (docs/tickets#40). The team formally agreed to focus on establishing a universal base set of organization-wide labels rather than mandating repo-level labels. A vote to ratify the new label structure is scheduled for the May 19 meeting. Petr Bokoč (@pbokoc) and Peter Boy (@pboy) will prepare a formal proposal ahead of the vote.
The team also discussed the consolidated local workflow article (docs/tickets#14), which is now ready for review. All Docs Team members are encouraged to provide feedback on the draft. Finally, a brief update was given regarding the outdated docsbuilder.sh script (docs/tickets#19), noting that updates need to be applied in the docs-template repository.
Action Items
- @pboy & @pbokoc: Write a clear proposal for issue labels and update Ticket #40 with the proposal, so it is clear to all Docs Team members what is being voted on. Do this at least 48 hours before the next Docs Team meeting on 19 May 2026.
- @pbokoc: Create a first-draft version of issue label howto for Fedora Docs team docs repo, prepare to share on 19 May 2026 team meeting
- @hricky: Add a comment update on progress and next steps to Ticket #19 for updates to the Docs Template repo
- @egret & @korora: Kick off a Matrix team room discussion about a deadline for Ticket #14 and what is sensible for your individual capacities
- @jflory7:
Post a meeting summary from today on Fedora Discussion
Detailed Meeting Log
Announcements & news
@jflory7 opened the meeting by noting the successful release of Fedora Linux 44 and the shift into the F44 release cycle. Nominations for community elections (Fedora Council, FESCo, Mindshare Committee, and EPEL Steering Committee) open on May 7. The team warmly welcomed @korora as a new member.
@jflory7 also announced an upcoming migration of the “Tickets” project board to an organization-level project board in Forgejo (docs/tickets#33). Moving forward, the correct way to triage tickets for meeting discussion will be to add an issue directly to the “To Do” column.
Ticket discussion
Before diving into specifics, @jflory7 and @pbokoc shared that they did some pre-meeting prioritization due to the high volume of tickets. They highlighted Ticket #40 (repo label alignment), Ticket #19 (outdated docsbuilder scripts), and Ticket #14 (local workflow article) as the primary agenda items.
Ticket: docs/tickets#40 ([Repo alignment] Fix labels)
The team engaged in a deep discussion about how to organize issue labels. @pbokoc expressed a desire for a single org-level set of labels instead of keeping them per-repo, noting the current setup is a disorganized mix of legacy imports and Forgejo defaults. @jflory7 linked the current org-wide labels and clarified that organization-wide labels are forced upon every repo under docs/.
Christian Strauf (@cstrauf) and @pboy supported a universal base set of labels to ease onboarding. The team reached a consensus that individual maintainers can still decide if greater specificity is needed via repo-level labels, but the team’s focus should be on the org-level foundation.
!agreed As a team, we should focus this conversation about organization-wide issue labels since it impacts all repos and contributors working under the forge.fp.o/docs organization. We prefer to not get in the business of standardizing repo-level labels, as we believe individual maintainers can decide whether greater specificity is needed beyond the organization-wide labels.
@jflory7 noted the heavy use of exclusive labels (e.g., state/, ?/, scope/) which restrict an issue to only one label from a specific set. @pboy and others requested time to review these structures. The team agreed to time-box feedback and hold a final vote at the next meeting.
!agreed We are putting a team vote requirement on this ticket. All team members are encouraged to share feedback in Ticket #40. On the next team meeting on 19 May 2026, we will record a final vote, ratify, and move on. Docs Team leads will also work on a clear proposal for voting on, and also writing meta docs on the proposed labeling system.
An opportunity for newcomer contribution or documentation improvement was raised:
- !halp There is no documentation about our current label organization system. At the very least, if we do not approve new changes, we need to write up some docs for Docs Team members on how to use the org-level labels consistently.
- !halp Instead of writing a new page, we have an existing page which likely could get a facelift. Yay for not duplicating ourselves!
(Workflow documentation link)
Ticket: docs/tickets#19 (Outdated docsbuilder.sh pulls Antora container w/ EOL nodejs)
@pbokoc noted that Hristo Marinov (@hricky) planned to look into this but was largely AFK for the week. The team confirmed that changes need to be made in the docs-template repository first, and then submodules will be set up to propagate the script to other repositories. @hricky joined briefly to confirm he would look at the script and took an action item to post a status update on the ticket.
Ticket: docs/tickets#14 (Consolidate the Local Workflow Article)
Eli Ridge (@egret) and @korora announced that the Local Workflow draft is ready for review. @cstrauf volunteered to read it and supply feedback.
- !halp All Docs Team members are encouraged to review the local authoring guide that Eli Ridge and Jocelyn Gould (UTC-4) have been hard at work on. See ticket #14 for details and to find a place to share feedback.
To ensure momentum, @egret and @korora took an action item to set a review deadline asynchronously in the Matrix room.
Open floor
Due to the feature-packed agenda, there was no time remaining for the open floor, and the meeting was concluded.