Section: Role Handbooks

# Section: Role Handbooks ## Role: CommOps Team Member ### How to become a CommOps Team Member: Move -> https://docs.fedoraproject.org/en-US/commops/contribute/join/ to this section. Please simplify headers so that it does not take up as much space. ### Responsibilities Community Operations (CommOps) team members provide tools, resources, and utilities for different sub-projects of Fedora to improve effective communication. - Work closely with Fedora Community Action and Impact Coordinator to prioritize key focus areas - Work closely with the Mindshare Committee to actualize initiatives - Assist Fedora Program Manager with release preparations - Support preparation and execution of Fedora Elections - Work with sub-projects and teams to improve on-boarding methods and practices - Use metrics and data to improve understanding of Fedora community - Support development of metrics tooling ### Teams you will be closely working with - Mindshare Committee - Fedora Design & Badges - Fedora Council - Community Outreach teams (Ambassadors, Join SIG, ) ### Current members The FAS group currently holds the list of people who are currently https://accounts.fedoraproject.org/group/commops/ ### Contact information Discourse forum https://discussion.fedoraproject.org/c/project/commops IRC channel #fedora-commops on Libera.Chat Telegram group @fedoracommops on Telegram Matrix/Element https://matrix.to/#/#fedora-commops:matrix.org ### How to retire from CommOps Life happens, things get busy, and interests change. This is a natural part of life that we embrace in the Fedora community. Whether you are moving to a new team in Fedora or taking a break altogether, it is important to have an avenue to retire. CommOps Team memmbers looking to retire should [open a thread on the CommOps Discourse](https://discussion.fedoraproject.org/c/project/commops) forum with a retirement message- it doesn't have to be long (or it can be!) to let your teammates know you will be retiring or taking a break. This gives everyone a chance to thank you for all your efforts in CommOps! The CommOps Team will also run a yearly group cleanup. This entails running a script to search for inactive users(Fedora Account System) and reaching out to them directly via their Fedora Project email. It is absolutely fine to respond to this as "I want to stay involved" or "I will be back soon" or "I am unable to be a part at this time". ## Role: CommOps & Ambassador Reps to Mindshare There are two representatives from the CommOps structure to Mindshare. Ideally, this would be one Ambassador representative and one representative from CommOps. These people are responsible for representing Ambassadors/CommOps as a collective to the Mindshare Committee and not as a single voice. They will be required to work with all the various groups that collaborate with Mindshare and act as a liaison between these groups and CommOps. These roles will require a fair amount of time investment and good communication skills. #### Current representatives - Nick Bebout (nb) \[Ambassador Rep\] - Alberto Rodríguez Sánchez (bt0dotninja) \[CommOps Rep\] #### Responsibilities Representatives are a crucial point to keep communication flowing between CommOps, Ambassadors, and Mindshare. As a CommOps/Ambassador representative to Mindshare you will be involved with: - Participate in weekly meetings at fedora-mindshare IRC channel. - Review and comment on tickets in the fedora-mindshare Pagure repo. - Work closely and collaborate with the other outreach teams’ representatives to ensure that the most effective decisions are made. - Give valuable feedback to the Mindshare Committee. - Share the best practices: one of the Mindshare’s goals is to take down barriers or whatever is blocking sharing best practices. - Ensure that CommOps/Ambassadors are being represented and bring to the Mindshare meetings any problems or obstacles they might encounter. - Ensure that the Fedora budget is managed in the most effective way across all regions. - Listen to the needs, concerns and hopes of the Fedora community and relay them to the Mindshare Committee. #### Duration of Service The duration of service is two Fedora release cycles, or one year. However, terms may run shorter or longer depending on the personal situation of the persons filling the Representative roles. In an unlikely event of the representative(s), Mindshare Committee, or the CommOps Team wish to make a change in representation, sufficient reasoning must be provided. Following the SOP, a new representative will then be selected by the CommOps Team. #### Selection This section explains how the representatives are nominated and selected. The selection process documented below is initiated when a rotation of representatives is motioned by the existing representative, the Mindshare committee, or the Fedora Council. #### Nomination There will be a two-week nomination period for potential representatives. Nominees can be self-nominated or nominated by other members of CommOps/Ambassadors with their consent. Nominees are required to be members of CommOps/Ambassadors and should have a basic understanding of various Fedora sub-projects, and have sufficient time to perform the responsibilities required. In the event that there are no nominees, Commops/Ambassadors will work with the Mindshare Committee to broaden the search message and request more time. Should no nominees be found after that, the role will rotate among existing CommOps/Ambassador members until the next representative is identified. #### Confirmation After the one-week nomination period expires, the CommOps teams (including Ambassadors) will discuss candidates in a public meeting. In a meeting discussion, it provides an opportunity for the team to weigh in and share other context. In the event that three or more nominees are interested in the Representative roles, the Fedora CommOps Team will coordinate with the [Fedora Program Manager](https://docs.fedoraproject.org/en-US/council/fpgm/) to run an election. For the Fedora Elections application, use these conditions: - Nominee must be a member of fedora-commops Fedora Account group - Voting is open to CLA+1 voters (like Council elections) The selected person and the Mindshare Committee will be notified once the selection is confirmed. The selected person will begin serving as the CommOps/Ambassador representative to the Mindshare Committee as soon as possible. #### Teams you will be closely working with - Fedora Mindshare - CommOps - Ambassadors - Various other Outreach teams as required ---- ## Role: Ambassador Team Member A Fedora Ambassador is a representative of the Fedora Project. Ambassadors ensure the public understand Fedora Project's principles and the community's work. Additionally, Ambassadors are responsible for helping to grow the contributor base and to act as a liaison between other FLOSS projects and the Fedora community. You can still represent Fedora in public without being an Ambassador. In this case, you are a Fedora Advocate. (link to Advocates' docs) * You give a face and a name to Fedora. You are a person, friendly and approachable. Fedora can be big and scary, but you will help make sure that one person finds their way through all the confusion into the place where they can contribute. * You are the glue. You help connect different people in different parts of the Project because you are constantly dealing with people whose interests are diverse. You should be eager and happy to work with other parts of Fedora to solve problems. * People are the key. Everything that we do – events, budgets, swag, membership verifications, blogging – it's all done as an attempt to make personal connections with folks who either want to use or contribute to Fedora. Places where Ambassadors get together are one of the few times that Fedora contributors have an opportunity to meet face to face (other than FUDCons and FADs). * You are the expert in your region. You understand the culture, the needs, and the best ways to communicate about Fedora and FOSS in your region. FAmSCo and other "leaders" in Fedora work for you and need to listen to what you are saying makes sense. We can't ignore the global picture, but we need to be flexible in adapting to local needs. ### How to move to Ambassador Emeritus Write a post on the Ambassador Discourse topic and let the team know that you are ready to step down as an Ambassador and move to the Ambassador Emeritus group. If you have set tasks/responsibilities related to Ambassadors, ensure that you have a successor in place. ### How does someone come back? Write a post on the Ambassador discourse to express your interest in returning. Join the next Monthly Ambassador call and raise your discourse thread. If you took a short break, and there are no objections, you can expect to be added back to the Ambassador group shortly. If you took a longer break, we suggest finding a mentor and getting a short refresher before returning. Ambassador Rep to Mindshare, the FCAIC, and representatives from FAMSCo will look at the request and make final approval. ### Ambassador Conduct The Fedora Code of Conduct applies to everyone in the Fedora community, and especially to you as a Fedora Ambassador. When acting as an ambassador, you don't just represent yourself; you represent the Fedora Project. When people think of you, they will think of the Fedora Project. This means that there are some important rules to follow, and giving the right impression is important to set aside personal biases in favour of goodwill for yourself and Fedora. #### Know your message As an ambassador and as part of the Marketing project, you need to know the good word of Fedora and know the differences between it and its cousin, Red Hat Enterprise Linux. Make sure to focus on the strengths of Fedora, do not insult any other project or product. #### No monetary requests Remember, you are not allowed to publish any monetary details or funding requests on fedoraproject.org. You are not authorized to collect funds on behalf of the Fedora Project or any Fedora-related venture. #### Respect the Trademark Guidelines Always be aware of the Trademark Guidelines for the Fedora trademarks. They protect the Fedora brand. You should also respect the logo guidelines. As an ambassador, you should be especially careful not to violate these guidelines. #### No illegal software You should not direct people to software that may violate the law. Review and understand our Forbidden items. You can direct users to third-party software but do not lead users to software that may violate the law or copyrights. When you direct someone to third-party software, please make it clear that use of the software is not supported or encouraged by the Fedora Project. #### You represent Fedora, not Red Hat This is pretty simple. You represent the Fedora Project, which is sponsored by Red Hat. You do not represent Red Hat. If someone is interested in Red Hat specific details or Red Hat Enterprise Linux, please put them in touch with the Fedora Project Leader. Even though you may believe that Fedora is perfection, you should not insult any other project or product. #### Dress to represent The Fedora brand is independent and stand-alone, and it's important to Fedora's marketing efforts that we maintain that distinction. When representing Fedora in person, try not to confuse people by wearing Red Hat, or any other distribution, clothing or apparel. Our founding organization and main sponsor, Red Hat, has specifically requested that we not connect hats, red in colour or otherwise, to the Fedora Project. Please do not use a hat, whether it's a fedora or any other type of hat, in any presentation of Fedora or to represent the Fedora Project in any way. #### Online presence As an Ambassador, you represent the Fedora Project, which may include virtual spaces. In any virtual space, you represent yourself as a Fedora representative, you need to adhere to Fedora's Code of Conduct. #### Ask for help if you get lost Inevitably, things happen, and they aren't always great. If you need help or something goes wrong, make sure to reach out to any local event coordinators or group leads, and also communicate the situation to the Fedora Community Action and Impact Coordinator. ### Responsibilities The main responsibility of Ambassadors is to ensure the Fedora updates are being broadcasted to the public and collect feedback from users and contributors. Ambassadors should share their feedback at the Mindshare Committee through their representative at the Mindshare Committee. * Organize Fedora's participation at events (sessions, info booths, hand out swag, etc). * Onboard new contributors and users. * Organize release parties and install fests. * Talk about the Fedora Four Foundations. * Regularly check up on other Ambassadors to ensure others are doing good and provide assistance. * Promote FLOSS and open source projects. * Demonstrate Fedora and other open source projects to the public. * Promote Fedora at local user groups with talks etc. * Teams you will be closely working with ### Ambassadors work closely with: * the Mindshare Committee * the Join SIG * the Marketing team * CommOps * Advocates ### Contact information * Discourse forum: TBD * IRC channel: #fedora-ambassadors on Libera.Chat * Matrix/Element: https://matrix.to/#/#fedora-ambassadors:fedora.im _____ ## Role: Ambassador Emeritus Member Life happens, things get busy, and interests change. This is a natural part of life that we embrace in the Fedora community. Whether you are moving to a new team in Fedora or taking a break altogether, it is important to have an avenue to retire. Ambassador team members looking to retire should [send an email to the Ambassador Mailing List](https://lists.fedoraproject.org/admin/lists/ambassadors.lists.fedoraproject.org/) with a retirement message- it doesn't have to be long (or it can be!) to let your teammates know you will be retiring or taking a break. This gives everyone a chance to thank you for all your efforts in the Ambassador Program! The CommOps Team will also run a yearly group cleanup. This entails running a script to search for inactive users(Fedora Account System) and reaching out to them directly via their Fedora Project email. It is absolutely fine to respond to this as "I want to stay involved" or "I will be back soon" or "I am unable to be a part at this time". ### How does someone come back? Just like the first time you joined Fedora, you are always welcomed to come back and join. Same as the first time you joined the Ambassadors group, you should create a ticket at the Ambassadors repo in order to express your interest to come back, give a brief explanation of the reason that made you retire (no personal details are required!) and share some ideas about how you can help the community. If you have been away for a long time and you would like some "Fedora orientation", don't forget to mention that as well. In the meantime, you can check what the rest of the community is up to by reading the Mailing Lists' archives, checking Fedora social media accounts, check Fedora Discussion, have a look at the Fedora repos in order to see what the community is currently working on. Don't hesitate to participate in all the above by providing your assistance when help is needed or by simply joining that discussion. --- ## Role: Fedora Advocate ### Overview Advocates are passionate contributors who want to participate in community events, represent Fedora and help grow the user and contributor community. Advocates are people who love spreading knowledge about their area of interest in Fedora. Many advocates also organize release parties where they share information about What’s new in Fedora. Advocates also help new contributors join and hack on any of the subprojects at meetups and Fedora Activity Days (FADs). Advocates come from all parts of the project and represent contributors from all areas, technical and non-technical. * Organize Fedora participation at events * Foster Fedora contributors and encourage contribution and usage * Promote Fedora and cross-community interaction * Hold calendar events like release parties * Promote Fedora technology at local user groups with talks etc. The complete documentation for Fedora Advocates is located in the Mindshare Docs page. ### Contact information - Mindshare mailing list - Mindshare Libera/Element chat ### Information Sheet ### How does someone come back? --- ## Role: Fedora Join SIG Team Member Link to: https://docs.fedoraproject.org/en-US/fedora-join/#_membership --- ## Role: Fedora Marketing Team Member The Fedora Marketing Team develops and executes marketing strategies to promote the usage and support of Fedora worldwide. Through the development of processes and content, this project aims to support the efforts of other Fedora projects to spread Fedora and to provide a central source of ideas and information that can be used to deliver Fedora to new audiences. The marketing Team works closely with the Join SIG and Fedora Ambassadors who spread the word about Fedora at events and allow the Fedora Project to interact directly with its existing and prospective users. ### How to join the team/ step down Join the mailing list and introduce yourself. This helps us to know who wants to contribute, and gives us the opportunity to know each person's strengths and learn how we can coordinate with you. When you join the list, you'll get an email that tells you other useful information about the list. Register in the Fedora Account System , and complete the FPCA. This establishes your account as an official Fedora contributor and is used to grant various kinds of access to Fedora features, including edit rights on this wiki. The FPCA makes sure your contributions always remain free in the spirit of Fedora. Join the 'marketing' group in the Account System. Do this after you have introduced yourself . Your membership will be approved after making a series of contributions to the Marketing team. We approve memberships regularly based on concrete and sustained contributions to Fedora's marketing efforts. ### Responsibilities - Help spread news on all major development updates, releases, new projects and events related to Fedora. - Consider picking one or two stories and contacting appropriate press outlets about it. - Solicit Linux User Groups members to use and contribute to Fedora. - Dispel common myths and educate the public about Fedora. - Educate yourself on what marketing is, and apply marketing strategies in the promotion of Fedora. ### Teams you will be closely working with --- ## Role: Ambassador Mentor ### How to join the team/ step down ### Responsibilities ### Teams you will be closely working with ### Current members ### Contact information ### Information Sheet ### How does someone come back? --- ## Role: IRC / Libera Chat Group Contacts libera.chat IRC network has a concept of 'Groups' for various projects. Group contacts for each of those groups are granted special powers on the network over their groups channels. Additionally, requests from Group contacts can be taken as 'official' requests from the group. Fedora group contacts represent Fedora to libera.chat. The primary functions of group contacts are: 1. Check/process 'cloak' requests and request them from libera.chat admins to process. (Cloaks are a hostmask with the project name in them instead of hostname or ip address. It's a way to note your affiliation with a group) 2. To (re)gain and configure control of irc channels in the group namespace "#fedora*" ### How to join the team / step down Group contacts are added from very trusted project members and kept to a small number. Council should appove changes in libera.chat group members. Changes will then be made by libera admins to joining / leaving accounts. ### Responsabilities 1. Process the 'cloaks' requests: https://fedoraproject.org/wiki/LiberaCloaks as time permits. 2. Process requests in the https://pagure.io/irc tracker for matrix bridges or regaining control of a channel in the #fedora* namespace as requested. 3. idle in the #libera-communities channel to make requests to libera admins as needed. ### Teams you will be working closely with libera.chat admins in #libera.communities Any fedora groups needing irc work ### Current members * Tom Calloway / spot * Nick Bebout / nb * Kevin Fenzi / nirik ### Contact information https://pagure.io/irc

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.