|Description||The Gentoo Quality Assurance team|
Last elected: 2016/05/07
(and inherited members)
|Parent Project||Gentoo Linux|
The Gentoo Quality Assurance Project aims to keep the portage tree in a consistent state across all the architectures. This means that syntax, dependencies (both compile-time and run-time), file sizes, changelog and metadata entries are all kept up to date and as accurate as possible. We work with other teams to address problems found with their packages, and create QA policies that reflect the best practices to follow when working on ebuilds. In addition to that, we keep up to date technical documentation to assist developers with working on packages in the tree, in a general sense.
- Keep the tree in a state which benefits all of our users and developers alike.
- Create documentation to assist developers.
- Work with other teams to overcome deficiencies in tools Gentoo uses to better suit the needs of all developers and users.
- Develop QA policies with the interest of improving the quality of Gentoo overall.
Resources offered by the QA project are:
Role, purpose and projects
- When and how do I ask the Quality Assurance team to look into a problem?
- gentoo-qa mailing lists
- #gentoo-qa channel on Freenode.
- --as-needed introduction and fixing guide
- Handling Libtool archives in Gentoo
- Automagic dependencies, what they are and how to fix them
- How to fix autotools failures
- How to get meaningful backtraces in Gentoo
Policies and Discussion
All current and future Gentoo developers should endeavor to be a part of the QA project in some fashion. This includes helping to come up with a QA policy, as well as doing your part to ensure that your packages meet a certain set of QA standards. Additionally, we hope that all Gentoo developers will be co-operative in finding and fixing QA issues. Future and prospective developers can contact our recruiters. Ongoing QA projects may be found at Project:Quality_Assurance/Current_projects
Joining the Team
To join the team (as an existing developer), email firstname.lastname@example.org or the current team leader with a short summary of what you want to do as a QA team member and your qualifications.