* xref:index.adoc[Council Charter]

  * xref:members.adoc[Current Council Members]

  ** xref:fpl.adoc[Fedora Project Leader]

  ** xref:fca.adoc[Fedora Community Architect]

  == Fedora Discussion (asynchronous)

  The link:{team_asynch_communication}[*#council tag*] on https://discussion.fedoraproject.org/[Fedora Discussion] is the primary space for {team_name} conversations.

  [[discussion-private]]

  === Private mailing list

  We also have a private mailing list: https://lists.fedoraproject.org/admin/lists/council-private@lists.fedoraproject.org/[*council-private*].

  This list is only used for topics that cannot be discussed on the public forum.

  We use it as little as possible.

  [[chat]]

  == Fedora Chat (synchronous)

  [[decisions]]

  It is better to start with an asynchronous conversation, described above.

  This is a public issue tracker.

  However, if you have a privacy- or security-sensitive issue, check the *Private* box when you create the ticket.

  If an issue is not sensitive, the discussion should open and public.

  This position facilitates decision-making on how to best focus that to meet our community's goals and objectives.

  The FCA supports the xref:fpl.adoc[Project Leader] with all things "community" and works directly with the Fedora Leadership to help bring more Heat and Light to the project.

  [[current]]

  == Roles and Responsibilities ==

  [[roles-council]]

  * Participate in decision-making about use of trademarks, project structure, community disputes or complaints, and other such issues

  [[roles-special]]

  [[roles-elections]]

  === Elections ===

  * Ad-hoc election support for other teams when needed

  [[roles-council]]

  * Serve as a member of the {team_name}

  [[roles-misc]]

  === Miscellaneous ===

  The _Fedora Project Leader_ (or _FPL_) is ultimately accountable for everything that happens within Fedora and in particular is responsible for maintaining Red Hat's relationship with Fedora and vice versa.

  They are Fedora's President, CEO, Chair, Fearless Leader, whatever-you-want-to-call-it.

  However the project leader is not a dictator, benevolent or otherwise.

  image::mattdm-2014-fedora10y-thumb.jpg[float="right",50%,link="https://fedoraproject.org/w/uploads/e/e8/Mattdm-2014-fedora10y-small.jpg"]

  https://mattdm.org[Matthew Miller] is the current Fedora Project Leader.

  Matthew created the BU Linux distribution for Boston University in 1999 and maintained that through 2008, when he moved to the Harvard School of Engineering and Applied Sciences to work on high performance computing and this up-and-coming “cloud” thing.

  He has been at Red Hat since 2012, first working on Fedora Cloud and becoming FPL in June 2014.

  overall governance,

  or similar,

  please submit as a pull request

  Thank you!

  {team_summary}

  of the project, named roles appointed by Red Hat, and a variable number

  of seats connected to medium-term project goals. Decisions are made by a

  *consensus process*, in which we work together as a common team to find

  shared solutions and address concerns, with a focus on giving voice

  rather than on balance of power.

  and is responsible for providing advice to and oversight of other Fedora

  governance bodies and teams as needed.

  Responsibilities

  ----------------

  that require leadership and coordination across the various teams and

  subprojects to achieve.

  achieve them.* This is done in consultation with the entire Fedora

  community through transparent, public discussion.

  sponsor(s) to establish an annual budget allocated to support Fedora

  initiatives, including Fedora Ambassadors, Fedora-managed events, and

  other activities which advance the project's goals.

  *trademarks*, is responsible for final *arbitration of complaints*

  related to project policies and for *settling disputes* escalated from

  other committees or subgroups, and may handle *sensitive legal or

  software. It works because we work together in a community of mutual

  respect even when we disagree.

  Fedora project member can make negative or positive votes. It is the

  tally.

  Leader to decide on a resolution. Such a request can be made when issues

  the request.

  === Community Initiative Leads

  Each Community Initiative will be documented with measurable goals, and the Community Initiative Lead is responsible for coordinating efforts to reach those goals, evaluating and reporting on progress, and working regularly with all relevant groups in Fedora to ensure that progress is made.

  === Representatives

  ==== Engineering & Mindshare Representatives

  The DEI Advisor works with {team_name} leadership to represent perspectives and voices of the Fedora community in decision-making and project discussions.

  Additionally, they also lead initiatives to assess and promote equity and inclusion in collaboration with the xref:dei::index.adoc[Fedora DEI Team].

  ==== Elected Representatives

  engineering or mindshare banners, and the community at large. One

  specific responsibility is to represent the voice of individual

  contributors to the Fedora project. Each representative will also work

  during the election process.

  Elections are held twice a year, in concert with the joint Fedora

  election cycle. One seat is selected at each election, and each position

  has a two-election (approximately one year) term. No person who

  === Appointed Leadership Positions

  *Fedora Project Leader*

  The xref:fpl.adoc[Fedora Project Leader] serves as the

  the table, and facilitating the consensus process. He or she is

  accountable for success in all areas of the project, but is not a

  dictator, benevolent or otherwise. The FPL often serves as the public

  needs of project contributors and stakeholders.

  The Fedora Project Leader is hired by Red Hat with the advice and

  *Fedora Community Architect*

  for {team_name} Meetings.

  This position is funded by and hired for by Red Hat, with the approval

  == Coda

  === Meetings

  The {team_name} is not driven by meetings or by tickets, but does hold link:{FWIKI}/Council_Meetings[regular public meetings] (via a chat system or video call).

  All members are expected to regularly communicate what is going on in their area, through blog posts or other public updates.

  All members should strive to attend in person (travel funding is available).

  We also often meet for a day before or after other significant Fedora-related conferences (Flock, DevConf.cz).

  These meetings are not public, but minutes and summary documents will be provided.

  Additionally, the xref:fpl.adoc[Fedora Project Leader] will set aside regular times to meet with the community.

  === Transparency

  Serving on the {team_name} is a significant commitment of time and

  energy. Workload for the various roles will vary, but each will require

  a number of hours every week, and in most cases, the more, the better a

  We recognize that most Fedora community members do not have the luxury

  of working on Fedora full-time or as part of a paid position. The time

  commitment required for these roles comes simply from what is required

  to lead a large project like Fedora, and is not intended to be an

  artificial limit on who can participate. We know that that it can be a

  extra effort to receive, recognize, be responsive to, and meaningfully

  reward the input of contributors offering their individual time.

  Former membership on the {team_name}, along with membership on the

  previous Fedora Board, is documented on the xref:history.adoc[History of

  Document History

  smaller changes (minor wording or formating, etc., without impact on

  meaning) can be found in the

  https://pagure.io/Fedora-Council/council-docs/commits/main[git repository]

  2023-05-04: Rename Fedora Community Action and Impact Coordinator to Fedora Community Architect

  * Elected Representative: *link:{FWIKI}/User:Sumantrom[Sumantro Mukherjee]* _(f37-f38)_

  +

  Sumantro Mukherjee (sumantrom) works in Fedora QA team and takes part in the day to day testing activities.

  He loves to blog technical walkthroughs and running community onboarding calls and classroom.

  Currently, is striving to stay positive and test negative (Covid-19 Jokes) :D

  = Additional Policies

  * Fedora Magazine is the venue for user-targeted communication and the Community Blog is the venue for contributor-targeted communication.

  * The Fedora Project wants to advance free and open source software and as a pragmatic matter we recognize that some infrastructure needs may be best served by using closed source or non-free tools today.

  * Because we value participation over strict bureaucracy ('Friends' foundation!) candidates for Fedora elections may be accepted within a reasonable grace period after the deadline.

    However, be aware that this may mean missing out on Fedora Magazine interviews, town halls, and other opportunities for campaigning.

    We encourage event organizers to specify the language(s) for their event.

  * The {team_name} may choose to withdraw Fedora's support from events or other activities that involve fiscal sponsorship or use of Fedora trademarks when it determines that participation is not in the interests of the Fedora Project.

    Deliberation and reasoning for the decision should be public to the extent possible.

  = Code of Conduct response policy

  ({team_name} IRC meeting, 2018-05-23)

  Teams within Fedora have the freedom to decide what is on- and off-topic for their fora (IRC channel, mailing list, Telegram channel, et cetera).

  Bans for being off-topic in one channel may not be extended to other channels unless the behavior is displayed in that channel as well.

  In this case, each ban should be treated as a separate issue with its own ticket.

  Prior to submitting the Change proposal, the following tasks should be completed:

    File a ticket and participate in related discussion.

  * *Review test cases and release criteria with QA.*

    The QA team will draft test cases and release criteria based on the PRD.

  == History

  = Policy Change policy

  Proposed changes to {team_name} policies must be publicly announced on the link:{team_asynch_communication}[#council tag on Fedora Discussion] and in a link:{COMMBLOG}[Fedora Community Blog] post in order to get feedback from the community.

  ### Survey Schedule

  * **Apr 1st** Open https://pagure.io/fedora-badges/new_issue[Badges ticket] to request badge design & publication

  * **April 1st** Open https://pagure.io/design/new_issue[Design ticket] to request banner design

  * **May 1st** Open https://docs.fedoraproject.org/en-US/websites/[Websites and Apps Team ticket] to request banner published on Fedora sites

  * **May 15-24th** Update LimeSurvey data according to the changes in the Survey Questions accumulated over the last year.

  * **June 1st** Publish link:{COMMBLOG}/[Community Blog] Post promoting survey

  * **June 1st-30th** Survey runs

  ** **June 1st** Announce survey is open for month of June on IRC and Twitter

  ## Storage and process to make changes

  ** PR's reviewed and accepted to markdown file through out the year

  ** git diff to locate the differences and make changes directly in the

     LimeSurvey UI two weeks prior to running survey

  == Goals

  - To gain an understanding of the usage patterns in various Fedora flavours and tooling

  - To analyze trends based on particular tools, preferred media platforms, or role

  - Publish open, anonymous datasets for contributors to analyze.

  - Review and analysis by the Survey team. 

  - Review and analysis by the Mindshare Committee.

  == Survey maintenance

  == How do I get involved?

  == Past Survey CSVs

  participate in the project in any way, be it coding, bug testing,

  docs, graphic design, translations, outreach, etc.

  our Fedora Contributors and Community Members, and to better steward

  the Fedora Project based on data.

  Who gets to see the raw data::

  Who gets to see the summary data::

  Public

  * Who would you first try to contact if you wanted to run a Fedora event/needed swag?

      - Fedora Community Architect

      - Local User Group

      - Fedora Mindshare Committee

      - Regional Fedora Ambassador group

      - Other

      - Yes

      - No

      - I was/am a member now

  = Fedora Team Directory

  "Teams" should be read as a catch-all term for groups in Fedora that may call themselves "Special Interest Groups (SIGs)", "Working Groups", or any other similar term.

  == Intent

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

  The {team_name} uses a link:{team_issue_tracker}[ticket queue] to track decisions and other work.

  If you are looking to start a discussion, consider posting to the link:{team_asynch_communication}[#council tag on Fedora Discussion] first.

  == Issue priorities

  * **OMG Urgent!!!1**: The ticket should be acted on asynchronously as soon as possible.

  * **Needs Review** (default): The ticket needs to be triaged.

  == Issue tags

  Mutliple tags should be applied when appropriate.

  * **budget**: Big-picture budget issues

  * **objectives**

  * **policies**

  * **spending-request**: For as-we-go allocations

  * **trademarks**

  == Voting

  When a vote is called for, the **ticket-vote** tag should be applied.

  If multiple proposals or multiple versions of a proposal have been made, please indicate which the vote applies to.

  Policies for voting and approval are covered xref:index#_making_decisions[elsewhere].

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

  Welcome to the {team_name}!

  You have just joined

  == General expectations

  *Be brave.*

  We expect you to share your ideas and opinions.

  If you are the representative of another group

  (i.e. Diversity & Inclusion, FESCo, and Mindshare Committee representatives),

  you are expected to speak on behalf of the group you represent.

  Share what's going well.

  *Take action.*

  not just _discuss_ things.

  You don't need to wait to be assigned a task.

  If there's something that needs to be done,

  This provides a checklist for all of the places you need to be granted access.

  Don't worry!

  There's not much you need to do there.

  open an issue or ask in xref:_#chat[chat].

  == Communication

  We have asynchronous conversations in the link:{team_asynch_communication}[#council tag] on Fedora Discussion.

  This is a public forum,

  On the rare occasions when we need to discuss confidential matters,

  we have a private mailing list.

  == Meetings

  These are an opportunity to check on the progress of tasks

  and have conversations about open issues.

  Attendance is not mandatory,

  Once a month,

  we hold link:{FWIKI}/Council/Video_Meetings[video meetings].

  These are an opportunity to let the community showcase their work

  Video meetings are open to the community at large.

  From time to time,

  These are private and in-person when possible.

  Attendance at these meetings is strongly encouraged.

  == Tickets