| |
@@ -0,0 +1,100 @@
|
| |
+ include::docs/entities.adoc[]
|
| |
+
|
| |
+ = Join Community Operations
|
| |
+
|
| |
+ Become a member of Fedora Community Operations (CommOps) by following these steps.
|
| |
+
|
| |
+
|
| |
+ [[fas]]
|
| |
+ == Create a FAS account
|
| |
+
|
| |
+ Create a {FWIKI}Account_System[Fedora Account System account] and sign the {FWIKI}Legal:Fedora_Project_Contributor_Agreement[Fedora Project Contributor Agreement].
|
| |
+ Do this through the {FWIKI}Infrastructure/AccountSystem[Fedora Account System].
|
| |
+
|
| |
+
|
| |
+ [[mailing-list]]
|
| |
+ == Join the mailing list
|
| |
+
|
| |
+ Subscribe to the https://lists.fedoraproject.org/admin/lists/commops.lists.fedoraproject.org[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.
|
| |
+
|
| |
+
|
| |
+ [[introduction]]
|
| |
+ == Send a self-introduction
|
| |
+
|
| |
+ Say hello and introduce yourself to the team!
|
| |
+ Send a self-introduction to the mailing list and tell us a little about yourself (click mailto:commops@fedoraproject.org[here, Self-Introduction: your name 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?
|
| |
+
|
| |
+
|
| |
+ [[community-blog]]
|
| |
+ == Register on Community Blog
|
| |
+
|
| |
+ The Fedora https://communityblog.fedoraproject.org[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 https://communityblog.fedoraproject.org/wp-login.php[login page] with your Fedora Account System (FAS) credentials.
|
| |
+
|
| |
+ Need more help logging in?
|
| |
+ Read the https://communityblog.fedoraproject.org/how-to-log-in/[help page] for more detailed instructions.
|
| |
+
|
| |
+
|
| |
+ [[irc]]
|
| |
+ == Join our IRC channel
|
| |
+
|
| |
+ Fedora uses the https://freenode.net[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.
|
| |
+
|
| |
+ Never used IRC before?
|
| |
+ See the https://fedoramagazine.org/beginners-guide-irc/[Beginner's Guide to IRC] on the Fedora Magazine.
|
| |
+ If you want to stay connected even when you are not online, consider https://opensource.com/article/17/5/introducing-riot-IRC[using Riot] as your IRC client.
|
| |
+
|
| |
+
|
| |
+ [[first-steps]]
|
| |
+ == Make your first steps
|
| |
+
|
| |
+ See link::contribute/join.adoc[Make your first steps in Fedora] for more info.
|
| |
+
|
| |
+
|
| |
+ [[start-task]]
|
| |
+ == Start on a task
|
| |
+
|
| |
+ CommOps uses https://pagure.io/fedora-commops[this Pagure repository] to track our tasks and what we're working on.
|
| |
+ Tasks, problems, and goals are filed as tickets in the https://pagure.io/fedora-commops/issues[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 https://pagure.io/fedora-commops/issues?status=Open&tags=good+first+issue[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.
|
| |
+
|
| |
+
|
| |
+ [[meetings]]
|
| |
+ == Join our meetings
|
| |
+
|
| |
+ 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 https://apps.fedoraproject.org/calendar/commops/[CommOps meeting calendar].
|
| |
+ Feel free to attend and introduce yourself during roll call!
|
| |
Finally, it's done! This PR closes #122.
This is an updated version of our CommOps/Join page. I also updated the instructions to be more accurate for how we're running things in 2018 (it was last given a serious review in 2016).
Once we figure out how this deploys and builds tomorrow, I'll set up a permanent redirect on the wiki page to point to the doc.
{{#fedoradocs: https://docs.fedoraproject.org/whatever-the-of-this-new-page}}