Hey folks! 
Here is the summary of the June 23, 2026, Fedora Community Ops team meeting.
As a core team in the Fedora Mindshare branch, the Community Operations (CommOps) team focuses on community data analysis, contributor experience, and event operations. Today’s meeting focused heavily on infrastructure migrations ahead of the Pagure.io sunset, kicking off planning for the Virtual F45 Release Party, and exploring new avenues to make Fedora news more accessible to newcomers.
Topics discussed in this meeting:
- Migrating Fedora Magazine and Community Blog repositories ahead of the Pagure.io sunset
- Kicking off planning and identifying leads for the Virtual F45 Release Party
- Exploring a Matrix bot for crowdsourcing a human-curated “This Week in Fedora”
- Seeking a new CommOps representative for the Fedora Mindshare Committee
Note: AI (Google Gemini) was used to summarize the transcript of the public video meeting. I reviewed and corrected the AI-generated output before posting.
Executive Summary
The Fedora Community Ops team met to advance several operational and event-based initiatives. A pressing infrastructure item was the impending sunset of Pagure.io in mid-to-late July. Repositories containing Fedora Magazine and Community Blog assets, themes, and proposals must be migrated to Forgejo (commops/tickets#132). Because ownership spans multiple groups, Michal Konečný (@zlopez) volunteered to liaison with the respective team owners to ensure a smooth transition.
Event operations also took center stage as Justin Wheeler (@jflory7) initiated the planning process for the Virtual F45 Release Party, tentatively scheduled for Friday, October 30, 2026 (commops/tickets#143). The team defined key leadership roles, with Carol Chen (@cybette) volunteering for promotion and content, and root_dir stepping up for design. @jflory7 took actions to formally open planning tickets with the Design Team, Matrix WG, and Magazine editors.
Additionally, Michael Winters (@mwinters) presented an initiative to deploy a Matrix chat bot to crowd-source a human-curated “This Week in Fedora” report (commops/tickets#144). Noting that current LLM-generated summaries can be dense for newcomers, the team formally agreed that a crowd-sourced bot (akin to hebbot) is the right direction, and green-lit a proof of concept. Finally, the team put out an open call for a new CommOps representative to the Fedora Mindshare Committee (commops/tickets#145), thanking @gwmngilfen for their service in the role.
Action Items
- @zlopez: Liaison with Fedora Design Team, Fedora Magazine Editorial Team, and Fedora Apps org owners for importing various Pagure repos for the Community Blog and Fedora Magazine to Forgejo
- @jflory7: Summarize next steps and create pointers in ticket #132
- @jflory7: Open a planning ticket with the Fedora Design Team for F45 Release Party design assets, Fedora Matrix WG for room configuration and setup, Fedora Magazine editors for article pitch for August 2026 to announce the party plan
Detailed Meeting Log
Topic: Intros, welcomes, hellos
The meeting kicked off with introductions and greetings. The team engaged in brief chatter regarding post-Flock 2026 wrap-up work. @cybette and @jflory7 noted that revisiting the meeting time might be a good idea soon to avoid ongoing scheduling conflicts.
Ticket: commops/tickets#132 (Fedora Magazine + Community Blog repos)
With Pagure.io targeting a sunset toward mid-to-late July, several repositories containing software themes, design assets, and project management workflows for the Fedora Magazine and Community Blog need to be relocated.
Because these repositories involve the Design Team, the Fedora Magazine Editorial Team, and the Fedora Apps organization, cross-team coordination is required. @zlopez volunteered to act as the liaison to discuss repository relocation with the current owners. @jflory7 took an action item to summarize the next steps in the ticket.
Ticket: commops/tickets#143 (Virtual F45 Release Party: Wrangler Planning Ticket)
@jflory7 introduced the early planning stages for the Virtual F45 Release Party, establishing a tentative target date of Friday, October 30, 2026. The priority is to identify team leads to break up the workload across distinct streams: Wrangler, Speakers, Design, Promotion & Content, and Production & Video.
Several community members stepped up to help:
- @cybette volunteered to assist with content and promotion.
root_direxpressed interest in assisting with graphic design and assets, with guidance from Madeline Peck (@madelinepeck) and Emma Kidney (@ekidney).- @mwinters noted he has unpolished work on a video editing pipeline that could be useful, alongside existing work from Akashdeep Dhar (@t0xic0der), Shounak Dey (@sdglitched), and Adrian Edwards (@moralcode).
@jflory7 took an action item to open the necessary external planning tickets with the Design Team, Matrix WG, and Fedora Magazine to get the gears turning.
Ticket: commops/tickets#144 (A human “this week in Fedora”)
@mwinters pitched the idea of creating a human-curated “This Week in Fedora” utilizing a Matrix chat bot. He noted that while the current LLM-generated summaries are valuable for those following the project closely, they miss the mark for newcomers or low-availability contributors who need a more accessible entry point.
He suggested allowing contributors to submit news piecemeal to a bot, citing successful implementations in GNOME, Ansible, and Bootc (which uses hebbot). @jflory7 shared links to @moralcode’s bctw-config tool built for Bootc as a potential starting point.
The team reached a consensus on the concept:
!agreed Seems like consent that a Matrix chat bot for human-solicited inputs on topics of importance to the community could be the right direction for this ticket.
@mwinters was green-lit to build a proof-of-concept deployment to test the model locally before considering a broader rollout.
Ticket: commops/tickets#145 (New CommOps representative needed on the Mindshare committee)
The team extended a round of applause to @gwmngilfen for their tenure as the CommOps representative to the Fedora Mindshare Committee.
@jflory7 announced an open call for a new representative to take over the role. This position is vital for representing CommOps interests in outreach-level activities and events globally. He pointed interested members to the recent Flock 2026 panel discussion regarding the renewed scope and charter of the Mindshare Committee, noting that @gwmngilfen is available to answer questions about the position.