#14 Redefine our "official" definition and purpose
Closed: Fixed None Opened 5 years ago by jflory7.

Looking at our [https://fedoraproject.org/wiki/CommOps wiki page], I think some of the wording about what CommOps does is unclear and ambiguous. My guess is that some of this wording is likely left over from when the team was in the propositional phases.

However, I think know that the "ball is rolling", we should focus on more clearly defining '''what we do''' and '''how we do it'''. This will make it easier for other members of the Project to understand how CommOps fits into the Project and perhaps make it easier for them to identify how they may be able to help.

I mostly refer to [https://i.j-f.co/u/4d2f712405266a01d0b48969972b56b7.png this section].

I am marking this ticket as critical priority because I believe that we are getting more eyes turned towards what we're doing, so it is more important than ever to have a clear and to the point definition of our work.

Does anyone else have any ideas / rewordings / bullet points about clearly defining what it is that we work on and the areas we're focusing at improving? I plan to offer my own ideas soon, closer to the meeting.


Discussed in 2015-12-08 meeting.

We agreed that more specific rewording was a good idea now that we have some concrete things to point to. A rough idea of things to bullet-point-describe "what we do" is…
- Electioneering
- Assisting Fedora Release Manager with prepping for releases
- Running Community Blog (and how to write for it)

This ticket should be shared with the list to get more opinions and input.

Discussed in 2015-12-15 meeting.

Getting a Badges Onboarding Series' ready for different teams in Fedora Project is a high priority task for 2016. So, I think,we should be add something on the lines of
"Assisting with New Contributor Onboarding"

Also, I believe "Metrics" is another CommOps contribution area (though not exclusive).

Replying to [comment:2 bee2502]:

Getting a Badges Onboarding Series' ready for different teams in Fedora Project is a high priority task for 2016. So, I think,we should be add something on the lines of
"Assisting with New Contributor Onboarding"
I definitely think this is something we can add to the wiki article, especially after what we hit on today. I think it's in there now, but it could definitely be expanded upon a good bit now. :)

Also, I believe "Metrics" is another CommOps contribution area (though not exclusive).
Also agreed. I think it might be helpful to link to some examples of the posts you've written already for the CommBlog, like the IRC meeting metrics article as an example of some of the metrics things CommOps helps with.

I'm planning on sharing a rewrite of sorts with the mailing list this week as well, I'm hoping we can have the article updated by week's end. :)

Replying to [comment:3 jflory7]:

Replying to [comment:2 bee2502]:

Getting a Badges Onboarding Series' ready for different teams in Fedora Project is a high priority task for 2016. So, I think,we should be add something on the lines of
"Assisting with New Contributor Onboarding"
I definitely think this is something we can add to the wiki article, especially after what we hit on today. I think it's in there now, but it could definitely be expanded upon a good bit now. :)

Also, I believe "Metrics" is another CommOps contribution area (though not exclusive).
Also agreed. I think it might be helpful to link to some examples of the posts you've written already for the CommBlog, like the IRC meeting metrics article as an example of some of the metrics things CommOps helps with.

I think CommBlog metrics are more oriented towards understanding Fedora Project Community as a whole - rather than being a specific package oriented stats. The IRC meeting metrics, post Election Metrics as well as metrics for Badges and Comm Ops Year in Review post are aligned with similar goals.

IRC meeting article : https://communityblog.fedoraproject.org/meetbot-data-analytics-peek-fedora-irc-meetings/

I'm planning on sharing a rewrite of sorts with the mailing list this week as well, I'm hoping we can have the article updated by week's end. :)

Replying to [comment:4 bee2502]:

I think CommBlog metrics are more oriented towards understanding Fedora Project Community as a whole - rather than being a specific package oriented stats. The IRC meeting metrics, post Election Metrics as well as metrics for Badges and Comm Ops Year in Review post are aligned with similar goals.

IRC meeting article : https://communityblog.fedoraproject.org/meetbot-data-analytics-peek-fedora-irc-meetings/

I see, that makes sense. I will make note of this for sure. I'm putting together a rewrite now, and will share here on the ticket and with the mailing list soon!

I finished a preliminary draft of the changed wording in the first part of the CommOps wiki article to make it easier to identify "what it is we do" at a glance.

I'm copying the syntax directly from the wiki, so formatting may be strange on Trac. [https://i.j-f.co/u/fb9ae8bec8da5e4de84c6b53bc476f70.png This is what it should look like.]

= rewritten overview, rev. 1 =
The rise of DevOps has been swift. Sysadmins are increasingly instrumenting and integrating automated systems to stand up and maintain their infrastructure. This same approach can be taken to support community infrastructure in a distributed and automated fashion, that doesn't force people to choose between using their precious volunteer time to "build things" or "build communities that build things."

Community Operations, a.k.a. ''CommOps'', aims to address the area of community infrastructure by providing the tools, resources, and utilities for the different subgroups of Fedora to increase communication across the Project. We accomplish this by focusing on the following areas.

  • [[Community Blog]]
    ** The [[Community Blog | CommBlog]] helps improve communication about "what's happening" in the four corners of the Project. Fedora is huge and there are awesome things and tasks being worked on every day - the CommBlog intends to be a central location for finding '''contributor-oriented''' news.
  • Assisting Fedora Release Manager with preparing for releases
    ** Every new release of Fedora, there are tasks that need to be completed to ensure that everyone is on the same page and that each release happens smoothly. CommOps helps support the Release Manager by providing tools and resources to improving collaboration and communication project-wide.
  • Helping provide support and information to the Elections process
    ** During Elections cycles, CommOps helps provide metrics for Elections, provide a platform for candidates to publish interviews, and brings greater exposure to the entire process, from nominations to campaigning to voting to results.
  • Assisting subgroups and teams with improving on-boarding methods and practices
    ** A long-term goal of CommOps is to assist the various subgroups and teams of Fedora with tools and resources (e.g. Badges) to help make it easier to get new contributors involved. Part of this process involves identifying milestones where new contributors can get a footing.
  • Collecting and using metrics to direct and provide support where needed
    ** Using various tools [[CommOps#Toolbox | mentioned in our toolbox]], we help collect and provide metrics to identify key areas in need of assistance in Fedora as well as to help subgroups discover areas of improvement or areas of success in their own work. See [https://communityblog.fedoraproject.org/meetbot-data-analytics-peek-fedora-irc-meetings/ IRC Meeting Analytics] as an example.
  • Various other tasks
    ** CommOps also assists in a wider span of tasks mentioned in the [[CommOps#Things_we_help_with | Things we help with]] section of our wiki page.

End of week. Wiki article has been updated. If any late objections, feel free to reopen this ticket.

Login to comment on this ticket.

Metadata