Become a member of Fedora Community Operations (CommOps) by following these steps.
Subscribe to the Fedora CommOps mailing list to receive email discussion by the team. The mailing list receives low to medium volume.
The mailing list is a key part to how we communicate. News, updates, and discussion are shared through our mailing list.
Say hello and introduce yourself to the team! Send a self-introduction to the mailing list and tell us a little about yourself (click here to send an intro).
Not sure what to say? Answer some of these questions to get started:
Why are you interested in contributing to Fedora?
Why are you interested in contributing to CommOps?
If you’re involved with other things in Fedora, what are/were you working on?
Do you have any experience in open source or online communities? If so, what?
What parts of CommOps were interesting to you?
Do you have any questions for us? How can we help you get started?
The Fedora Community Blog is a key component to CommOps. An account gives permissions to view article drafts and previews before they are published. If you ever write an article, you will need an account. To register, log in at the login page with your Fedora Account System (FAS) credentials.
Need more help logging in? Read the help page for more detailed instructions.
Fedora uses the Freenode IRC network for instant messaging and communication. Short discussions and planning happen in our IRC channel. Our weekly team meetings also take place on IRC.
See Make your first steps in Fedora for more info.
CommOps uses this Pagure repository to track our tasks and what we’re working on. Tasks, problems, and goals are filed as tickets in the issue tracker. There are a lot of tickets, but we’re not working on everything at once. Scrolling through the issue tracker gives a good idea of what CommOps helps with.
Look for the good first issue tag on tickets to find good tasks for beginners.
Does something look interesting? Leave a comment if you have a question or want to work on something. Also check and see if the ticket has an owner. If there is no owner, you can take lead on it! If there is, ask if the owner needs help or if they are still working on the ticket.
This provides you an opportunity to receive mentorship and get help to start a new task.
CommOps has an IRC team meeting each week. In our meeting, the team discusses items on our agenda and checks in on any progress of current tasks. Tickets selected for meetings are updated after the meeting with new information.
The meetings are open to the public and anyone can join. See when our meetings are in your time zone on the CommOps meeting calendar. Feel free to attend and introduce yourself during roll call!