Happy Tuesday, Fedora folks! 
Here is a summary of the recent meeting of the Fedora Community Operations (CommOps) Team held on February 17, 2026. The CommOps Team is responsible for providing tools, resources, and utilities to the Fedora community to help different sub-projects communicate and work together more effectively.
Topics discussed in this meeting:
- Forgejo Migration: The team has officially migrated from Pagure/GitLab to the new Fedora Forgejo instance.
- Repository Housekeeping: Discussions on where specific repositories (Fedora Magazine and Community Blog repositories) should live long-term (e.g., Design or Marketing teams).
- Community Blog Workflow: Revisiting the proposal to move the Community Blog from WordPress to Fedora Discussion.
- Fedora Hatch at SCaLE 23x: Planning promotion and content for the upcoming event in Southern California.
Note: AI (Google Gemini) was used to summarize the transcript of the video meeting. I edited the AI-generated output before making this Fedora Discussion topic. If you notice mistakes, please provide a correction as a reply to this topic.
Executive Summary
The CommOps team met to discuss the status of the recent migration to Forgejo. The migration is largely complete, with the ticket repository and documentation now successfully moved and separated for better navigation. However, the organization profile and older issues require significant triage and cleanup.
The team also revisited the long-standing proposal to migrate the Community Blog from WordPress to Fedora Discussion. The goal is to simplify infrastructure maintenance while ensuring news still reaches external audiences effectively.
Finally, the team coordinated promotion for the upcoming Fedora Hatch at SCaLE 23x. To maximize attendance (“butts in seats”), @shaunm will publish a promotional article on Fedora Magazine rather than the Community Blog, supported by social media amplification.
Action Items
- @jflory7: Follow up with @theprogram and @ilikelinux regarding the status of the Community Blog-to-Discussion migration prototype.
- @neil: Locate and share documentation on how the Ubuntu team uses Discourse to publish documentation to their website.
- @jflory7: Triage the new Forgejo issue tracker and close outdated/legacy issues.
- @shaunm: Write a long-form article for Fedora Magazine promoting Fedora Hatch at SCaLE 23x.
- @shaunm: Promote Fedora Hatch at SCaLE 23x via CentOS social accounts and Matrix.
- @jflory7, @joseph, @ekidney: Assist with cross-promotion for Fedora Hatch at SCaLE 23x on Fedora’s social channels (Mastodon, Instagram, LinkedIn).
- @jflory7: Coordinate with Magazine editors (@glb, @rlengland) regarding the incoming SCaLE 23x article draft from @shaunm.
Detailed Meeting Log
Organizational Changes & Forgejo Migration
- The team confirmed they are officially operating on Forgejo following the migration during CentOS Connect/FOSDEM.
- @jflory7 noted that while the migration is technically complete, the organization profile needs polish.
- A key improvement in the new setup is the separation of the Docs repository from the Tickets repository, making organization and navigation easier compared to the previous GitLab structure.
- @zlopez provided a brief update on the broader Fedora Infrastructure migration to Forgejo, noting that the Ansible repo migration is the current focus, with GitHub migration potentially next.
- @jflory7 highlighted that the Data Working Group now has its own distinct space on Forgejo, meaning data-specific conversations will likely move out of the general CommOps meetings.
Repository Ownership & Housekeeping
- The team reviewed an inquiry regarding the ownership of various repositories (Images, Magazine Planning, Themes).
- @jflory7 proposed realigning these repositories with the teams best suited to manage them:
- Images Repos: Should likely move to the Design Team, as they hold the expertise in brand guidelines and graphic assets.
- Magazine Planning Board: Should likely be a Marketing Team project but needs input from @glb and @rlengland.
- Themes: Could potentially be an Infrastructure project.
- @jflory7 committed to cleaning up the “tickets” issue tracker, noting many issues are leftovers from the 2024 Strategy Initiative and need to be closed to improve hygiene.
Community Blog to Fedora Discussion
- The team revisited the stalled project of moving the Community Blog from WordPress to Fedora Discussion. The last major update was in November 2025.
- @shaunm expressed support for the move to reduce infrastructure debt (one less WordPress instance to secure/maintain) but emphasized the need for a mechanism (like RSS) to ensure press and casual observers still receive announcements.
- @neil mentioned that the Ubuntu team successfully uses Discourse (the software behind Fedora Discussion) to publish content directly to their portals and offered to find documentation on their workflow.
Promotion: Fedora Hatch at SCaLE 23x
- @shaunm announced that Fedora Hatch at SCaLE 23x is happening in three weeks (Friday of SCaLE). This will be in coordination with the SCaLE 23x event owners, @aacosta and @lajuggler.
- The event will feature five talks and a packaging workshop.
- Decision: To reach a broader audience, @shaunm will write the promotional article for Fedora Magazine (user-focused) rather than the Community Blog (contributor-focused).
- @jflory7 notified the Magazine editors (@glb and @rlengland) during the meeting to expect the draft.
- @shaunm and @jflory7 will handle social media cross-promotion on CentOS and Fedora channels respectively.