| |
@@ -7,24 +7,32 @@
|
| |
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 https://docs.fedoraproject.org/fedora-project/council/fcaic.html[Fedora Community Action and Impact Coordinator] to prioritize key focus areas
|
| |
- * Assist https://docs.fedoraproject.org/fedora-project/council/fpgm.html[Fedora Program Manager] with release preparations
|
| |
- * Support preparation and execution of Fedora Elections
|
| |
+ * 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 fully below)
|
| |
+ * And more (detailed below)
|
| |
|
| |
|
| |
[[find-commops]]
|
| |
== Where to find CommOps
|
| |
|
| |
The CommOps team uses a mailing list and https://en.wikipedia.org/wiki/Internet_Relay_Chat[IRC] channel to communicate.
|
| |
+
|
| |
The mailing list 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 discussions.
|
| |
+
|
| |
The CommOps IRC channel on the https://freenode.net/[Freenode 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.
|
| |
|
| |
Mailing list:: commops [at] lists [dot] fedoraproject [dot] org (https://lists.fedoraproject.org/admin/lists/commops.lists.fedoraproject.org/[subscribe here])
|
| |
IRC channel:: irc://irc.freenode.net/#fedora-commops[#fedora-commops] on Freenode
|
| |
+ 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.
|
| |
@@ -35,8 +43,7 @@
|
| |
== Workflow
|
| |
|
| |
CommOps uses a ticket-based workflow to keep track of our work.
|
| |
- The repository with tickets is on https://pagure.io/[Pagure].
|
| |
- The repository is named https://pagure.io/fedora-commops[fedora-commops].
|
| |
+ 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.
|
| |
@@ -46,10 +53,10 @@
|
| |
[[meetings]]
|
| |
== Meetings
|
| |
|
| |
- CommOps holda a meeting once a week on IRC to check in our tasks and plan ahead.
|
| |
+ 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].
|
| |
+ Past meeting minutes are recorded in https://meetbot.fedoraproject.org/teams/commops/[Meetbot].
|
| |
|
| |
|
| |
[[meeting-format]]
|
| |
@@ -73,14 +80,14 @@
|
| |
=== 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 https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html#what-is-fedora-all-about[Four Foundations] to represent our community culture.
|
| |
+ 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 culture of the Fedora community.
|
| |
+ 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.
|
| |
+ 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.
|
| |
|
| |
@@ -92,13 +99,13 @@
|
| |
|
| |
=== Elections
|
| |
|
| |
- There are a few elected bodies in Fedora, such as the https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council], https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/mindshare.html[Mindshare Committee], and https://docs.fedoraproject.org/fedora-project/subprojects/fesco/fesco.html[FESCo].
|
| |
+ 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 together.
|
| |
+ 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 https://docs.fedoraproject.org/fedora-project/council/fpgm.html[Fedora Program Manager] in organizing and executing elections.
|
| |
- These responsibilities consist of curating content on the https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/docs/community-blog.html[Community Blog], creating interview templates, and outreach to grow awareness.
|
| |
+ 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:
|
| |
|
| |
@@ -110,8 +117,8 @@
|
| |
|
| |
=== Storytelling
|
| |
|
| |
- Messaging and storytelling bring the "story" of the Fedora Project to both the contributor and user community.
|
| |
- Every year, a https://mattdm.org/fedora/2018devconf/DevConfcz2018Charts.pdf[couple thousand people] work on Fedora.
|
| |
+ 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.
|
| |
@@ -120,7 +127,7 @@
|
| |
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 the help to "dig out" the stories and the tools to share them widely.
|
| |
+ 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.
|
| |
@@ -170,15 +177,18 @@
|
| |
[[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 working on real-world projects
|
| |
- * Gain holistic view of the Fedora Project and learn how the pieces fit together
|
| |
+ * 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 superhero
|
| |
+ * Aspire to the greatness of a community superheroine or superhero
|
| |
|
| |
.Join the CommOps team today
|
| |
[link="contribute/join/"]
|
| |
@@ -189,14 +199,14 @@
|
| |
== Toolbox
|
| |
|
| |
The CommOps toolbox explains tools and services often used by the team.
|
| |
- The tools are organized by their purpose and use.
|
| |
+ The tools are organized by purpose and use.
|
| |
|
| |
[[communication-tools]]
|
| |
=== Communication tools
|
| |
|
| |
- These tools are for communicating to others in the Fedora community.
|
| |
+ These are communication tools to share content and information with others in the Fedora community.
|
| |
|
| |
- https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/docs/community-blog.html[Community Blog] (CommBlog) - https://communityblog.fedoraproject.org/[communityblog.fedoraproject.org]::
|
| |
+ 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.
|
| |
|
| |
@@ -208,7 +218,7 @@
|
| |
[[metrics-tools]]
|
| |
=== Metrics tools
|
| |
|
| |
- These tools access and use the Fedora messaging bus, **fedmsg**.
|
| |
+ 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]::
|
| |
@@ -245,9 +255,6 @@
|
| |
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://github.com/fedora-infra/statscache[statscache]::
|
| |
- Daemon to build and keep highly-available fedmsg statistics
|
| |
-
|
| |
https://pagure.io/wordcloudbot[wordcloudbot]::
|
| |
Create pretty wordclouds from IRC meeting logs
|
| |
|
| |
This commit makes minor content revisions and corrections, moves more cross-document linking from hard-coded URLs to internal Antora anchors, and removes statscache from the CommOps toolbox, since it is likely to go away in the near future.
Actual changes to source content were kept minimal, other than a slight modernization to current times. More unique content change will come in later PRs.
For content review, @bt0dotninja @bex @bee2502 @dhanesh95 @meskarune @wesleyotugo @x3mboy could any of you take a quick look?
For an
xref
sanity check, @asamalik @bex @pbokoc could one of you verify how I did these, mostly for theindex.adoc
file?