Hello everyone! 
This is a meeting summary of the Fedora Docs Team meeting held on Tuesday, 16 December 2025. The Fedora Docs Team is responsible for the documentation of the Fedora Project, including the maintenance of the publication system (Antora), content curation, and supporting documentation contributors across the project.
Special Note: This was the first meeting of the Fedora Docs Team in at least a year or two. Consequently, it was a casual check-in meeting rather than one focused on accomplishing specific work items. The discussion was mildly chaotic with high attendance and enthusiasm, but we expect that as we move to a ticket-based workflow, our future meetings will become more focused and planned.
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.
Agenda
The meeting began with a review of the agenda, which focused on introductions, the basic framework of the new initiative, and an overview of immediate next steps.
- Introductions and team member goals
- Overview of the Fedora Docs 2025 Initiative
- Organization of task tracking and repositories
- Plans for advocacy and tooling improvements
- Schedule for upcoming meetings in 2026
Basic Framework: What we expect to do 
The team reviewed the core tasks of the Fedora Docs Team and the recently approved Fedora Docs 2025 Community Initiative. The identified core tasks are as follows:
- Maintenance of the publication system
- Content curation
- Graphical design
- Improving publication tools
- Workshops/training
- Quality Assurance
- Supporting specialist groups/authors
Introductions 
A significant portion of the meeting was dedicated to re-introducing active members and welcoming new interested contributors.
-
Justin (@jflory7): Focused on program management, onboarding, and information architecture.
-
Cornelius (@lochipi): Interested in helping where needed, specifically onboarding and workshops.
-
Petr BokoÄŤ (@pbokoc): Docs initiative co-lead, focusing on keeping docs running and fixing issues.
-
Freya (@venefilyn): Cockpit contributor, interested in AsciiDoc migration.
-
Peter Boy (@pboy): Server WG, Initiative author. Focused on advocacy and visibility of docs.
-
Hristo Marinov (@hricky): Involved with bootc, CoreOS, Atomic Desktops.
-
Chris Idoko (@chris): Badges/DEI. Interested in Design/UX for docs revitalization.
-
Brandon Nielsen (@nielsenb): QA. Emphasized the importance of documentation for usage.
-
Richard (@Yukih): Rust SIG. Interested in reforming the Docs website for better user experience.
-
Jef Spaleta (@jspaleta): Fedora Project Leader. Interested in tracking SIG health regarding documentation.
Cursory Overview: What are we doing next 
Discussion shifted to organizational tasks and technical infrastructure.
-
Organizational Tasks: Mission statement, membership management, and advocating for Docs (events, postings).
-
Task Tracking: There was a discussion on where to centralize task tracking. The team discussed the split between the “Initiative” tracking (specific 2025 goals) and general “Team” maintenance.
-
Current Initiative Tracker: Forgejo Project Board
-
General Tracker: There is a desire to consolidate or clearly designate a “home” repository for general team tasks to avoid confusion with content-specific repositories.
-
Quality Assurance: Ideas were discussed regarding a Forgejo runner to check for “Last content change” to help identify outdated documentation and unresponsive SIGs.
-
Infrastructure: Need to update FAS group membership and permissions.
Next meeting’s topics 
The team looked ahead to 2026.
-
Next Meeting: Tuesday, 13 January 2026, at 13:00 UTC.
-
Anticipated Topics:
-
Advocating for Fedora Docs (events, workshops).
-
Contribution guides.
-
UI/UX improvements to the Antora UI bundle.
-
-
Call for Help: Attendees were encouraged to reflect on areas of passion to volunteer for in the new year.
-
Action: Co-leads (@pboy and @pbokoc) will continue setting up the Projects board on Forgejo.