Fedora Mindshare Committee Meeting (2025-11-13): Recognition, Digital Ambassadorship, and Regional Event Planning

jflory7 · November 13, 2025, 12:32pm

Hello everyone! Here is the summary for the Fedora Mindshare Committee meeting held on Thursday, November 13, 2025.

The Mindshare Committee handles the non-technical side of Fedora’s community outreach. This includes supporting our ambassadors, managing event budgets, organizing digital marketing efforts, and fostering contributor recognition.

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.

We discussed several key initiatives during this meeting. Topics included:

Defining the scope of the “Recognition Service” within Mindshare (Ticket #88).
- Discussing the ongoing improvements of the Fedora Badges platform (Tahrir) and contributor metrics.
Refining the definition and responsibilities of “Digital Ambassadorship” (Ticket #89).
Proposing a revival of the regional event budget collection process (Ticket #90).
Canceling the next meeting (Nov 27) due to scheduling conflicts.

Here is a more detailed breakdown of our discussions.

Topic: #88 - Recognition Service in Mindshare

This discussion, led by @gwmngilfen and @t0xic0der, focused on how the Mindshare Committee handles contributor recognition, covering both metrics and badges.

Contributor Metrics

@gwmngilfen presented a resurrected report (using the fedora-infra GitHub org as an example) to spark discussion on contributor metrics. This has been shared with the Data Working Group. A key concern raised was the desire to avoid public “leaderboards,” which can foster unhealthy competition. The committee stressed maintaining a cooperative culture and respecting data privacy (like GDPR/COPPA) by potentially anonymizing public reports.

Fedora Badges improvements

@t0xic0der provided an update on his improvements of the Fedora Badges (Tahrir) platform. The goal for 2026 is to make Badges a more integrated experience by:

Streamlining automated badges.
Adding “badge rarities” for gamification.
Introducing a “Model Context Protocol” (MCP), a small language model (LLM) to lower the barrier for creating and awarding badges using simple text prompts.

Action: All community members are invited to review the discussion and provide feedback on Mindshare Ticket #88.

Topic: #89 - Digital Ambassadorship Responsibilities

@ekidney presented a new draft to clarify the Digital Ambassadorship role. This aims to define how Mindshare supports digital advocacy and manages different social media account types (Global, Personal, and Regional).

The new draft is simpler and clearer. A key idea that gained enthusiasm was the creation of a “Video or PDF covering Fedora’s tone, messaging, and values,” which the Design team could help produce as a valuable asset for all contributors.

The discussion also touched on the need to define a vetting process for regional accounts to ensure they adhere to the Fedora Code of Conduct, especially when using the Fedora logo.

Actions:

@ekidney will iterate on the draft to include the Mindshare representative’s specific role in stewarding this area.
@ekidney plans to submit a Merge Request to update the Mindshare documentation based on this work.
Community feedback is requested on Mindshare Ticket #89.

Topic: #90 - Event Budget Collection Process

@lbazan proposed reviving and modernizing an old, lost process for collecting annual event budgets on a regional basis. This would help with visibility and planning for regional event spending.

The committee discussed the challenges with the old regional definitions (NA, LATAM, EMEA, APAC), which were based on Red Hat’s corporate structure. These definitions often didn’t fit the Fedora community well and sometimes led to funding inequalities.

The new proposal suggests a role like an “event wrangler” who would coordinate between the Mindshare Committee and individual event owners within a specific geographic area. There is a clear need to redefine what “regions” mean for the Fedora community in 2025.