Fedora Mindshare Committee

Fedora Mindshare Committee logo

The Fedora Mindshare Committee is a body focused on representing and supporting the Fedora contributor community, particularly in areas like events, outreach, and recognition. It is undergoing a revamp to become a more functional leadership body, with a focus on regional event support, project-wide recognition, and digital ambassadorship. This restructuring aims to address issues of inactivity and redefine the committee’s role to better serve the evolving needs of the Fedora Project.

Responsabilidades

The Fedora Mindshare Committee has the following responsibilities:

Regional Event Support

  • Support and coordinate budget requests for events in each region (EMEA, LATAM, NA, APAC), acting as a liaison between the regions, the FCA, and the wider committee.

  • Review funding requests, ensuring the regional representative advocates for the sponsorship’s approval and that requests adhere to a clearly defined process (similar to the Fedora Advocate Program).

  • Ensure active regional representation and assist the FCA in planning events.

Recognition Service

  • Recognize the efforts of contributors across the project by working with project teams (QA, Design, Rel-Eng, etc.) to reward contributions.

  • Develop and implement a system for recognition, including:

    • Determine the review frequency (weekly/monthly/per release).

    • Ensure recognized individuals receive a reward (swag, blog post, etc.).

    • Work with the FCA to develop an SOP for identifying recognition efforts.

    • Create metrics to measure the impact of contributions.

  • Present recognition metrics to the Fedora Council regularly.

Digital Ambassadorship

  • Support Digital Ambassadors and integrate them with the Fedora Marketing Team to align with Fedora’s brand and communication goals.

  • Collaborate with the Marketing Team to create and maintain resources, including:

    • Content (e.g. blog posts, tutorials, etc.).

    • Templates for online campaigns (e.g. banners, video scripts, infographics).

    • A training program for Digital Ambassadors on Fedora’s tone, messaging, and values.

    • Workshops (Fedora Classroom) on tools (social media schedulers, analytics platforms, graphic design).

  • Establish and track clear KPIs (engagement rates, follower growth) to measure the impact of Digital Ambassadorship activities, and share regular progress reports with the Mindshare Committee and the Fedora Council.

  • Leverage Digital Ambassadors to bridge in-person and online events, particularly Release Parties, through:

    • Event promotion on social media and encouragement of online participation.

    • Livestream sessions or highlight reels.

    • Gather byte-sized clips from Fedora contributors to help “attach-a-username-to-a-face”.

    • Hosting virtual Release Parties or webinars with interactive sessions (e.g. Q&As, trivia, polls).

    • Publishing post-event blogs summarizing highlights and contributions.

    • Encourage Digital Ambassadors to share personal stories or event photos.

  • Develop and implement a managed social media framework, including:

    • Account Types:

      • Global Accounts (official Fedora accounts managed by the Marketing Team).

      • Regional/Language Accounts (accounts managed by trained Digital Ambassadors).

    • Guidelines and Policies:

      • A clear social media policy (e.g. approval workflows, moderation guidelines, brand tone).

      • Ensuring compliance with the Fedora Code of Conduct.

    • Platform Diversity:

      • Encouraging participation on various platforms (e.g. Twitter/X, Mastodon, Reddit, YouTube, LinkedIn, etc.).

      • Exploring emerging platforms (e.g. BlueSky).

Tomando decisiones

The Fedora Mindshare Committee makes decisions in two ways. It uses "lazy approval" for basic decisions. It uses "full consensus" for more important decisions.

Lazy Approval

The committee uses "lazy approval" for many basic decisions. In this process, the committee assumes that everyone agrees. This is true unless someone objects within a specific timeframe. The timeframe is usually three to seven days. The committee states the timeframe each time. The committee uses this process for decisions that:

  • Have short-term effects.

  • Can be easily reversed.

Any committee member can ask for more time. Any member can ask for the decision to require full consensus.

Full Consensus

The committee uses "full consensus" for more important decisions. For these decisions to pass, they need:

  • Three or more positive votes (+3).

  • No negative votes (-1).

A negative vote stops the decision-making process. It also requires discussion. To be valid, negative votes must include:

  • Specific concerns about the proposal.

  • Suggestions for changes to make the proposal acceptable.

A vote of "0" can show disagreement. It can also show a willingness to accept the decision. Members should explain a "0" vote.

This decision-making model follows Fedora’s "Friends" foundation. This foundation emphasizes finding acceptable consensus. The goal is to benefit free software. This model relies on a community of mutual respect. This is true even when members disagree.

The Mindshare Committee generally discusses issues publicly. Any Fedora Project member can share their opinions. The committee must carefully consider these opinions. However, only committee members' votes count in the final decision.

Dónde encontrar al Fedora Mindshare Committee

El Fedora Mindshare Committee usa las siguientes plataformas de comunicación:

Asíncrona

https://discussion.fedoraproject.org/tag/mindshare

Síncrona

https://matrix.to/#/#mindshare:fedoraproject.org

El {DISCOURSE}[Foro Discourse] es el mejor para comunicación asíncrona. Esto significa que es lo mejor para preguntas y temas que alguien puede responder mas tarde. Es mucho mejor para discusiones largas y enhebradas.

The Fedora Mindshare Committee Matrix room is best for synchronous communication. This means it is best for quick feedback, like a conversation. It is helpful for real-time discussions or getting someone’s attention more quickly.

Administración de tareas basada en ticket

El Fedora Mindshare Committee opera en un flujo de trabajo basado en ticket. Nuestros tickets abiertos están en nuestro repositorio GitLab. Las nuevas tareas se añaden como "issues" en GitLab.

Este es un rastreador público de cuestiones. Si tiene una cuestión sensible privada o de seguridad, confirme la caja This issue is confidential cuando cree la cuestión.

Reuniones

Fedora Mindshare Committee celebra reuniones regulares basadas en texto en una sala Matrix para discutir temas actuales, aclarar cualquier cosa pendiente que pueda resolverse rápidamente y asegurarse de que nada importante se queda en el limbo. El formato de la reunión se pretende que sea actualizaciones rápidas y discusiones largas. Es una buena oportunidad para comunicarse con otros miembros del equipo en tiempo real y comprender lo que está ocurriendo en su área, a la vez que permite que cualquiera del público observe como trabaja el Fedora Mindshare Committee.

¡Encuentre nuestra próxima reunión en nuestro calendario!

Las actas de la reunión se publican automáticamente en Fedora Meetbot Logs.

Composición

The Fedora Mindshare Committee has seven (7) seats with the following roles:

Fedora Community Architect (x1)

The Fedora Community Architect (FCA) is the chairperson of the Fedora Mindshare Committee. This is a permanent position. The FCA’s responsibilities include:

  • Running regular meetings.

  • Managing the Fedora Mindshare Committee’s outreach budget.

  • Supporting other Fedora Mindshare Committee members.

  • Maintaining documentation.

Program Administrators (x4)

Program Administrators are elected positions responsible for managing the Fedora Ambassadors and Advocates programs. They represent and advocate for community members. Their responsibilities include:

  • Running Ambassador/Advocate meetings.

  • Sponsoring events.

  • Counseling Ambassadors.

  • Guiding Ambassadors on resources.

  • Mentoring Advocates.

  • Maintaining documentation.

Program Administrators serve 1-year terms, with two seats elected each release cycle.

Marketing Team Representative (x1)

The Marketing Team Representative is a connection point between the Fedora Marketing Team and the Ambassador/Advocate community. They provide access to Fedora outreach channels. Their responsibility is to help maintain a content calendar related to in-person events.

This is a 1-year appointed position.

Community Operations (CommOps) Representative (x1)

The Community Operations (CommOps) Representative facilitates planning and execution, primarily assisting the FCA.

This is a 1-year appointed position.

Miembros actuales

  • Fedora Community Architect (FCA): Justin W. Wheeler (jflory7)

  • Representante del Embajadores/as: FAmA Nick Bebout (nb)

  • Representante de CommOps: Alberto Rodríguez Sánchez (bt0dotninja / bt0)

  • Website & Apps Representative: Onuralp Sezer (thunderbirdtr)

  • Representante de Diseño: Máirín Duffy (Duffy)

  • Representante de Documentación: Petr Bokoč (pbokoc)

  • Representante del Proyecto de Tutelaje: Smera Goel (smeragoel)

  • Representante Electo: Madeline Peck (madelinepeck) (f37-f38)

  • Representante Electo: Fernando F. Mancera (ffmancera) (f38-f39)

Miembros anteriores

Designado

  • CommOps

    • F27-F28: Justin W. Wheeler (jflory7)

  • Diseño

  • Documentación

    • F27-F31: Brian Exelbierd (bex)

  • FCA

  • Marketing

    • F30-F33: Eduard Lucena (x3mboy)

  • Website & Apps

Elegid@

  • F27-F31: Jared Smith (jsmith)

  • F29-F32: Sumantro Mukherjee (sumantrom)

  • F32-F33: Héctor Louzao (hhlp)

  • F33-F34: Maria Leandro (tatica)

  • F34-F36: Till Maas (till)

  • F37-F38: David Duncan (davdunc)

  • F39-F40: Luis Bazan (lbazan)

  • F40-F41: Luis Bazan (lbazan)

Want to help? Learn how to contribute to Fedora Docs ›