- Python 72.1%
- HTML 27.7%
- Shell 0.2%
Justin Wheeler
43615cc142
This commit obliterates all content in this repository that is related to Community Ops docs content. Since we moved to Forgejo, we have a more organized workspace for the Community Ops Team to collaborate. Also, several other Fedora teams are adopting a convention of having a dedicated "docs" repo inside their Forgejo organization. This commit brings the Community Ops Team docs content in line with other Fedora teams using this convention of a dedicated docs repository. Additionally, I already updated the Fedora Docs builder repository to use the new git repository as the source for building the content for our Fedora Docs site. ref: https://forge.fedoraproject.org/commops/docs Signed-off-by: Justin Wheeler <jwheel@redhat.com> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| data | ||
| email-templates | ||
| scripts | ||
| LICENSE.txt | ||
| README.md | ||
Community + Operations = CommOps
The Fedora Community Operations Team provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.
What CommOps does
The following areas are examples of where CommOps focuses:
- Work closely with Fedora Community Architect to prioritize key focus areas
- Assist Fedora Operations Architect with release preparations
- Support preparation and execution of 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
Read more about us on docs.fedoraproject.org.
What can I do here?
File a ticket for topics such as the following:
- Culture
- Elections
- Storytelling
- Metrics
- Supporting sub-projects
You can also help us! Read our getting started guide for new contributors to get involved. After reviewing the guide, check out any open tickets marked as good first issue. If you are not sure where to start, ask any questions or doubts on the Discussion forum.
If an issue needs urgent attention, contact the ticket assignee to check on their progress. If you don’t hear back within a week, you can take ownership of the task.
As our team is mostly volunteers, we may not notice new issues immediately. Thank you for your understanding!
Get in touch with us
The Fedora Community Operations (CommOps) Team uses both a Fedora Discussion forum tag and a Fedora Chat/Matrix room for communication.
- Fedora Discussion Forum: This forum is ideal for asynchronous communication, where responses may come later. It’s the best place for longer, threaded discussions or when you have a question that doesn’t need an immediate answer.
- Fedora Chat/Matrix Room: This chat is optimal for synchronous, real-time conversations. Use it when you need quick feedback or want to discuss something actively and interactively with other team members.
Get involved
Read our guide on how to join the Fedora Community Operations Team
The team is always excited to welcome new contributors. Whether you’re just starting out or a seasoned Fedora member, there are plenty of ways to get involved and make an impact.