You've arrived at the homepage of the Quality Assurance team. QA is a vital part of any software project, as it is where code is put to the test to ensure the best user experience possible. Every piece of software has its share of bugs - it is the job of QA to ensure that these bugs are found, confirmed, highlighted & prioritized so developers can fix them.
Here you will find information about the primary role of LibreOffice QA, how QA goes about fulfilling this role, and how to get involved, and even learn a bit about some of our team members.
If you are new to the project and wish to contribute, QA is a fantastic entry point for many reasons, one of the best reasons being contributing through the QA process requires no coding experience. We encourage you to explore this site, join us on IRC, join our mailing list, and to contact any of the team members listed on our QA team page with any questions you may have.
The primary responsibility of QA can easily be summarized as:
Doing our due dilligence to ensure a great user experience
Bug Confirmation/Prioritization (beginner task): The great thing about open source is that users participate heavily in bug reporting. It is the job of QA to investigate these bugs, confirm them, and lastly prioritize them. This process is known as triaging. For detailed instructions on this process please read our WIKI.
Getting involved with QA is incredibly easy. As mentioned at the beginning of this page no programming skills are needed to get involved with QA work. That being said, there are a few personality traits that are needed by our QA team:
If you have at least the first four things we encourage you to get involved. The easiest way to do this is to collaborate with experienced QA members. We have two primary ways to accomplish this and our team prides itself in its friendly and jovial nature. If you put out minimal effort - we will meet you more than half way :) Please find us on: