docs/modules/ROOT/pages/index.adoc

include::ROOT:partial$attributes.adoc[]

= {team_name}

image::mindshare-logo.png[{team_name} logo,75%,float=right]

{team_summary}


[[members]]
== Current members

* xref:#composition-fca[Fedora Community Architect] (FCA):
  *Justin Wheeler* (link:{FWIKI}/User:Jflory7[jflory7])

* xref:#composition-admins[Elected Program Administrators]:
** Akashdeep Dhar (link:{FWIKI}/User:T0xic0der[t0xic0der])
** Luis Bazan (link:{FWIKI}/User:Lbazan[lbazan])
** Mat Holmes (link:{FWIKI}/User:Theprogram[theprogram])
** Samyak Jain (link:{FWIKI}/User:Jnsamyak[jnsamyak])

* xref:#composition-marketing[Marketing Team Representative]:
  _vacant_

* xref:#composition-commops[Community Ops Representative]:
  _vacant_

xref:former-members.adoc[See former members of the {team_name}].


[[responsibilities]]
== Responsibilities

The {team_name} has the following responsibilities:

[[responsibilities-regional-events]]
=== Regional Event Support

_F45–F46 Leads: Justin Wheeler (link:{FWIKI}/User:Jflory7[jflory7]), Mat Holmes (link:{FWIKI}/User:Theprogram[theprogram])_

* 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.

[[responsibilities-recognition]]
=== Recognition Service

_F45–F46 Leads: Luis Bazan (link:{FWIKI}/User:Lbazan[lbazan]), Samyak Jain (link:{FWIKI}/User:Jnsamyak[jnsamyak])_

* 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.

[[responsibilities-ambassadorship]]
=== Digital Ambassadorship

_F45–F46 Lead: Akashdeep Dhar (link:{FWIKI}/User:T0xic0der[t0xic0der])_

Digital Ambassadors are individuals who personally promote Fedora, its projects, and its values by actively interacting with and fostering engagement within online communities.
While the xref:marketing::index.adoc[Marketing Team] directly manages the official Global accounts, Digital Ambassadors focus on outreach on their personal or approved Regional accounts.

The Mindshare Committee and the xref:marketing::index.adoc[Marketing Team] aim to empower Digital Ambassadors by providing structure, support, and resources to ensure alignment with Fedora's brand and communication goals.
Mindshare aims to provide and maintain these resources and act as a touchpoint for the Marketing Team and Digital Ambassadors for support or raising issues.
We encourage Digital Ambassadors to help create and maintain these resources also.

==== Managed Social Media Framework
We will operate a clear social media framework built around different account types: global, community-managed/regional, and personal.

**Global accounts** are the xref:marketing::social-media.adoc#official[official Fedora presence] and are managed by the Marketing Team.

**xref:marketing::social-media.adoc#community[Community-managed accounts]**, or **Regional accounts**, are managed by trained Digital Ambassadors.
These accounts must be vetted by the Marketing Team and Mindshare Committee, and clearly represent a specific corner of the community (e.g., https://f.cz/@fedoracz[Fedora CZ]).
The vetting process considers the account's purpose and grants explicit permission to use the Fedora logo.
It must be clear that these are not Fedora’s official accounts.

[NOTE]
====
Adherence to the xref:project:code-of-conduct:index.adoc[Fedora Code of Conduct] is mandatory for all Community-managed accounts/Regional accounts.
The Marketing Team and Mindshare Committee reserve the right to revoke logo permission and take appropriate action against non-compliant accounts.
====

**Personal accounts** are managed independently by individual Digital Ambassadors who wish to promote Fedora.
They focus on interacting with people as the account owner sees fit.
They are in no way an official Fedora voice and do not require vetting, though we encourage Ambassadors using their personal accounts to adhere to the xref:project:code-of-conduct:index.adoc[Fedora Code of Conduct].

We encourage Digital Ambassadors to maintain presence across diverse platforms (e.g., Mastodon, YouTube, Reddit, LinkedIn) and explore new platforms as they emerge.

Additional support & resources can be found on the xref:marketing::resources.adoc[Marketing Team docs].


[[decisions]]
== Making Decisions

The {team_name} makes decisions in two ways.
It uses "lazy approval" for basic decisions.
It uses "full consensus" for more important decisions.

[[decisions-lazy]]
=== 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.

[[decisions-full]]
=== 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.


[[find-team]]
== Where to find {team_name}

The {team_name} uses the following communication platforms:

Asynchronous:: link:{team_asynch_communication}[{team_asynch_communication}]
Synchronous:: link:{team_synch_communication}[{team_synch_communication}]

The Discourse forum is best for _asynchronous_ communication.
This means it is best for questions or topics that someone may respond to later.
It is better for longer, threaded discussions.

The {team_name} 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.


[[tickets]]
== Ticket-based task management

The {team_name} operates in a ticket-based workflow.
Our open tickets are in our link:{team_issue_tracker}[Forgejo repository].
New tasks are added as "issues" into Forgejo.

*This is a public issue tracker*.
If you have a privacy- or security-sensitive issue, check the _This issue is confidential_ box when creating the issue.


[[meetings]]
== Meetings

The {team_name} holds regular text-based meetings in a Matrix room to discuss current issues, clear through anything outstanding which can be quickly resolved, and ensure that nothing important is left in limbo.
The meeting format is intended to be quick updates and long discussion.
It is a good opportunity to check in with other members of the team in real-time and understand what is going on in their area, while allowing anyone in the public to observe how the {team_name} operate.

link:{team_meetings}[**Find our next meeting on our calendar!**]

The meeting minutes are published automatically https://meetbot.fedoraproject.org/[on Fedora Meetbot Logs].


[[composition]]
== Composition

The {team_name} has seven (7) seats with the following roles:

[[composition-fca]]
=== Fedora Community Architect (x1)

The Fedora Community Architect (FCA) is the chairperson of the {team_name}.
This is a permanent position.
The FCA's responsibilities include:

* Running regular meetings.
* Managing the {team_name}'s outreach budget.
* Supporting other {team_name} members.
* Maintaining documentation.

[[composition-admins]]
=== 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.

[[composition-marketing]]
=== 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.

[[composition-commops]]
=== Community Ops Representative (x1)

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

This is a 1-year appointed position.