qaGentoo Quality Assurance
The Quality Assurance Project provides an umbrella project for keeping
Gentoo's 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.

The Gentoo Quality Assurance Project aims to keep the portage tree in a consistent
state. 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

creffettpinkbytetommy
Repoman is a tool that is used by Gentoo developers to perform pre-commit
quality checks. It is available as part of portage package.
Sven has taken the code and updated it to perform better and more thorough
checks on a tree wide basis.
I Want to Participate

All current and future Gentoo developers should endeavour 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.

GLEP 48: QA Team's Role and Purpose
--as-needed introduction and fixing guide
Automagic dependencies, what they are and how to fix them
How to fix autotools failures
How to get meaningful backtraces in Gentoo
gentoo-qa mailing lists
#gentoo-qa channel on FreeNode