#209 docs(council): Replace "Council" with `{team_name}`
Merged 9 months ago by jflory7. Opened 9 months ago by jflory7.
Fedora-Council/ jflory7/council-docs change/council-team_name-macro  into  main

@@ -1,5 +1,5 @@ 

  * xref:index.adoc[Council Charter]

- * xref:contact.adoc[Contact the Fedora Council]

+ * xref:contact.adoc[Contact the {team_name}]

  * xref:members.adoc[Current Council Members]

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

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

@@ -10,13 +10,13 @@ 

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

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

+ We use this for discussion within the {team_name} 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]]

  === Private mailing list

  

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

- Its membership is restricted to the current Council members and discussions there are not archived.

+ Its membership is restricted to the current {team_name} members and discussions there are not archived.

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

  We use it as little as possible.

  
@@ -24,7 +24,7 @@ 

  [[chat]]

  == Fedora Chat (synchronous)

  

- Council members are also often present on the link:{team_synch_communication}[*#council:fedoraproject.org* Matrix room] on https://chat.fedoraproject.org[chat.fedoraproject.org] (bridged to the *#fedora-council* IRC channel on https://libera.chat/[Libera.Chat]).

+ {team_name} members are also often present on the link:{team_synch_communication}[*#council:fedoraproject.org* Matrix room] on https://chat.fedoraproject.org[chat.fedoraproject.org] (bridged to the *#fedora-council* IRC channel on https://libera.chat/[Libera.Chat]).

  

  

  [[decisions]]
@@ -32,7 +32,7 @@ 

  

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

  

- When you have a specific proposal for the Council to make a decision, open a ticket on the link:{team_issue_tracker}[*Council Pagure instance*].

+ When you have a specific proposal for the {team_name} to make a decision, open a ticket on the link:{team_issue_tracker}[*{team_name} Pagure instance*].

  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.

@@ -9,8 +9,8 @@ 

  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.

  

- The FCA is appointed to the Community Architect seat on the Fedora xref:index.adoc[Council], Fedora’s top-level community leadership and governance body.

- The Council is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora Community.

+ The FCA is appointed to the Community Architect seat on the xref:index.adoc[{team_name}], Fedora’s top-level community leadership and governance body.

+ The {team_name} is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora community.

  

  

  [[current]]
@@ -38,10 +38,10 @@ 

  == Roles and Responsibilities ==

  

  [[roles-council]]

- === Council ===

+ === {team_name} ===

  

- * Work with other Council members to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them

- * Primary Council member with responsibility for the development of the annual Fedora community budget

+ * Work with other {team_name} members to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them

+ * Primary {team_name} member with responsibility for the development of the annual Fedora community budget

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

  

  [[roles-special]]

@@ -33,14 +33,14 @@ 

  [[roles-elections]]

  === Elections ===

  

- * Managing xref:program_management::elections.adoc[elections] for Council, FESCo, and Mindshare

+ * Managing xref:program_management::elections.adoc[elections] for {team_name}, FESCo, and Mindshare

  * Ad-hoc election support for other teams when needed

  

  [[roles-council]]

- === Council ===

+ === {team_name} ===

  

  * Serve as a member of the {team_name}

- * Act as Council secretary

+ * Act as {team_name} secretary

  

  [[roles-misc]]

  === Miscellaneous ===

@@ -7,12 +7,12 @@ 

  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.

- The FPL chairs the Fedora xref:index.adoc[Council].

+ The FPL chairs the xref:index.adoc[{team_name}].

  

  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.

- He led the Fedora.next initiative for a strategic approach to Fedora's second decade, as well as the transition from the Fedora Board to the current Council governance model.

+ He led the Fedora.next initiative for a strategic approach to Fedora's second decade, as well as the transition from the Fedora Board to the current {team_name} governance model.

  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.

  

@@ -25,5 +25,5 @@ 

  overall governance,

  or similar,

  please submit as a pull request

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

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

  Thank you!

@@ -6,21 +6,21 @@ 

  

  {team_summary}

  

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

+ The {team_name} is composed of a mix of representatives from different areas

  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.

  

- The Council is ultimately accountable for the Fedora Project as a whole,

+ The {team_name} is ultimately accountable for the Fedora Project as a whole,

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

  governance bodies and teams as needed.

  

  Responsibilities

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

  

- The Council is responsible for issues of strategic importance for Fedora

+ The {team_name} is responsible for issues of strategic importance for Fedora

  that require leadership and coordination across the various teams and

  subprojects to achieve.

  
@@ -29,12 +29,12 @@ 

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

  community through transparent, public discussion.

  

- The Council *governs Fedora's financial resources*, working with our

+ The {team_name} *governs Fedora's financial resources*, working with our

  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.

  

- The Council also decides on issues regarding use of the Fedora

+ The {team_name} also decides on issues regarding use of the Fedora

  *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
@@ -84,17 +84,17 @@ 

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

  respect even when we disagree.

  

- In general, the Council conducts business in public discussion, and any

+ In general, the {team_name} conducts business in public discussion, and any

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

- duty of the Council to take concerns raised in this way into serious

- consideration, but only Council members' votes are binding in the final

+ duty of the {team_name} to take concerns raised in this way into serious

+ consideration, but only {team_name} members' votes are binding in the final

  tally.

  

- When consensus can't be reached, the Council may ask the Fedora Project

+ When consensus can't be reached, the {team_name} may ask the Fedora Project

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

- leading to negative votes are outstanding and all Council members agree

- that the Council is deadlocked, or if the dispute is unresolved after

- fourteen days and a simple majority of Council members are in favor of

+ leading to negative votes are outstanding and all {team_name} members agree

+ that the {team_name} is deadlocked, or if the dispute is unresolved after

+ fourteen days and a simple majority of {team_name} members are in favor of

  the request.

  

  
@@ -102,14 +102,14 @@ 

  

  === Community Initiative Leads

  

- On an ongoing basis, including sessions at Flock and in public online meetings, the Council will identify two to four key xref:project::initiatives.adoc[Community Initiatives] with a timeframe of approximately eighteen months, and appoint *Community Initiative Leads* for each goal.

- These will serve as Council members.

+ On an ongoing basis, including sessions at Flock and in public online meetings, the {team_name} will identify two to four key xref:project::initiatives.adoc[Community Initiatives] with a timeframe of approximately eighteen months, and appoint *Community Initiative Leads* for each goal.

+ These will serve as {team_name} members.

  

  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

  

- The Council also includes five representative seats, an *Engineering Representative*, a *Mindshare Representative*, a *DEI Advisor* and two *Elected Representatives*.

+ The {team_name} also includes five representative seats, an *Engineering Representative*, a *Mindshare Representative*, a *DEI Advisor* and two *Elected Representatives*.

  

  ==== Engineering & Mindshare Representatives

  
@@ -132,7 +132,7 @@ 

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

  

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

+ This position is appointed by members of the Fedora DEI Team, with the approval of the {team_name}.

  

  ==== Elected Representatives

  
@@ -140,21 +140,21 @@ 

  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

- on specific goals which she or he brings to the Council as highlighted

+ on specific goals which she or he brings to the {team_name} as highlighted

  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

- currently holds another Council seat can be elected. If a seat becomes

- vacant, the Council will arrange for a temporary replacement.

+ currently holds another {team_name} seat can be elected. If a seat becomes

+ vacant, the {team_name} will arrange for a temporary replacement.

  

  === Appointed Leadership Positions

  

  *Fedora Project Leader*

  

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

- chair of the Council, organizing discussion agendas, bringing issues to

+ chair of the {team_name}, organizing discussion agendas, bringing issues to

  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
@@ -163,7 +163,7 @@ 

  needs of project contributors and stakeholders.

  

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

- consent of the Council.

+ consent of the {team_name}.

  

  *Fedora Community Architect*

  
@@ -183,7 +183,7 @@ 

  for {team_name} Meetings.

  

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

- of the Council.

+ of the {team_name}.

  

  

  == Coda
@@ -191,16 +191,16 @@ 

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

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

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

  

- The Council holds a multi-day, face-to-face meeting annually.

+ The {team_name} holds a multi-day, face-to-face meeting annually.

  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.

- Attendance is not mandatory for all Council members but is encouraged.

+ Attendance is not mandatory for all {team_name} members but is encouraged.

  

  === Transparency

  
@@ -218,14 +218,14 @@ 

  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

- Council member is able to do the job fully.

+ {team_name} member is able to do the job fully.

  

  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

- _pragmatic_ limit, and for that reason, the Council is responsible for

+ _pragmatic_ limit, and for that reason, the {team_name} is responsible for

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

  reward the input of contributors offering their individual time.

  
@@ -271,7 +271,7 @@ 

  

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

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

- Council Membership] page.

+ {team_name} Membership] page.

  

  

  Document History
@@ -283,7 +283,7 @@ 

  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]

- for Council documents.

+ for {team_name} documents.

  

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

  

@@ -13,7 +13,7 @@ 

  * 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 was formerly elected to Mindshare and represented Mindshare to council from (2018-2020).

+ He was formerly elected to Mindshare and represented Mindshare to {team_name} 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

  

@@ -2,19 +2,19 @@ 

  

  = Additional Policies

  

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

-   The region will be dependent on the location of Council members at the time.

-   We will also conduct in-person meetings at Flock and DevConf.CZ for Council members in attendance.

+ * The {team_name} will have a regular face-to-face in November each year.

+   The region will be dependent on the location of {team_name} members at the time.

+   We will also conduct in-person meetings at Flock and DevConf.CZ for {team_name} members in attendance.

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

- * The Council supports greater efficiency in the infrastructure to allow more to be done, even when this means that we move away from self-hosted or self-maintained infrastructure.

+ * The {team_name} supports greater efficiency in the infrastructure to allow more to be done, even when this means that we move away from self-hosted or self-maintained infrastructure.

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

-   Therefore the Council is willing to accept closed source or non-free tools in Fedora’s infrastructure where free and open source tools are not viable or not available.

+   Therefore the {team_name} is willing to accept closed source or non-free tools in Fedora’s infrastructure where free and open source tools are not viable or not available.

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

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

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

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

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

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

+   Decisions to withdraw support will be published in venues normally used for {team_name} 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.

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

@@ -2,14 +2,14 @@ 

  

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

+ Once a ticket notifying us of a code of conduct issue has been filed, the {team_name} 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 {team_name}'s initial response.

  

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

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

+ Moderators may ban participants for repeatedly engaging in off-topic discussion in contributor channels, however they must file a ticket with the {team_name}'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.

- Community members who wish to appeal the ban may file a link:{team_issue_tracker}/issues[ticket with the Council].

+ Community members who wish to appeal the ban may file a link:{team_issue_tracker}/issues[ticket with the {team_name}].

  

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

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

@@ -56,7 +56,7 @@ 

  

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

  

- * *Approval from the Council.*

+ * *Approval from the {team_name}.*

    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.
@@ -82,4 +82,4 @@ 

  

  == History

  

- This policy was approved in link:{team_issue_tracker}/issue/296[Council ticket #296].

+ This policy was approved in link:{team_issue_tracker}/issue/296[{team_name} ticket #296].

@@ -3,5 +3,5 @@ 

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

- After a minimum of two calendar weeks, the Council may vote on the proposed change using the *full consensus* voting model.

- After approval, the change is reflected on the xref:policies.adoc[Council policies page].

+ After a minimum of two calendar weeks, the {team_name} may vote on the proposed change using the *full consensus* voting model.

+ After approval, the change is reflected on the xref:policies.adoc[{team_name} policies page].

@@ -4,12 +4,12 @@ 

  

  ### Survey Schedule

  

- * **Apr 1st** Open link:{team_issue_tracker}/new_issue[Council ticket] to track progress and collect feedback

+ * **Apr 1st** Open link:{team_issue_tracker}/new_issue[{team_name} ticket] to track progress and collect feedback

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

+ * **May 24-31st** Review of actual survey in LimeSurvey. Approval from xref:fca.adoc[FCA] is necessary at this step.

  * **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
@@ -96,7 +96,7 @@ 

  

  ## Storage and process to make changes

  

- * Take markdown file in Council repo

+ * Take markdown file in {team_name} repo

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

@@ -4,7 +4,7 @@ 

  

  == Goals

  

- In 2021 the Council ran the first Fedora Annual Contributor Survey. We intend to improve and iterate year over year to help achieve the following goals:

+ In 2021 the {team_name} ran the first Fedora Annual Contributor Survey. We intend to improve and iterate year over year to help achieve the following 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
@@ -20,7 +20,7 @@ 

  

  - Publish open, anonymous datasets for contributors to analyze.

  - Review and analysis by the Survey team. 

- - Review and analysis by the Fedora Council. 

+ - Review and analysis by the {team_name}.

  - Review and analysis by the Mindshare Committee.

  

  == Survey maintenance
@@ -38,9 +38,9 @@ 

  

  == How do I get involved?

  

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

- - Provide feedback and share ideas about the survey with the Fedora Council via link:{team_asynch_communication}[Discussion site] and use the tag #council

+ - Suggest new questions or edits to current questions with a {team_name} ticket.

+ - Analyze data and publish results to the Community Blog and make sure to let the {team_name} know.

+ - Provide feedback and share ideas about the survey with the {team_name} via link:{team_asynch_communication}[Discussion site] and use the tag #council

  

  == Past Survey CSVs

  

@@ -14,12 +14,12 @@ 

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

  docs, graphic design, translations, outreach, etc.

  

- This survey is being ran by the Fedora Council to better understand

+ This survey is being ran by the {team_name} to better understand

  our Fedora Contributors and Community Members, and to better steward

  the Fedora Project based on data.

  

  Who gets to see the raw data::

- Fedora Council members and survey moderator (vsiddhar@redhat.com)

+ {team_name} members and survey moderator (vsiddhar@redhat.com)

      

  Who gets to see the summary data::

  Public
@@ -396,13 +396,13 @@ 

  

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

      - Fedora Community Architect

-     - Fedora Council

+     - {team_name}

      - Local User Group

      - Fedora Mindshare Committee

      - Regional Fedora Ambassador group

      - Other

  

- * Have you considered becoming a member of the FESCo, Mindshare or Council? And why? (comes with the comment field)

+ * Have you considered becoming a member of the FESCo, Mindshare or {team_name}? And why? (comes with the comment field)

      - Yes

      - No

      - I was/am a member now

@@ -2,8 +2,8 @@ 

  

  = Fedora Team Directory

  

- In order to provide visibility into what teams exist _and are active_ in Fedora, the Council link:{COMMBLOG}/fedora-council-november-2019-meeting-more-miscellaneous-stuff[decided] to maintain a directory that receives regular checks.

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

+ In order to provide visibility into what teams exist _and are active_ in Fedora, the {team_name} link:{COMMBLOG}/fedora-council-november-2019-meeting-more-miscellaneous-stuff[decided] to maintain a directory that receives regular checks.

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

  

  == Intent

@@ -1,16 +1,16 @@ 

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

  

- = Council ticket queue

+ = {team_name} ticket queue

  

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

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

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

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

  

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

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

  

  == Issue priorities

  

- Currently, the Council uses the following priorities for tickets:

+ Currently, the {team_name} uses the following priorities for tickets:

  

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

  * **Needs Review** (default): The ticket needs to be triaged.
@@ -20,7 +20,7 @@ 

  

  == Issue tags

  

- The Council uses tags to indicate the topic of issues.

+ The {team_name} uses tags to indicate the topic of issues.

  Mutliple tags should be applied when appropriate.

  

  * **budget**: Big-picture budget issues
@@ -33,14 +33,14 @@ 

  * **objectives**

  * **policies**

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

- * **ticket-vote**: Indicates an issue that should be voted on by Council members

+ * **ticket-vote**: Indicates an issue that should be voted on by {team_name} members

  * **trademarks**

  

  == Voting

  

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

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

- Council members can provide additional context explaining their vote, but should still indicate explicitly which of +1, 0, or -1 applies.

+ {team_name} members can provide additional context explaining their vote, but should still indicate explicitly which of +1, 0, or -1 applies.

  

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

@@ -1,6 +1,6 @@ 

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

  

- = Welcome to Council

+ = Welcome to {team_name}

  

  Welcome to the {team_name}!

  You have just joined
@@ -13,18 +13,18 @@ 

  == General expectations

  

  *Be brave.*

- You are on the Council because you represent the Fedora community.

+ You are on the {team_name} because you represent the Fedora community.

  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.

- Let the rest of the Council know when you need help.

+ Let the rest of the {team_name} know when you need help.

  Share what's going well.

- Communicate Council goings on back to the group you represent.

+ Communicate {team_name} goings on back to the group you represent.

  

  *Take action.*

- The Council is an active leadership body,

- which means Council members should feel empowered to _do_ things,

+ The {team_name} is an active leadership body,

+ which means {team_name} members should feel empowered to _do_ things,

  not just _discuss_ things.

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

  If there's something that needs to be done,
@@ -43,14 +43,14 @@ 

  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.

- If there's something Council-related that you don't have access to,

+ If there's something {team_name}-related that you don't have access to,

  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,

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

+ so we expect—and welcome—input from community members who are not on {team_name}.

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

  we have a private mailing list.

  
@@ -60,7 +60,7 @@ 

  

  == Meetings

  

- The Council holds bi-weekly business meetings.

+ The {team_name} holds bi-weekly business meetings.

  These are an opportunity to check on the progress of tasks

  and have conversations about open issues.

  Attendance is not mandatory,
@@ -73,14 +73,14 @@ 

  Once a month,

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

  These are an opportunity to let the community showcase their work

- and ask the Council and broader community for help.

+ and ask the {team_name} and broader community for help.

  Video meetings are open to the community at large.

  

  From time to time,

- the Council holds face-to-face meetings.

+ the {team_name} holds face-to-face meetings.

  These are private and in-person when possible.

  Attendance at these meetings is strongly encouraged.

- The Council will pay travel expenses when necessary.

+ The {team_name} will pay travel expenses when necessary.

  

  == Tickets

  

This commit changes almost every occurrence of "Council" and "Fedora
Council" with {team_name}, an Antora macro that resolves to "Fedora
Council". This continues the integration work with the team profile
introduced in previous commits. It ensures consistent use of the Fedora
Council name in our documents and may also contribute to a slight boost
in search engine optimization.

Metadata Update from @jflory7:
- Pull-request tagged with: type - existing docs
- Request assigned

9 months ago

Pull-Request has been merged by jflory7

9 months ago