| |
@@ -0,0 +1,107 @@
|
| |
+ = Get involved with Fedora Diversity and Inclusion Team
|
| |
+
|
| |
+ Interested in helping the Fedora Diversity and Inclusion Team?
|
| |
+ This page explains the typical process for getting involved with our team.
|
| |
+
|
| |
+
|
| |
+ [[create-fas-account]]
|
| |
+ == Create Fedora Account System (FAS) account
|
| |
+
|
| |
+ All contributors to Fedora need to register in the https://admin.fedoraproject.org/accounts/[Fedora Account System].
|
| |
+ New contributors are asked to sign the https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement[Fedora Project Contributor Agreement] (FPCA).
|
| |
+ This is not a copyright assignment agreement, but ensures your contributions to Fedora have acceptable licensing terms.
|
| |
+ If you need help with this, contact the https://fedoraproject.org/wiki/Infrastructure#Communicating[Fedora Infrastructure Team].
|
| |
+
|
| |
+
|
| |
+ [[mailing-list]]
|
| |
+ == Join the mailing list
|
| |
+
|
| |
+ https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org[**Subscribe here!**]
|
| |
+
|
| |
+ The Fedora Diversity and Inclusion Team uses a mailing list.
|
| |
+ The mailing list is used for announcements, summaries of meetings, and a way to share longer-form content with the team.
|
| |
+ It is a good place to keep up with what we are up to!
|
| |
+ To join the mailing list, subscribe on https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org[lists.fedoraproject.org].
|
| |
+
|
| |
+
|
| |
+ [[self-introduction]]
|
| |
+ == Send a self-introduction
|
| |
+
|
| |
+ If you want to get involved, we want to get to know you!
|
| |
+ So don't be shy, send an introduction on our mailing list.
|
| |
+ This is a helpful step for other folks on the team to get to know you.
|
| |
+
|
| |
+ Not sure what to say?
|
| |
+ Does writing an introduction feel awkward?
|
| |
+ Consider these questions when introducing yourself:
|
| |
+
|
| |
+ * Are you new to the Fedora community?
|
| |
+ If so, what was interesting to you about Fedora?
|
| |
+ * Are you involved with other communities?
|
| |
+ Tell us about what you do in other communities or projects.
|
| |
+ * Do you already contribute to Fedora?
|
| |
+ Let us know what parts of Fedora you are involved in.
|
| |
+ * Are you an organizer of local events or programs?
|
| |
+ If you run any kind of event in your local community, let us know what you do.
|
| |
+ * What is interesting to you about the Fedora Diversity and Inclusion Team?
|
| |
+ Our team is a collection of people with different interests and niches.
|
| |
+ Knowing each others' interests and what we like lets us connect each other to things we want to help out with.
|
| |
+
|
| |
+
|
| |
+ [[join-irc-telegram]]
|
| |
+ == Join IRC/Telegram group chat
|
| |
+
|
| |
+ The Fedora Diversity and Inclusion Team has a real-time group chat.
|
| |
+ We use this group chat for quick updates, friendly chatter, and running meetings.
|
| |
+ We use both an IRC channel on the https://freenode.net/[Freenode IRC network] and a Telegram chat group.
|
| |
+ Both are bridged to each other, so folks in IRC will see Telegram messages and vice versa.
|
| |
+
|
| |
+ Here are the easiest ways to join:
|
| |
+
|
| |
+ * IRC
|
| |
+ ** link:ircs://chat.freenode.net:6697/%23fedora-diversity[`chat.freenode.net/#fedora-diversity`]
|
| |
+ ** https://webchat.freenode.net/?channels=#fedora-diversity[Web chat]
|
| |
+ * https://t.me/fedoradiversity[Telegram]
|
| |
+
|
| |
+ Don't forget to say hi when you join!
|
| |
+
|
| |
+
|
| |
+ [[first-steps]]
|
| |
+ == Make your first steps
|
| |
+
|
| |
+ See xref:commops::contribute/first-steps.adoc[Make your first steps in Fedora] for more info.
|
| |
+
|
| |
+
|
| |
+ [[attend-meeting]]
|
| |
+ == Attend a meeting
|
| |
+
|
| |
+ https://apps.fedoraproject.org/calendar/diversity-team/[**Find our next meeting on our calendar!**]
|
| |
+
|
| |
+ The team usually holds a weekly meeting over IRC/Telegram to review on-going work and determine next steps on current work.
|
| |
+ The meeting format is intended to be quick updates instead of long discussion.
|
| |
+ It is a good opportunity to say hello and meet other members of the team in real-time.
|
| |
+
|
| |
+
|
| |
+ [[tickets]]
|
| |
+ == Check out Pagure tickets
|
| |
+
|
| |
+ The next step to get involved is to review our ticket tracker and look for something interesting to you.
|
| |
+ All of our open tickets are in our https://pagure.io/fedora-diversity/issues[Pagure repository].
|
| |
+ New tasks are added as "issues" into the Pagure repository.
|
| |
+
|
| |
+ Here is a quick index of different types of tickets:
|
| |
+
|
| |
+ * https://pagure.io/fedora-diversity/issues?status=Open&priority=20[Meeting tickets]
|
| |
+ * https://pagure.io/fedora-diversity/issues?status=Open&tags=good+first+issue[Good first tickets for newcomers]
|
| |
+ * https://pagure.io/fedora-diversity/roadmap[Roadmap] (collection of tickets around specific objectives or goals)
|
| |
+
|
| |
+ See a ticket that looks interesting?
|
| |
+ If someone is not already assigned, leave a comment and ask how you can help.
|
| |
+ Another member of the team will get back to you with some feedback on how you get help.
|
| |
+ This is one opportunity to get mentorship and help with getting started on a task.
|
| |
+
|
| |
+ Alternatively, do you think something is missing or could be improved in the Fedora community?
|
| |
+ Open a new ticket with your idea or suggestion.
|
| |
+ Our best ideas come from a wide range of people with different backgrounds, experiences, and perspectives.
|
| |
+ Whether you are new to the Fedora community or are a long-time contributor, you might have the next great idea for the team.
|
| |
+ Open a new ticket and we can discuss more about your idea or suggestion.
|
| |
This commit is a significant rewrite of our "Get involved" page. I expanded some parts, rewrote some parts to be more clear, fixed a lot of URLs, and removed some parts that are not a major part of actually getting involved as a team member. My edits are briefly explained below:
xref
to CommOps docs