
Welcome to Fedora!
Fedora is not just an Operating System. It is the future. A future for how we work, how we play, how we make and how we communicate. The technology that Fedora builds first is integrated into some of the world’s most important infrastructure.
We are the people that build Fedora. Some of us came here to make something we just had to, some for a life-long career and some to be with people with similar skills and interests.
People join Fedora with all kinds of skill sets. Some are advanced engineers with many years experience, others have just left high school. Wherever you are in your journey, Fedora welcomes you to participate in our community. We welcome people from all over the planet. We support diversity of all types as it strengthens the whole.
If you support the code of conduct and core values of Freedom, Friends, Features and First there will likely be somewhere for you to fit in. If you want to know what makes a good contributor to Fedora, we have a section on that.
Fedora is not strictly speaking a software development centre. One of our core principles is Upstream First. This is so we can give back to the broader Linux community.
What we do:
Fedora is divided into a number of working areas. You can see our organization chart. We do everything from running servers and writing code to design and event management.
If you would like to be part of our community, you do not need to know everything or promise much. We want you to learn, connect and identify what you would like to become. We will not give you a job. We will help you find your way around the Fedora ecosystem to find a group or project that fits your skills.
You do not need to sign up to do this yourself. Feel free to join in on our Matrix Channel or our discussion forums. It is a good idea to read the docs (plus other places!) and have a good look around before contacting us.
Getting Started:
As a newcomer to Fedora, all your access starts with an account. Sign up here. You will be asked for your name and a username. The name and username you put in may be public, but you can put in whatever you like. You can change your name later, but you cannot easily change your username.
It really helps us if you introduce yourself on Matrix or on the forums. We want to know who you are so we can work together better. Don’t be afraid of saying too much, if you like cooking or anime as well as Python and Inkscape many of us will too! A good working environment lets you talk about all the things that interest you (as long as it fits the code of conduct). Just don’t publish your home address or passwords!
Feel free to approach people in your areas of interest. We want to double the number of contributors we have, and we want to make sure Fedora has an active and engaging future. When approaching people, write as much as you can. Lay out neatly and succinctly and give as much information as you want to receive. People here like to read, and the more you tell us the more we can tell you.
You will be 'Fedora' when you have found and made your first contribution to a project or group.
Onboarding:
Once you have decided you would like to stick around, or would like a hand getting introduced, we can 'onboard' you. This means we will give you a little bit more access to systems and can introduce you to teams. The 'behind the scenes' process is detailed below, it’s up to you if you want to know how we do it.
To begin the onboarding, we need to know your username. All you have to do is
1) Login to Pagure with your Fedora account once, and 2) Reachout via Join Fedora on Matrix or on the mailing list which you can subscribe
And that is it! You are one of us now, for as long as you would like.
Remember, there is no minimum commitment. Take the time to look around.
We would of course recommend you to use Fedora :)
Onboarding New Joiners (workflow for the Join SIG team)
When a new person joins the Fedora community, they may not know what they want to do. The Join SIG aims to help people to explore the community and find their area of interest.
We go through the following steps with the new person.
1) We tag tickets. - Tags starting with "S:" track the status of the ticket from their perspective. - Tags starting with "C:" track the status of the ticket from the community’s perspective. - Tags starting with "I:" track their interests.
2) We ask $USER to subscribe to the Fedora Join mailing list. This is so people can interact via e-mail if they wish, and can stay informed on what happens in the community. The associated tag is: S: Subscribed.
3) We open a new "Hello Fedora World" ticket for the $USER and add them to the fedora-join
group in Pagure. The associated tag is: S: Hello Fedora World.
4) We ask the $USER to introduce themselves, preferably via the mailing list. The associated tag is: C: Introduction requested. When $USER have introduced themself, we mark the ticket with the S: Introduced myself tag.
-
People can comment on their tickets whenever they need to ask questions, to give feedback, or just to chat.
-
When the $USER need a response, they can use the C: Needs response tag to gain the community’s attention.
-
The $USER then spend time exploring Fedora, speaking to people, learning how things work; all at their own pace. $USER is not expected to do any tasks at this time. The idea is to get comfortable with the Fedora community and ecosystem before contributing.
5) Every two weeks we check to see how the $USER is doing. Each time we do so, we set a new tag. At the first progress check, we will set the C: Progress check 1 tag. If we do not hear from the $USER in approximately two weeks, we do a second progress check and set the C: Progress check 2 tag.
-
If we do not hear from the $USER again for another two weeks, we do a final progress check. We set the C: Progress check 3 - Final tag.
-
If we do not hear from the $USER in the total of 6 weeks, we assume that the $USER is inactive and close the ticket with the S: User unresponsive tag.
6) Some infrastructure in Fedora requires users to be part of a team or group on the Fedora Account System. We can give temporary membership to the "Fedora-Join" FAS group if a new user requires. This can be requested by setting the C: Temporary membership needed tag. After discussing the situation, if temporary membership to the FAS group is given, we will mark the ticket with the C: Temporary membership approved tag, and grant the temporary membership.
7) When $USER feel that they no longer need our help or don’t have the time, we can close the ticket. If $USER decide to exit the Fedora community we will close the ticket with the tag S: User closed. The $USER can re-engage with the community or re-open the ticket anytime.
8) As the $USER learn about the community and ecosystem, they will hopefully find tasks and teams that interest them. When the $USER have joined a team, they has become a contributing Fedora community member! We mark the ticket as S: I am Fedora to celebrate this.
9) We collect feedback from new community members at any time and at close of ticket. For this, we use the S: Feedback.
10) When $USER comments that they don’t have time to interact with the community, we can close the ticket. Let them know that they can have it reopened once they have some time to spare.
Want to help? Learn how to contribute to Fedora Docs ›