Hello everyone! Here’s a summary of today’s Community Operations (CommOps) team meeting. The CommOps team helps with the people-facing and operational side of the Fedora Project. We know not everyone can attend every meeting, so this summary is to help keep you in the loop.
I chaired today’s meeting since @rwright was out. Several community members were in attendance. The conversation covered several important announcements and three key discussion topics.
Note: I used AI (Google Gemini) to summarize the HTML log of the public meeting, and I reviewed and corrected the AI-generated output afterwards.
Team Announcements & News
This section covered important news and updates relevant to the wider Fedora community.
-
Policy on AI-Assisted Contributions: A final draft for a project-wide policy on using AI tools for contributions is now under review by the Fedora Council. A vote is expected within the next week. You can follow the discussion on the Council ticket and the Fedora Discussion thread.
-
New Guide: “How to Create a Fedora SIG”: Community member @nancywrites has drafted a new documentation page explaining how to create a new Special Interest Group (SIG) in Fedora. The draft is available for review and will soon be submitted as a merge request to the official CommOps documentation.
-
Fedora Docs 2025 Initiative: A new community initiative has been proposed to revitalize the Fedora Docs team. The goal is to improve the structure and process for creating and maintaining Fedora’s documentation. Feedback is welcome on the Fedora Discussion topic before it goes to a formal Council vote.
-
Community Health Metrics & Data Analysis: Community member Michael Winters (@mwinters) is leading an effort to better analyze Fedora’s vast amount of community data. The plan involves creating a “data lakehouse” to structure and analyze historical data from sources like
datagrepper. A proof-of-concept is underway, and he is looking for more contributors interested in this effort.
Discussion Topics
The team held focused discussions on three main topics.
Fedora 43 Release Party Check-in
Planning for the next Fedora Linux Release Party is ongoing.
-
Design: The Design Team is creating promotional artwork, social media graphics, and theming for the event registration page.
-
Content & Speakers: The next step is to coordinate with the speakers for the event. An action was assigned to Shaun McCance (@shaunm) to follow up with @amoloney and @jspaleta on the speaker leads.
-
Logistics: An action was assigned to Neil Hanlon (@neil) to confirm the deadline for speakers to submit pre-recorded videos.
Proposed Fedora Data Working Group
Building on the announcement about community health metrics, the team discussed forming a dedicated Data Working Group.
-
Why?: The goal is to create a focused space for conversations about data engineering, analysis, and community metrics. This would provide a clearer home for this work, attract new contributors, and avoid cluttering the main CommOps channel with technical details. It would also be a place to collaborate with external open source communities like CHAOSS.
-
Next Steps:
-
A new Matrix room,
#data:fedoraproject.org, has been created for these discussions. -
An action was assigned to Michael Winters (@mwinters) to create a formal CommOps GitLab ticket proposing the creation of the Data WG under the CommOps umbrella.
Moving the Community Blog to Fedora Discussion
The team revisited a long-standing proposal to retire the WordPress-based Community Blog (communityblog.fedoraproject.org) and move to a publishing workflow that is native to the Fedora Discussion forum.
-
Why?: This move aims to reduce the overhead of maintaining a separate WordPress instance and centralize community content and interaction on a single platform. It also seeks to ease the workload on the small team of volunteer blog editors.
-
Discussion: The team reviewed the original proposal and discussed the need for more editors. There was also a conversation about using social media management tools (like Buffer) to publish content from Discourse to other platforms.
-
Next Steps: The conversation will continue on the existing Discussion thread. Actions were assigned to propose a timeline for the move, explore social sharing tools, and gather volunteers interested in becoming editors for the new workflow.
The meeting wrapped up with a brief open floor. For more details, you can review the full meeting log. To join the conversation, please find us in the #commops:fedoraproject.org channel on Matrix!