include::ROOT:partial$attributes.adoc[] = {team_name} :page-aliases: contribute/commops-landing.adoc, teams:commops.adoc, teams:commops-role.adoc // #TODO Create a new page to document the CommOps brand assets. // This does not exist yet. // The link below is where the source SVGs currently live as of 2025-02-03. // When the page is created, this comment and the URL can be removed from the index page. // https://gitlab.com/fedora/commops/home/-/blob/main/docs/modules/ROOT/assets/images/team-logos/community-ops/ image::team-logos/community-ops/commops.png[Fedora Community Ops team logo.] {team_summary} // NOTE: This variables are defined in ROOT/partials/attributes.adoc [[profile]] == Team profile [cols=2] |=== |*Team URL* |{team_url} |*Team status* |{team_status} |*Forum* |link:{team_synch_communication}[{team_synch_communication_name}] |*Chat* |link:{team_asynch_communication}[{team_asynch_communication_name}] |*Issue tracker* |link:{team_issue_tracker}[{team_issue_tracker_name}] |*Meeting schedule* |link:{team_meetings}[{team_meetings_name}] |*Meeting agenda* (A/V meetings) |link:{team_meetings_agenda_url}[{team_meetings_agenda_name}] |*Meeting minutes* (Matrix meetings) |link:{team_meetings_minutes_url}[{team_meetings_minutes_name}] |=== [[vision]] == Vision To foster a transparent, inclusive, and data-informed Fedora community that empowers collaboration, celebrates diversity, and continuously evolves. We envision a community where contributors, teams, and leaders have the insight, tools, and support needed to sustain a thriving open source ecosystem. [[mission]] == Mission The {team_name} (CommOps) strengthens the Fedora Project by connecting people, data, and process to create a more resilient, informed, and cohesive community. Community Operations supports the lifecycle of community collaboration by supporting contributors and sustaining teams through data-driven insights, clear communication, and process excellence. [[focus-areas]] == Focus Areas * *Community Activities*: Supporting teams and community projects & initiatives that build contributor engagement and community growth. * *Moderation & Community Collaboration*: Partnering with moderation working groups to support a safe, respectful, and inclusive community culture. * *Data & Analytics*: Building and maintaining ethical, privacy-conscious analytics that provide visibility into community health, participation, and trends. * *Events & Outreach*: Collaborating with event organizers and outreach teams to enhance community experiences, from global conferences and local meetups. * *Process Improvement & Incubation*: Experimenting with and incubating new methods, tools, and workflows that improve how Fedora collaborates, communicates, and evolves. [[goals]] == Goals & objectives The following are examples of where the {team_name} focuses: * Work closely with xref:council::fca.adoc[Fedora Community Architect] to prioritize key focus areas * Assist xref:council::foa.adoc[Fedora Operations Architect] with release preparations * Support preparation and execution of link:{url_wiki}/Elections[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 [[contact]] == Get in touch with us The {team_name} uses a {team_asynch_communication}[{team_asynch_communication_name}] forum tag and a {team_synch_communication}[{team_synch_communication_name}] room to communicate. The {team_asynch_communication}[{team_asynch_communication_name} forum tag] 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_synch_communication_name} room is best for _synchronous_ communication. This means it is best for quick feedback, like in a conversation. It is helpful for real-time discussions or getting someone's attention. {team_asynch_communication_name} forum tag:: {team_asynch_communication}[{team_asynch_communication}] {team_synch_communication_name} room:: link:{team_synch_communication}[`#commops:fedoraproject.org`] [[workflow]] == Workflow The {team_name} uses a ticket-based workflow to keep track of our work. The repository with tickets is found on link:{team_issue_tracker}[{team_issue_tracker_name}]. Tickets are found under the link:{team_issue_tracker}/-/issues[_Issues_] tab in the sidebar. Various labels are used to sort and triage GitLab Issues. For good beginner tasks, look at the link:{team_issue_tracker}/-/issues/++?label_name[]=good%20first%20issue++[_good first issue_] tag. [[meetings]] == Meetings The {team_name} holds meetings every other week to check in on tasks and plan ahead. This translates to two meetings a month. One of the meetings is run via a text chat in a Matrix room. The other meeting is run as an audio/video call. Check link:{team_meetings}[{team_meetings_name}] for the next meeting date and time. Past text meeting minutes are recorded in link:{team_meetings_minutes_url}[{team_meetings_minutes_name}]. [[meeting-format]] === Meeting format The upcoming meeting agenda is found on link:{team_meetings_agenda_url}[{team_meetings_agenda_name}]. Meetings follow an agenda split into six parts: . *Intros, welcomes, hellos*: Appx. 5 minutes. Waiting for others to arrive, opportunity to introduce yourself, and ask general questions. . *Team announcements & news*: Appx. 5-10 minutes. Any Fedora news or updates to share with the wider team. . *Initiative Co-leads updates to the team*: Appx. 5-10 minutes. Fedora Council updates from the Initiative Co-leads, if there are any. . *Follow-ups from last meeting (if any)*: Appx. 5-10 minutes. Follow up on pending action items from the previous meeting. . *Ticket discussions*: Use the remaining meeting time. Discussion and follow-up on tickets link:{team_issue_tracker}/-/issues/++?label_name[]=meeting%20topic%20request++[marked for meetings]. . *Open floor*: Final 5-10 minutes of the meeting. General discussion or comments, or time to discuss anything that had to be revisited during the meeting. [[join]] == Get involved Read our guide on xref:join.adoc[how to join the {team_name}]. The team always welcomes new contributors. Whether you are a newcomer or an old-timer, there are ways to get involved. Join our team to do some or all of the following: * Build your portfolio in open source community management * Directly see the impact of your contributions over time * Gain a holistic view of the Fedora Project and learn how the pieces fit together * Work directly with Fedora Project leadership * Work with teammates from around the world * Aspire to the greatness of a community superhero .Join the {team_name} today! [#img-panda,caption="",link="join/"] image::https://fedoraproject.org/w/uploads/7/72/Happypanda.png[Happy Panda,100]