Hey Fedora folks! Here is a summary of the Fedora Diversity, Equity, & Inclusion (DEI) Team meeting that took place on Thursday, October 16, 2025.
For context, our team’s mission is to build a more diverse and inclusive Fedora community. We welcome new members and encourage anyone interested to join our discussions and contribute to our work.
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
Several important project-wide updates were shared:
-
OSCAFest’25 & CHAOSS’25 Recap: Fedora contributor @chris published a great recap of his experience at OSCAFest & CHAOSScon Africa 2025 in Lagos, Nigeria. The post covers key takeaways on open source metrics, community building, and onboarding new contributors. Read the post here.
-
AI-Assisted Contributions Policy: The discussion around a new policy for using AI tools in Fedora contributions is nearing its conclusion. A final draft is now under review by the Fedora Council, with a vote expected soon. You can follow the latest developments in the Council ticket and the Discussion forum topic.
-
Fedora Docs 2025 Initiative: A new Fedora Community Initiative has been proposed to revitalize the Fedora Docs team. The goal is to improve the structure and output of our project’s documentation. Community feedback is welcome on the Discussion forum before the Council holds an official vote.
Follow-ups from Last Meeting
The team confirmed that all action items from the previous meeting were completed. This included creating the ticket for our forge migration (#61) and providing feedback on the event location exclusion policy (#57).
Ticket #61: Migrate to Fedora Forge (Forgejo)
The team discussed the plan to migrate our team’s repositories and issue tracker from GitLab to Fedora’s new code forge, located at src.fedoraproject.org.
Since our team does not use private issues, the migration process is expected to be straightforward. The next step is for @lochipi to file a ticket with the Fedora Infrastructure team to request a new organization and assistance with migrating our existing issues. A discussion also took place regarding the best strategy for preserving the history of our old tickets from Pagure and GitLab, ensuring that past decisions remain accessible to the community.
Ticket #45: Supporting DEI & Regional Communities
This discussion focused on how the DEI Team can better support Fedora’s regional communities around the world. There is significant overlap here with the goals of the Fedora Mindshare Committee, which is also working to empower local event organizers.
The team discussed collaborating more closely with Mindshare, improving the process for event funding, and creating clear guides or “blueprints” to help community members organize successful local events. You can review the initial proposal on the Discussion forum and see an example of a community blueprint here.
Open Floor
During the open floor, a link to the latest Mindshare Committee Meeting Summary was shared. It provides more context on their evolving roles and plans to support the community, which is relevant to our work on regional communities.
New Action Items
-
@lochipi & @jonatoni: File a ticket with Fedora Infrastructure to create a new organization/team for the DEI Team on Fedora Forge.
-
@jflory7 & @theprogram: Comment on DEI Team ticket #61 with thoughts on Forgejo migration strategies and preserving historical ticket data.
Thanks to everyone who attended!