#286 add navdoc
Merged 7 months ago by sumantrom. Opened 7 months ago by sumantrom.
Unknown source main  into  main

add navdoc
sumantrom • 7 months ago  
@@ -1,271 +1,15 @@

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

+ = CommOps Teams

+ :page-layout: with_menu

  

- = Fedora Community Operations (CommOps)

+ CommOps Teams are focused on helping our community with onboarding , outreach and metrics

  

- image::commops-logo.png[CommOps logo]

+ * https://docs.fedoraproject.org/en-US/commops/teams/ambassadors/[**Ambassadors**]- Ambassadors are people who can organize medium and large events

  

- Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.

- The following areas are examples of where CommOps focuses:

+ * https://docs.fedoraproject.org/en-US/commops/teams/advocate-team-overview/[**Advocates**] - Advocates are people who organize or help organize small events

  

- * Work closely with xref:council::fcaic.adoc[Fedora Community Action and Impact Coordinator] to prioritize key focus areas

- * Assist xref:council::fpgm.adoc[Fedora Program Manager] with release preparations

- * Support preparation and execution of https://fedoraproject.org/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

- * And more (detailed below)

+ * https://docs.fedoraproject.org/en-US/commops/#commops.adoc[**CommOps**] - Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication

  

- image::infographic-2020.png[Infographic with statistics about Fedora Community Operations. Created by Smera Goel.]

+ * https://docs.fedoraproject.org/en-US/commops/#join.adoc[**Join**] - The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors engage with the community

  

+ * https://docs.fedoraproject.org/en-US/commops/#marketing.adoc[**Marketing**] - The Fedora Marketing Team ensures that people in Fedora can consistently explain to everyone what Fedora is, why the project can help them, and how they can help the project.

  

- [[find-commops]]

- == Where to find CommOps

- 

- The CommOps team uses a {DISCOURSE}[Discourse] forum and https://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] channel to communicate.

- 

- The {DISCOURSE}[Discourse forum] 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 CommOps IRC channel on the https://libera.chat/[Libera.chat IRC network] 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.

- Additionally, the CommOps IRC channel is bridged to a Telegram group, if Telegram is more convenient.

- 

- Discourse forum:: {DISCOURSE}[{DISCOURSE}]

- IRC channel:: https://libera.chat/[#fedora-commops] on Libera.chat

- Telegram group:: https://t.me/fedoracommops[@fedoracommops] on Telegram

- 

- First time using IRC?

- Look into https://opensource.com/article/17/5/introducing-riot-IRC[Riot], a free and open source client that connects to various IRC networks.

- Riot also keeps you connected to IRC even when you're not connected to the Internet.

- 

- 

- [[workflow]]

- == Workflow

- 

- CommOps uses a ticket-based workflow to keep track of our work.

- The repository with tickets is found on https://pagure.io/fedora-commops[pagure.io/fedora-commops].

- Tickets are found under the _https://pagure.io/fedora-commops/issues[Issues]_ menu.

- 

- Various tags are listed at the top of the _Issues_ page.

- For good beginner tasks, look at the _https://pagure.io/fedora-commops/issues?status=Open&tags=good+first+issue[good first issue]_ tag.

- 

- 

- [[meetings]]

- == Meetings

- 

- CommOps holds a meeting once a week on IRC to check in on tasks and plan ahead.

- Check the https://apps.fedoraproject.org/calendar/commops/[CommOps calendar] for the current date and time.

- 

- Past meeting minutes are recorded in https://meetbot.fedoraproject.org/teams/commops/[Meetbot].

- 

- 

- [[meeting-format]]

- === Meeting format

- 

- The upcoming meeting agenda is found on the Fedora https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next[Infinote server].

- Meetings follow an agenda split into five parts:

- 

- . **Roll call**: Waiting for others to arrive, opportunity to introduce yourself and ask general questions

- . **Announcements**: Any news or updates to share

- . **Action items from last meeting**: Follow-up on `#action` items from previous meeting

- . **Tickets**: Discussion and follow-up on tickets https://pagure.io/fedora-commops/issues?status=Open&tags=meeting[marked for meetings]

- . **Open floor**: General discussion or comments

- 

- 

- [[what-commops-does]]

- == What CommOps does

- 

- CommOps focuses on a few key areas, both technical and non-technical.

- 

- === Culture

- 

- The Fedora Project builds and ships a Linux distribution, but there is a community behind the technical work and planning.

- In Fedora, we have the xref:project::index.adoc#_what_is_fedora_all_about[Four Foundations] to represent our community culture.

- The Fedora community represents a set of ethics and values to how we build our distribution.

- These ethics and values create the culture of the Fedora Project.

- When working in the community, mindfulness of this culture enriches and supports the different sub-communities inside of Fedora.

- 

- CommOps builds community infrastructure of support and acceptance for the Fedora community's culture.

- The _Friends_ foundation is there for a reason.

- The community infrastructure CommOps assists with builds on top of the _Friends_ foundation.

- People enjoy contributing in a community where they feel valued for who they are and what they bring to the community, not just that they are useful.

- CommOps supports this through some of our tasks relating to culture.

- 

- Examples of things we help with to build and support the culture of the Fedora community:

- 

- * https://pagure.io/fedora-commops/issue/17[Interviewing Fedora community members]

- * https://pagure.io/fedora-commops/issue/110[Fedora Appreciation Week]

- * https://pagure.io/fedora-commops/issue/138[Top Badgers of the Year]

- 

- === Elections

- 

- There are a few elected bodies in Fedora: the xref:project::leadership.adoc[Fedora Council], xref:mindshare::index.adoc[Mindshare Committee], and xref:fesco::index.adoc[FESCo].

- Every new Fedora release, the community holds elections for these bodies.

- Each election takes "wrangling" work to pull it together.

- This includes calling for nominations, conducting interviews with candidates, and raising awareness during the voting window.

- 

- CommOps supports the xref:council::fpgm.adoc[Fedora Program Manager] in organizing and executing elections.

- These responsibilities consist of curating content on the xref:community-blog.adoc[Community Blog], creating interview templates, and outreach to grow awareness.

- 

- Examples of things we do to help organize and execute Fedora elections:

- 

- * https://pagure.io/fedora-commops/issue/7[Fedora Elections and CommOps Coverage]

- * https://pagure.io/fedora-commops/issue/19[Improve automation of Elections communication]

- * https://pagure.io/fedora-commops/issue/93[Better explain roles of Council and FESCo]

- * https://pagure.io/fedora-commops/issue/107[Automated Fedocal reminders to send to all mailing lists for upcoming Elections]

- * https://pagure.io/fedora-commops/issue/112[Create August 2017 election interview templates for candidates]

- 

- === Storytelling

- 

- Messaging and storytelling bring the Fedora Project "story" to both contributors and user communities.

- Every year, a https://mattdm.org/fedora/2018flock/2018-State-of-Fedora.pdf[couple thousand people] work on Fedora.

- Messaging is a way of sharing our story in multiple formats.

- We bring the message of what we _as a community_ are doing out to others.

- Others include our contributors working in other areas of the project and users interested in what the Fedora community produces.

- When we share our story with each other, we are aware of other work happening in the Fedora community.

- Communicating the story of Fedora keeps our contributors moving together towards our goals.

- Good messaging helps our users better understand the goals and objectives of Fedora and how we plan to get there.

- 

- CommOps supports messaging by working with other sub-projects and teams to tell their own stories.

- CommOps provides help to "dig out" the stories and tools to share them widely.

- This includes tasks like interviews, sharing activities by Fedora contributors, running retrospectives, and more.

- These tasks keep contributors in sync with what we're working on.

- They are direct actions to keep everyone on the same page.

- 

- Examples of things we do to support messaging and tell stories:

- 

- * https://pagure.io/fedora-commops/issue/4[Interviews about goals for team sprints]

- * https://pagure.io/fedora-commops/issue/66[Call for nominations of a Working Group]

- * https://pagure.io/fedora-commops/issue/98[Covering upcoming talks by Fedora contributors at a major conference]

- * https://pagure.io/fedora-commops/issue/100["Help Wanted" columns]

- * https://pagure.io/fedora-commops/issue/129[Year in Review blog series]

- 

- === Metrics

- 

- CommOps measures community health and engagement through extensive metrics and data available about Fedora.

- {FEDMSG}[fedmsg] is a messaging bus with data about activity in the Fedora community.

- The data includes activity like git commits, new blog posts, wiki page edits, software build status, IRC meeting notes, and more.

- CommOps works with fedmsg to tell stories about our community, but specific types of stories.

- The stories told with metrics are helpful to understand what we may be doing right or wrong.

- It gives us a data-driven way to understand our huge community.

- 

- CommOps directly supports metrics in Fedora through development time and data-driven storytelling.

- Some members develop existing software or build new scripts to analyze data.

- Others use the data to write reports or studies on how the Fedora community works.

- Ultimately, metrics are a largely technical area that CommOps helps with.

- 

- Examples of metrics work and data-driven storytelling we do:

- 

- * https://pagure.io/fedora-commops/issue/32[Analyzing Fedora contributor activity]

- * https://pagure.io/fedora-commops/issue/88[Fedora release party metrics]

- * https://pagure.io/fedora-commops/issue/109[Understanding contributor activity by geographic location]

- 

- === Supporting sub-projects

- 

- CommOps assists other sub-projects and teams in following best practices and communicating effectively.

- We work with other teams to help them on-board new contributors into their teams.

- This includes creating Fedora Badge requests, reviewing guidelines, and making Fedora services and tools more understandable.

- 

- Examples of sub-project support and on-boarding work:

- 

- * https://pagure.io/fedora-commops/issue/62[Wiki gardening of Fedora Join]

- * https://pagure.io/fedora-commops/issue/69[Fedora Modularity onboarding]

- * https://pagure.io/fedora-commops/issue/76[Update Onboarding Calendar for GSoC 2016]

- * https://pagure.io/fedora-commops/issue/95[Onboarding: DotNet SIG]

- 

- 

- [[join-commops]]

- == Join CommOps

- 

- Read our guide on xref:contribute/join.adoc[how to join the CommOps team].

- 

- CommOps always welcomes new contributors.

- Whether you are a newcomer or an old-timer, there are ways to get involved.

- Join CommOps to:

- 

- * 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 superheroine or superhero

- 

- .Join the CommOps team today

- [link="contribute/join/"]

- image::https://fedoraproject.org/w/uploads/7/72/Happypanda.png[Happy Panda,100]

- 

- 

- [[toolbox]]

- == Toolbox

- 

- The CommOps toolbox explains tools and services often used by the team.

- The tools are organized by purpose and use.

- 

- [[communication-tools]]

- === Communication tools

- 

- These are communication tools to share content and information with others in the Fedora community.

- 

- xref:community-blog.adoc[Community Blog] (CommBlog) - https://communityblog.fedoraproject.org/[communityblog.fedoraproject.org]::

- Centralized blog for contributors to publish news, activities, or calls for help to the rest of the project.

- Useful place for getting an inside scoop on "what's happening" in Fedora.

- 

- https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/fedmsg/irc/templates/ircbot.py?id=0279643#n77[ircbot.py]::

- Python script for fedmsg notifications in https://libera.chat/[#fedora-commops].

- Relays real-time updates and changes relating to CommOps in our IRC channel.

- 

- 

- [[metrics-tools]]

- === Metrics tools

- 

- These tools access and use the Fedora messaging bus, {FEDMSG}[**fedmsg**].

- With these tools, you can generate metrics, analyze data, and interact with fedmsg.

- 

- https://github.com/fedora-infra/fedora-stats-tools/blob/develop/annualgrepper.py[annualgrepper]::

- Gather raw fedmsg totals on https://fedora-fedmsg.readthedocs.io/en/latest/topics.html[topics] in the last year

- 

- https://pagure.io/cardsite[cardsite]::

- Live fedmsg tracker inspired by http://emojitracker.com/[emojitracker]

- 

- https://github.com/fedora-infra/fedora-stats-tools/blob/develop/daily-briefing.py[daily-briefing.py]::

- Template that takes lists of URLs, generates summary reports of daily Meetbot links and action items (manual now, can be automated!)

- 

- https://apps.fedoraproject.org/datagrepper/[datagrepper]::

- The powerhouse tool to interact with fedmsg.

- Using HTTP GET requests, query for historical data from fedmsg.

- Examples include events by username, by package, by message source, and more.

- 

- {FEDMSG}[fedmsg]::

- Python package and API that hooks into various Fedora Infrastructure services.

- Sends messages from each service to a unified message bus in real-time.

- fedmsg drives and powers all the metrics tools we have.

- 

- https://github.com/fedora-infra/fedora-stats-tools[fedora-stats-tools]::

- Multiple statistics tools, data, and slide decks for fedmsg metrics, Year in Reviews, and Fedora event metrics

- 

- https://pagure.io/feedcloud[feedcloud]::

- Takes an RSS feed or list of RSS feeds and generates fancy word-clouds for them

- 

- https://pagure.io/gsoc-stats[gsoc-stats]::

- Python tool to generate statistics about Fedora contributors

- 

- https://github.com/fedora-infra/fedora-stats-tools/blob/develop/longtail-analyze.py[longtail-analyze.py], https://github.com/fedora-infra/fedora-stats-tools/blob/develop/longtail-gather.py[longtail-gather.py]::

- Measure the ratio of activity per user to approximate burnout

- 

- https://github.com/fedora-infra/fedora-stats-tools/blob/develop/meetbot-fedmsg-activity.py[meetbot-fedmsg-activity.py]::

- Jinja2 template that creates links to Meetbot activities

- 

- https://pagure.io/wordcloudbot[wordcloudbot]::

- Create pretty wordclouds from IRC meeting logs

- 

- 

- [[other]]

- === Other

- 

- Other tools that don't belong elsewhere fit under here.

- 

- https://github.com/OSAS/rh-events[OSAS/rh-events]::

- Data for Red Hat conference and talk attendance.

- Useful for plotting events in our own calendar and keeping track of what's happening in the open source community.

@@ -0,0 +1,271 @@

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

+ 

+ = Fedora Community Operations (CommOps)

+ 

+ image::commops-logo.png[CommOps logo]

+ 

+ Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.

+ The following areas are examples of where CommOps focuses:

+ 

+ * Work closely with xref:council::fcaic.adoc[Fedora Community Action and Impact Coordinator] to prioritize key focus areas

+ * Assist xref:council::fpgm.adoc[Fedora Program Manager] with release preparations

+ * Support preparation and execution of https://fedoraproject.org/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

+ * And more (detailed below)

+ 

+ image::infographic-2020.png[Infographic with statistics about Fedora Community Operations. Created by Smera Goel.]

+ 

+ 

+ [[find-commops]]

+ == Where to find CommOps

+ 

+ The CommOps team uses a {DISCOURSE}[Discourse] forum and https://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] channel to communicate.

+ 

+ The {DISCOURSE}[Discourse forum] 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 CommOps IRC channel on the https://libera.chat/[Libera.chat IRC network] 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.

+ Additionally, the CommOps IRC channel is bridged to a Telegram group, if Telegram is more convenient.

+ 

+ Discourse forum:: {DISCOURSE}[{DISCOURSE}]

+ IRC channel:: https://libera.chat/[#fedora-commops] on Libera.chat

+ Telegram group:: https://t.me/fedoracommops[@fedoracommops] on Telegram

+ 

+ First time using IRC?

+ Look into https://opensource.com/article/17/5/introducing-riot-IRC[Riot], a free and open source client that connects to various IRC networks.

+ Riot also keeps you connected to IRC even when you're not connected to the Internet.

+ 

+ 

+ [[workflow]]

+ == Workflow

+ 

+ CommOps uses a ticket-based workflow to keep track of our work.

+ The repository with tickets is found on https://pagure.io/fedora-commops[pagure.io/fedora-commops].

+ Tickets are found under the _https://pagure.io/fedora-commops/issues[Issues]_ menu.

+ 

+ Various tags are listed at the top of the _Issues_ page.

+ For good beginner tasks, look at the _https://pagure.io/fedora-commops/issues?status=Open&tags=good+first+issue[good first issue]_ tag.

+ 

+ 

+ [[meetings]]

+ == Meetings

+ 

+ CommOps holds a meeting once a week on IRC to check in on tasks and plan ahead.

+ Check the https://apps.fedoraproject.org/calendar/commops/[CommOps calendar] for the current date and time.

+ 

+ Past meeting minutes are recorded in https://meetbot.fedoraproject.org/teams/commops/[Meetbot].

+ 

+ 

+ [[meeting-format]]

+ === Meeting format

+ 

+ The upcoming meeting agenda is found on the Fedora https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next[Infinote server].

+ Meetings follow an agenda split into five parts:

+ 

+ . **Roll call**: Waiting for others to arrive, opportunity to introduce yourself and ask general questions

+ . **Announcements**: Any news or updates to share

+ . **Action items from last meeting**: Follow-up on `#action` items from previous meeting

+ . **Tickets**: Discussion and follow-up on tickets https://pagure.io/fedora-commops/issues?status=Open&tags=meeting[marked for meetings]

+ . **Open floor**: General discussion or comments

+ 

+ 

+ [[what-commops-does]]

+ == What CommOps does

+ 

+ CommOps focuses on a few key areas, both technical and non-technical.

+ 

+ === Culture

+ 

+ The Fedora Project builds and ships a Linux distribution, but there is a community behind the technical work and planning.

+ In Fedora, we have the xref:project::index.adoc#_what_is_fedora_all_about[Four Foundations] to represent our community culture.

+ The Fedora community represents a set of ethics and values to how we build our distribution.

+ These ethics and values create the culture of the Fedora Project.

+ When working in the community, mindfulness of this culture enriches and supports the different sub-communities inside of Fedora.

+ 

+ CommOps builds community infrastructure of support and acceptance for the Fedora community's culture.

+ The _Friends_ foundation is there for a reason.

+ The community infrastructure CommOps assists with builds on top of the _Friends_ foundation.

+ People enjoy contributing in a community where they feel valued for who they are and what they bring to the community, not just that they are useful.

+ CommOps supports this through some of our tasks relating to culture.

+ 

+ Examples of things we help with to build and support the culture of the Fedora community:

+ 

+ * https://pagure.io/fedora-commops/issue/17[Interviewing Fedora community members]

+ * https://pagure.io/fedora-commops/issue/110[Fedora Appreciation Week]

+ * https://pagure.io/fedora-commops/issue/138[Top Badgers of the Year]

+ 

+ === Elections

+ 

+ There are a few elected bodies in Fedora: the xref:project::leadership.adoc[Fedora Council], xref:mindshare::index.adoc[Mindshare Committee], and xref:fesco::index.adoc[FESCo].

+ Every new Fedora release, the community holds elections for these bodies.

+ Each election takes "wrangling" work to pull it together.

+ This includes calling for nominations, conducting interviews with candidates, and raising awareness during the voting window.

+ 

+ CommOps supports the xref:council::fpgm.adoc[Fedora Program Manager] in organizing and executing elections.

+ These responsibilities consist of curating content on the xref:community-blog.adoc[Community Blog], creating interview templates, and outreach to grow awareness.

+ 

+ Examples of things we do to help organize and execute Fedora elections:

+ 

+ * https://pagure.io/fedora-commops/issue/7[Fedora Elections and CommOps Coverage]

+ * https://pagure.io/fedora-commops/issue/19[Improve automation of Elections communication]

+ * https://pagure.io/fedora-commops/issue/93[Better explain roles of Council and FESCo]

+ * https://pagure.io/fedora-commops/issue/107[Automated Fedocal reminders to send to all mailing lists for upcoming Elections]

+ * https://pagure.io/fedora-commops/issue/112[Create August 2017 election interview templates for candidates]

+ 

+ === Storytelling

+ 

+ Messaging and storytelling bring the Fedora Project "story" to both contributors and user communities.

+ Every year, a https://mattdm.org/fedora/2018flock/2018-State-of-Fedora.pdf[couple thousand people] work on Fedora.

+ Messaging is a way of sharing our story in multiple formats.

+ We bring the message of what we _as a community_ are doing out to others.

+ Others include our contributors working in other areas of the project and users interested in what the Fedora community produces.

+ When we share our story with each other, we are aware of other work happening in the Fedora community.

+ Communicating the story of Fedora keeps our contributors moving together towards our goals.

+ Good messaging helps our users better understand the goals and objectives of Fedora and how we plan to get there.

+ 

+ CommOps supports messaging by working with other sub-projects and teams to tell their own stories.

+ CommOps provides help to "dig out" the stories and tools to share them widely.

+ This includes tasks like interviews, sharing activities by Fedora contributors, running retrospectives, and more.

+ These tasks keep contributors in sync with what we're working on.

+ They are direct actions to keep everyone on the same page.

+ 

+ Examples of things we do to support messaging and tell stories:

+ 

+ * https://pagure.io/fedora-commops/issue/4[Interviews about goals for team sprints]

+ * https://pagure.io/fedora-commops/issue/66[Call for nominations of a Working Group]

+ * https://pagure.io/fedora-commops/issue/98[Covering upcoming talks by Fedora contributors at a major conference]

+ * https://pagure.io/fedora-commops/issue/100["Help Wanted" columns]

+ * https://pagure.io/fedora-commops/issue/129[Year in Review blog series]

+ 

+ === Metrics

+ 

+ CommOps measures community health and engagement through extensive metrics and data available about Fedora.

+ {FEDMSG}[fedmsg] is a messaging bus with data about activity in the Fedora community.

+ The data includes activity like git commits, new blog posts, wiki page edits, software build status, IRC meeting notes, and more.

+ CommOps works with fedmsg to tell stories about our community, but specific types of stories.

+ The stories told with metrics are helpful to understand what we may be doing right or wrong.

+ It gives us a data-driven way to understand our huge community.

+ 

+ CommOps directly supports metrics in Fedora through development time and data-driven storytelling.

+ Some members develop existing software or build new scripts to analyze data.

+ Others use the data to write reports or studies on how the Fedora community works.

+ Ultimately, metrics are a largely technical area that CommOps helps with.

+ 

+ Examples of metrics work and data-driven storytelling we do:

+ 

+ * https://pagure.io/fedora-commops/issue/32[Analyzing Fedora contributor activity]

+ * https://pagure.io/fedora-commops/issue/88[Fedora release party metrics]

+ * https://pagure.io/fedora-commops/issue/109[Understanding contributor activity by geographic location]

+ 

+ === Supporting sub-projects

+ 

+ CommOps assists other sub-projects and teams in following best practices and communicating effectively.

+ We work with other teams to help them on-board new contributors into their teams.

+ This includes creating Fedora Badge requests, reviewing guidelines, and making Fedora services and tools more understandable.

+ 

+ Examples of sub-project support and on-boarding work:

+ 

+ * https://pagure.io/fedora-commops/issue/62[Wiki gardening of Fedora Join]

+ * https://pagure.io/fedora-commops/issue/69[Fedora Modularity onboarding]

+ * https://pagure.io/fedora-commops/issue/76[Update Onboarding Calendar for GSoC 2016]

+ * https://pagure.io/fedora-commops/issue/95[Onboarding: DotNet SIG]

+ 

+ 

+ [[join-commops]]

+ == Join CommOps

+ 

+ Read our guide on xref:contribute/join.adoc[how to join the CommOps team].

+ 

+ CommOps always welcomes new contributors.

+ Whether you are a newcomer or an old-timer, there are ways to get involved.

+ Join CommOps to:

+ 

+ * 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 superheroine or superhero

+ 

+ .Join the CommOps team today

+ [link="contribute/join/"]

+ image::https://fedoraproject.org/w/uploads/7/72/Happypanda.png[Happy Panda,100]

+ 

+ 

+ [[toolbox]]

+ == Toolbox

+ 

+ The CommOps toolbox explains tools and services often used by the team.

+ The tools are organized by purpose and use.

+ 

+ [[communication-tools]]

+ === Communication tools

+ 

+ These are communication tools to share content and information with others in the Fedora community.

+ 

+ xref:community-blog.adoc[Community Blog] (CommBlog) - https://communityblog.fedoraproject.org/[communityblog.fedoraproject.org]::

+ Centralized blog for contributors to publish news, activities, or calls for help to the rest of the project.

+ Useful place for getting an inside scoop on "what's happening" in Fedora.

+ 

+ https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/fedmsg/irc/templates/ircbot.py?id=0279643#n77[ircbot.py]::

+ Python script for fedmsg notifications in https://libera.chat/[#fedora-commops].

+ Relays real-time updates and changes relating to CommOps in our IRC channel.

+ 

+ 

+ [[metrics-tools]]

+ === Metrics tools

+ 

+ These tools access and use the Fedora messaging bus, {FEDMSG}[**fedmsg**].

+ With these tools, you can generate metrics, analyze data, and interact with fedmsg.

+ 

+ https://github.com/fedora-infra/fedora-stats-tools/blob/develop/annualgrepper.py[annualgrepper]::

+ Gather raw fedmsg totals on https://fedora-fedmsg.readthedocs.io/en/latest/topics.html[topics] in the last year

+ 

+ https://pagure.io/cardsite[cardsite]::

+ Live fedmsg tracker inspired by http://emojitracker.com/[emojitracker]

+ 

+ https://github.com/fedora-infra/fedora-stats-tools/blob/develop/daily-briefing.py[daily-briefing.py]::

+ Template that takes lists of URLs, generates summary reports of daily Meetbot links and action items (manual now, can be automated!)

+ 

+ https://apps.fedoraproject.org/datagrepper/[datagrepper]::

+ The powerhouse tool to interact with fedmsg.

+ Using HTTP GET requests, query for historical data from fedmsg.

+ Examples include events by username, by package, by message source, and more.

+ 

+ {FEDMSG}[fedmsg]::

+ Python package and API that hooks into various Fedora Infrastructure services.

+ Sends messages from each service to a unified message bus in real-time.

+ fedmsg drives and powers all the metrics tools we have.

+ 

+ https://github.com/fedora-infra/fedora-stats-tools[fedora-stats-tools]::

+ Multiple statistics tools, data, and slide decks for fedmsg metrics, Year in Reviews, and Fedora event metrics

+ 

+ https://pagure.io/feedcloud[feedcloud]::

+ Takes an RSS feed or list of RSS feeds and generates fancy word-clouds for them

+ 

+ https://pagure.io/gsoc-stats[gsoc-stats]::

+ Python tool to generate statistics about Fedora contributors

+ 

+ https://github.com/fedora-infra/fedora-stats-tools/blob/develop/longtail-analyze.py[longtail-analyze.py], https://github.com/fedora-infra/fedora-stats-tools/blob/develop/longtail-gather.py[longtail-gather.py]::

+ Measure the ratio of activity per user to approximate burnout

+ 

+ https://github.com/fedora-infra/fedora-stats-tools/blob/develop/meetbot-fedmsg-activity.py[meetbot-fedmsg-activity.py]::

+ Jinja2 template that creates links to Meetbot activities

+ 

+ https://pagure.io/wordcloudbot[wordcloudbot]::

+ Create pretty wordclouds from IRC meeting logs

+ 

+ 

+ [[other]]

+ === Other

+ 

+ Other tools that don't belong elsewhere fit under here.

+ 

+ https://github.com/OSAS/rh-events[OSAS/rh-events]::

+ Data for Red Hat conference and talk attendance.

+ Useful for plotting events in our own calendar and keeping track of what's happening in the open source community.

file modified
+1 -1
@@ -16,7 +16,7 @@

  *** xref:advocate-logo.adoc[Logos]

  *** xref:advocate-badges.adoc[Badges]

  ** CommOps

- *** xref:commops.adoc[Team Overview]

+ *** https://docs.fedoraproject.org/en-US/commops/index1.adoc[Team Overview]

  *** xref:commops-role.adoc[Member Roles]

  *** xref:mindshare-reps.adoc[Rep Roles]

  *** xref:commlogo.adoc[Logos]

no initial comment

Pull-Request has been merged by sumantrom

7 months ago