This docs outlines all the activities you can get involved in to help with Fedora QA and is meant to guide you through the QA ecosystem. It’s easy to get involved and we love to welcome people to the group! The first thing you probably want to do is get plugged in to all the right sources of information for Fedora QA.
There are six steps you can take to get up to speed with QA efforts (in rough order of precedence):
Whether you are looking to test a stable release, a new package from updates-testing, a Branched pre-release, or the leading edge Rawhide, QA has a way for you to contribute and get involved! We need people who like to push all the buttons, use all the command line options, verify all the documentation, review things for usability, and suggest future features - especially for anything that’s undergone major change in a recent or pending release.
Work on an upcoming stable release
Work on testing new package updates
I want to do something else!
For all of those tasks, it would be good to have some familiarity with our Bugzilla instance. A lot of contribution to Fedora QA comes through bug reports. All you need is a Bugzilla account: create your account. Please make sure that the email addresses for your Fedora account and the Bugzilla account are the same. Our bug reporting practices provide some good background for filing bugs. If you want to discuss the bugs before reporting, QA members can be found on the test mailing list and the #fedora-qa IRC channel. The mailing list is a great place to raise any questions or problems you are having. Experienced QA Members are more than happy to act as mentors for new members to help them get started with QA. There is no requirement of programming knowledge. However, being familiar with Fedora and Linux in general will be extremely useful.
If you haven’t found here what you were looking for, try to visit our QA wiki page to see more information about our team and activities.
Want to help? Learn how to contribute to Fedora Docs ›