| |
@@ -1,19 +1,25 @@
|
| |
- # Community + Operations = CommOps
|
| |
+ Community + Operations = **CommOps**
|
| |
+ ====================================
|
| |
|
| |
- This repository maintains tasks, goals, and objectives for the [Community Operations](https://fedoraproject.org/wiki/CommOps) team.
|
| |
-
|
| |
- 
|
| |
+ Community Operations, a.k.a. CommOps, addresss community infrastructure by
|
| |
+ providing tools, resources, and utilities for different sub-projects to improve
|
| |
+ communication across Fedora
|
| |
|
| |
|
| |
## What can I do here?
|
| |
|
| |
- You can [file an issue](https://pagure.io/fedora-commops/new_issue) to:
|
| |
+ [File a ticket](https://pagure.io/fedora-commops/new_issue) to:
|
| |
|
| |
* Share information in one area of the Project with the rest
|
| |
* Requesting metrics about an area of the Project
|
| |
* More coming soon…
|
| |
|
| |
- You can also help us out too! Take a look at the [active issue list](https://pagure.io/fedora-commops/issues) and look for an issue assigned with a blank assignment, and feel free to take that task yourself. If there aren't any open issues, ask on our [mailing list](https://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org/) where you can help out.
|
| |
+ You can also help us out too! Take a look at the [active issue
|
| |
+ list](https://pagure.io/fedora-commops/issues) and look for an issue assigned
|
| |
+ with a blank assignment, and feel free to take that task yourself. If there
|
| |
+ aren't any open issues, ask on our [mailing
|
| |
+ list](https://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org/)
|
| |
+ where you can help out.
|
| |
|
| |
Because this is mainly a volunteer-staffed team, we may not notice all new issues immediately when they are filed. If you think an issue needs attention, try to contact the owner and see if they are working on it. If you don't hear from them within a week, you can probably take over the task.
|
| |
|
| |
jflory7
commented 6 years ago
This makes trivial changes to the README.
Really, the purpose of this PR is to test the continuous integration (CI) hook that @cverna is helping us with. Fingers crossed!
(Making this again per the comment in #142)