** xref:policy/guiding-policy.adoc[Guiding Policy]

  ** xref:policy/policy-change-policy.adoc[Policy Change Policy]

  ** xref:policy/edition-promotion-policy.adoc[Edition Promotion Policy]

  ** xref:policies.adoc[Additional Policies]

  * Council Procedures

  ** xref:procedures/welcome.adoc[Welcome to Council]

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

  Anyone registered with an account in the https://accounts.fedoraproject.org[Fedora Account System] (FAS) can log in with their account to participate in either platform.

  [[discussion]]

  == Fedora Discussion (asynchronous)

  We use this for discussion within the Council as a team, and it is also the best place for any community member to engage in or start a conversation with us.

  [[discussion-private]]

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

  Note that ticket comments should be kept to a minimum.

  = Fedora Community Architect (FCA)

  :page-aliases: fcaic.adoc

  [.profile-picture]

  image::https://jwf.io/img/logo.jpg[Justin W. Flory (he/him)]

  Justin is a creative maker.

  He is best known as an Open Source contributor and Free Culture advocate originally from the United States.

  [[roles-budget]]

  === Budget ===

  * Ensure that budget is published and tracked transparently, with a public page indicating how each year’s budget is earmarked and its current state.

  [[previous]]

  == Previous Fedora Community Architects

    November 2019 – October 2022 (_Fedora Linux 31 to 37_)

    October 2016 – November 2019 (_Fedora Linux 25 to 31_)

    February 2015 – June 2016 (_Fedora Linux 22 to 24_)

  [[previous-title]]

  = Fedora Program Manager

  The xref:program_management::index.adoc[_Fedora Program Manager_] (or _FPgM_) is the Chief Operating Officer of the Fedora Project.

  [[roles-council]]

  === Council ===

  * Act as Council secretary

  [[roles-misc]]

  Previous Fedora Program Managers:

  == Useful links ==

  * https://fedorapeople.org/groups/schedule[Schedules] in HTML, ICS, and JSON formats

  [[previous]]

  == Previous Fedora Project Leaders

    February 2012 – June 2014 (Fedora 17 – 21)

    July 2010 – February 2012 (Fedora 14 – 16)

    February 2008 – July 2010 (Fedora 9 – 14)

    February 2006 – February 2008 (Fedora Core 5 – Fedora 9)

    August 2005 – February 2006 (Fedora Core 4 & 5)

  Cristian Gafton::

  = Fedora Governance Historical Documents

  Fedora has a long history,

  or similar,

  please submit as a pull request

  to the https://pagure.io/Fedora-Council/council-docs[Council Docs].

\ No newline at end of file

  |===

  |Aleksandra Fedorova | December 2022 - present (f38-)

  term (through the release of F23) and the runner-up for a half term (through

  the release of F22)._

  |===

  |Stephen Gallagher | _Three Editions (Fedora.next)_ | January 2015 – November 2015

  |Akashdeep Dhar | _Websites & Apps Revamp_ | June 2021 – April 2023

  |===

  |===

  |Josh Boyer | some time - November 2018

  |David Cantrell | June 2020 - present

  |===

  |===

  |Christoph Wickert (Outreach Representative) | January 2015 – December 2016

  |Alberto Rodríguez Sánchez | April 2021 - present

  |===

  |===

  |María Leandro    | March 2016 — March 2017

  |Jona Azizaj  | September 2023 - present

  |===

  |===

  |Ben Cotton       | June 2018 – May 2023

  |Jaroslav Reznik  | September 2014 – May 2015

  |===

  |===

  |Marie Nordin      | November 2019 - October 2022

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

  image::council-logo-500px.png[float="right"]

  The Council is composed of a mix of representatives from different areas

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

  ==== Diversity, Equity, & Inclusion (DEI) Advisor

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

  This position is appointed by members of the Fedora DEI Team, with the approval of the Council.

  through the Red Hat Open Source Program Office, and this position facilitates decision-making on how to

  best focus that to meet our collective objectives.

  *Fedora Program Manager*

  scheduling of Fedora releases, and tracks changes and features during

  the development and testing cycle. He or she also assists with the

  creation, maintenance, and execution of formal, repeatable Fedora

  processes. Additionally, the FPgM serves as record keeper and secretary

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

  of the Council.

  === Meetings

  The Council discusses current issues, clear through anything outstanding which can be quickly resolved, and to ensure that nothing urgent is left pending.

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

  === Transparency

  Most meetings are held in public channels, and open to all Fedora users and contributors.

  Occasionally, when personal, private, or sensitive issues need to be discussed, a video call might be used.

  A private mailing list and ticket tracking instance also exist for these situations, but will also only be used when dealing with these uncommon issues.

  Time Commitment

  ~~~~~~~~~~~~~~~

  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

  Council member is able to do the job fully.

  Historical Note

  ~~~~~~~~~~~~~~~

  had five members directly appointed by Red Hat and five elected at

  large. The current structure is more complicated but has a much greater

  proportion of members selected by the community by election or merit. In

  Record of Former Members

  ~~~~~~~~~~~~~~~~~~~~~~~~

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

  Council Membership] page.

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

  2023-02-07: Change name of Objectives to Community Initiatives. See xref:project::initiatives.adoc#history[Community Initiatives History & Future].

  2017-10-20: Move current membership list and contact info to separate docs.

  image::council-badge.png[float="right"]

  +

  Aleksandra Fedorova (bookwar) works on CI for Red Hat Enterprise Linux.

  Aleksandra is one of the organizers of http://ru.fedoracommunity.org/[Russian Fedora] and https://www.meetup.com/Fedora-User-Group-NRW/[Fedora user Group NRW].

  +

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

  He was formerly elected to Mindshare and represented Mindshare to council from (2018-2020).

  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

  +

  David has been involved in the Linux community since the 1997.  He

  first worked on Fedora Core starting with Fedora Core 4 in 2005.  He

  workflow tools.  He is a Fedora Ambassador and a member of the Fedora

  Engineering Steering Committee.

  +

  Alberto 'bt0dotninja' Rodríguez S. describes himself as "a Happy Fedora Contributor".

  As part of the Ambassadors, CommOps, and Fedora-Join and member Mindshare committee,

  he is very interested in finding new ways to grow the contributor base and retain our long-term contributors.

  He loves getting involved in the local communities, make docs and translations, tacos, and cats.

  +

  Read more about the xref:dei:roles:council-advisor.adoc[Fedora Diversity, Equity, & Inclusion Advisor's role] and the current Advisor's xref:dei:roles:council-advisor.adoc#current-advisor[biography]:

  = Additional Policies

  * The Council will have a regular face-to-face in November each year.

  * The Council has no objections to events being held in the local language or in English, and separate events can be held if there are multiple audiences.

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

  * Unspent budget allocated to the $150 event program will be pulled into the Council budget at the end of each fiscal quarter.

    Decisions to withdraw support will be published in venues normally used for Council decisions.

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

    The Council will engage with the committee/group/team that is involved with the event in question to ensure their input is considered.

  = Code of Conduct response policy

  Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response.

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

  Moderators may ban participants for repeatedly engaging in off-topic discussion in contributor channels, however they must file a ticket with the Council's https://pagure.io/CoC/issues[Code of Conduct issue tracker] to report the ban.

  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.

  The FCAIC is empowered to take action on Code of Conduct reports with an additional +1 from another core Council member or the Diversity & Inclusion Advisor and report back to Council.

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

  = Community Publishing Platforms

  v1.1.1, 2020-10-02

  [link=https://creativecommons.org/licenses/by/4.0/]

  image:https://img.shields.io/badge/License-CC%20BY%204.0-lightgrey.svg[License: CC BY 4.0]

  This policy page describes how Community Publishing Platforms are defined, reviewed, and moderated.

  [[what]]

  * Public social media posts

  * Other written communications depending on context

  Community Publishing Platforms include, but are not limited to, the following examples:

  * http://fedoraplanet.org/[Planet]

  * Specific social media accounts

  ** https://www.facebook.com/TheFedoraProject

  Community Publishing Platforms are not actively curated because they rely on decentralized community labor and contributions that are difficult to centrally control.

  Creative Works on Platforms must comply with the xref:project:ROOT:code-of-conduct.adoc[Fedora Code of Conduct].

  If the Fedora Trademark is used, it must comply to this policy.

  = Process for promoting a Fedora deliverable to Edition

  Fedora Editions are curated sets of packages, guidelines and configuration, and artifacts built from those pieces, that address a specific, targeted use-case.

  == Prerequisites

  * The candidate Edition must be backed by a team that holds regular public meetings

    If this includes a name change or a new name (e.g. “Fedora Bilverslue”), plan time for legal review.

    The PRD is used by other teams within Fedora (for example: the QA team uses it to develop release criteria and test cases, the marketing team uses it to develop collateral and positioning).

    The PRD must include:

  ** Market target, including key use cases and personas

  ** Unique policies for installation, updates, etc

  ** Scope of hardware support (including anything that is explicitly unsupported)

  ** Produced deliverables, and whether or not they should be considered release blocking

  NOTE: It is helpful to have someone on the team assigned to handle the bureaucratic tasks

  == Process

  When all of the prerequisites have been met,

  the team submits promotion as a System-Wide Change.

  This ensures that Release Engineering, FESCo, and the community at large have the opportunity to provide input.

  It also implies that the promotion may be delayed to the next release if the appropriate supporting pieces are not in place by the Beta or GA freezes.

  == History

  = Guiding Policy

  The Fedora Project's https://docs.fedoraproject.org/en-US/project/#_our_mission[Vision] is:

  == Context

  The Fedora.next initiative focused the outputs of the project around use cases.

  In 2017, we updated the mission statement to reflect changes in the computing landscape.

  Today, it’s too difficult to build new solutions in Fedora.

  = Policy Change policy

  = How to run the Fedora Annual Contributor Survey 

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

  * **May 24-31st** Review of actual survey in LimeSurvey. Approval from https://docs.fedoraproject.org/en-US/council/fcaic/[FCAIC] is necessary at this step. 

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

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

  ** **June 15th** Two week reminder to fill out survey on IRC and Twitter

  ** **June 30th** One day reminder to fill out survey on IRC and Twitter

  * **July 1st-31st** First round of survey analysis

  * **First weekend in August** Flock to Fedora/Nest with Fedora presentation

  ### Promotion

  Each year we need to write at least two blog posts for the survey. The

  first one is to promote taking the survey, the second features the

  released dataset and any findings. These are published on the

  Discussion.fpo for the month the survey is open.

  * 2021

  #### Fedora Websites Banner

  To help ensure we reach the maximum number of Fedora contributors, we

  promote the survey across as many Fedora spaces as possible including

  and the https://docs.fedoraproject.org/en-US/websites/[Websites and Apps Team].

  The first step is to open a ticket on the https://pagure.io/design/issues[Design Team pagure] to get

  * https://lists.fedorahosted.org/archives/list/hyperkitty-devel@lists.fedorahosted.org/[Hyperkitty]

  * https://docs.fedoraproject.org/en-US/docs/[Docs.fpo]

  * https://accounts.fedoraproject.org/[Accounts.fpo]

  * https://start.fedoraproject.org/[Start.fpo]

  #### Mailing Lists

  = Fedora Annual Contributor Survey Overview

  == Goals

  - Suggest new questions or edits to current questions with a Fedora Council ticket.

  - Analyze data and publish results to the Community Blog and make sure to let the Council know.

  == Past Survey CSVs

  ## Intro

  = Fedora Team Directory

  Council representatives are responsible for periodic evaluation of the teams under their area (D&I, Engineering, and Mindshare).

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

  Teams are responsible for ensuring their entries are up to date.

  They are _not_ responsible for _providing_ the information.

  Representatives may delegate sections of their area as they see fit.

  Checks can be done at any time, but should be done around the branch date for each release at a minimum.

  = Council ticket queue

  When opening a ticket to request a decision from the Council, please describe the issue in detail but have an explicit question (or better, a proposal) to decide on.

  NOTE: Do not file Code of Conduct reports in the Council issue tracker. Those should be filed against the https://pagure.io/coc/issues[Code of Conduct] issue tracker.

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

  Council members should vote by leaving a comment of +1 (in favor), 0 (abstain/no opinion/weakly opposed), or -1 (opposed).

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

  = Welcome to Council

  You have just joined

  (or perhaps you are thinking about joining)

  and now you want to learn your way around.

  If you have any questions,

  Ask for a mentor if you think that would help you.

  == General expectations

  feel free to do it!

  *Ask for help.*

  Don't feel bad if you need to ask for help or if something is unclear.

  Think of it as finding a bug in the documentation!

  == Access

  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.

  == Communication

  This is a public forum,

  so we expect—and welcome—input from community members who are not on Council.

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

  we have a private mailing list.

  For synchronous communication,

  (bridged to the *#fedora-council* IRC channel on https://libera.chat/[Libera.Chat]).

  == Meetings

  or ask for a poll.

  Once a month,

  These are an opportunity to let the community showcase their work

  and ask the Council and broader community for help.

  Video meetings are open to the community at large.

  If you have an idea that needs broader discussion or brainstorming,

  start a thread on Discussion.

  :COMMBLOG: https://communityblog.fedoraproject.org

  :FWIKI: https://fedoraproject.org/wiki

  :YEAR: 2023