"CommOps 2.0" is an emerging, potential Community Initiative focused on rebooting the Community Operations (CommOps) team.

Community Ops was born in Fedora in 2015. A lot changed in Fedora since then, and so has Community Ops. The goal of this effort is to rebuild the team with a focus on rising to the challenges that Fedora faces now in the 2020s.

Purpose

Vision

The Fedora Community Operations Team enables a highly-collaborative Fedora community ecosystem, where contributors thrive in achieving objectives of the Fedora 2028 strategy and friction in the contribution process can be identified and addressed for Fedora contributors.

Mission

The Fedora Community Operations Team achieves a highly-collaborative Fedora community ecosystem through two key areas: process improvement, to partner with others in making the contribution process more open and transparent, and community social analysis, to better understand contribution pathways without prescribing a specific journey.

Objective Leads

Co-Lead: Justin W. Flory
Co-Lead: Robert Wright
Executive Sponsor: TBD

Time-frame

Targeted completion within one month after Flock 2024 (i.e. September 2024).

The success of this Initiative may or may not spur on a new follow-on Initiative after the completion of this Initiative.

Logic Model

Last updated on 12 January 2024

Expanded (full text)

Inputs

Past and current Community Operations members
Fedora Join SIG members
Fedora Marketing Team
Fedora Infrastructure
Ambassadors and Advocates, both historical and aspirational
Matthew Miller (via velociraptorizer and brontosaurusifier)

Activities

Process Improvement:
- Write a new SOP about how to run virtual Fedora events.
- Review existing, documented best practices about contributing to Fedora. Propose improvements, where applicable. Unify existing content into a single resource to be used consistently across teams.
- Write 2-3 case study Community Blog posts about how a team collaborates in Fedora (e.g. Fedora Design workflow in GitLab, DEI Team workflow for meetings, etc.).
- Kickstart surveys as a function/capability of Community Ops.
- Execute the data governance framework created by the Community Social Analysis team, with a focus on asking questions that do not collect personally identifiable information.
- Documenting the process involved in creating a community-wide survey.
- Plan, execute, and promote the 2024 annual contributor survey.
- Run a newcomer onboarding clinic as a dedicated day and time where new contributors can come and ask for help on getting started in Fedora.
- Run planning calls for the Fedora Linux 40 and 41 Release Parties, starting two months before each event.
- Organize volunteer teams for the Release Party:
  - Graphic design & visual art
  - Event programming (e.g. content and scheduling)
  - Event infrastructure (e.g. Hopin, possibly Matrix/Jitsi)
  - Marketing & outreach
  - Media partner management
  - Project management (e.g. writing meeting agendas, sending reminders, doing follow-up tasks and emails, opening tickets, etc.)
  - Event support staff (e.g. moderators, Q&A wranglers, hype people)
- Create a LimeSurvey survey and interview a small group of contributors who both went through the Join SIG process or support as mentors. Collect feedback on strengths and weaknesses of existing processes.
- Invite five or more experienced Fedora contributors to help out in the Join SIG channel (either for fixed or indefinite terms).
- Implement and test 2-3 improvements to the Join SIG process, based on feedback surfaced from interviews.
- Create a template for Community Blog monthly reports on this month’s new contributors from the Join SIG. Include a place to identify active mentors.
- Publish new contributor reports for at least three months.
- Create a Fedora Badge for a mentor who is mentioned as an active mentor in the monthly reports.
Community Social Analysis:
- Kickstart surveys as a function/capability of Community Ops.
- Provide guidance and define requirements for data governance of Fedora LimeSurvey surveys.
- Analyze and review survey responses. Publish a summarized report, raw data, or both on request of the survey requestor.
- Identify trends and questions that help to better understand community health.
- Create methods/scripts in Python to visualize subsets of data related to team needs / community health.
- Write Community Blog article(s) about findings to a specific question or group of questions (i.e. not a full report).
- Run a data contribution workshop that introduces Fedora tools for data, our data sets, and how to work with them.
- Kickstart analytics as a function/capability of Community Ops.
All:
- Provide periodic updates on Initiative progress to the Fedora Council (e.g. monthly posts or video meeting updates).
- At the end of the Initiative, conduct an Initiative report that shares successes, failures, and recommendations for the next steps.

Outputs

Process Improvement:
- Documentation: Existing documentation about newcomer onboarding is enhanced. New documentation is created about running a virtual Release Party, organizing community-wide surveys, user stories about team workflow, and a template for team onboarding health reports.
- Documentation: Create best practices for launching a new Fedora SIG or Working Group, maintained by the Community Operations team.
- Merge/Pull Requests: Improving READMEs, documentation, and other first contact points for new contributors in the Join SIG.
- Fedora Linux 40 and 41 Release Parties: A team of volunteers works together in executing the next two virtual Release Parties for a Fedora release.
- 5+ active contributors from three time zone regions in Join SIG: Five or more contributors across three major time zone regions participate in Fedora Join SIG channels. Monitored channels include Fedora Discussion and Fedora Chat.
- Contributor recognition: A Community Blog series with a corresponding Fedora Badges series that recognizes contributors who participate in onboarding newcomers.
Community Social Analysis:
- A data dictionary for Fedora.
- A hub for published datasets, visualizations, and data tools (e.g. Fedora People to start, something else later).
- A managed data infrastructure that can be supported long-term by Fedora Infra using tools and FOSS software (e.g. Python, Fedora Linux, containers).
- Select and implement a dashboard solution that extends the managed data infrastructure.
- Create a community health report to be shared by the Fedora Project Leader in the State of Fedora keynote at Flock 2024.

Outcomes

Process Improvement (phase 1 — onboarding):
- Anyone can discover accepted best practices for creating a new team effort in Fedora.
- Fedora Release Parties are celebrated virtual events that are organized by the community, for the community.
- The Fedora Join SIG is enhanced with improved documentation, new mentors, and an improved onboarding process based on real feedback from Fedora community members.
- Contributors who are mentors receive greater recognition and appreciation for their mentoring efforts.
Community Social Analysis:
- There is a standard approach for working on data work in the Fedora community.
- More data-driven indications are available to indicate whether Fedora is on track to meet the 2028 Strategy.
- Community members have a forum to share ideas and requests for data analysis on a team or a component of Fedora.
- An exhaustive data source for contributors to start from.
- Gather data based on an agreed-upon standard of privacy that fits between the rights of users and the needs of the Fedora Project.
- Both Community Operations sub-teams are integrated (i.e. process improvement and community social analysis are linked).

Impact

Fedora 2028 Strategy objectives:
- We have insight into community health and trends through meaningful metrics.
- More (active) SIGs, fewer images. (or, SIGs have useful, real work)

Search

Initiatives/Community Ops 2024 Reboot

Contents