Project:Quality Assurance
| Quality Assurance | |
|---|---|
| Description | The Gentoo Quality Assurance team |
| Project email | qa@gentoo.org |
| IRC channel | #gentoo-qa (webchat) |
| Bugs | Related bugs |
| Lead(s) |
Last elected: 2023-07-23 |
| Member(s) |
|
| Subproject(s) (and inherited member(s)) |
|
| Parent Project | Gentoo |
| Project listing | |
The Gentoo Quality Assurance Project aims to keep the Gentoo ebuild repository 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.
Goals
- 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
Resources offered by the QA project are:
Role, purpose, and projects
- GLEP 48: QA team's role and purpose
- Current projects — to list ongoing projects upon which QA members and contributors may work.
Communication
- When and how do I ask the Quality Assurance team to look into a problem?
- gentoo-qa mailing lists
- #gentoo-qa (webchat) channel on Libera.Chat.
Documentation
- --as-needed introduction and fixing guide — explains how the
--as-neededLDFLAG works and provides the steps needed to fix simple cases where--as-neededfails to build a package. - Handling Libtool archives in Gentoo
- Automagic dependencies, what they are and how to fix them
- How to fix autotools failures — describes the common situations which makes autotools fail to run in an ebuild and gives advice on how to fix the associated issues.
- How to get meaningful backtraces in Gentoo — provides users with a simple explanation of why a default Gentoo installation does not provide meaningful backtraces and how to set it up to get them.
- How to use subslots and slot operators
- Updating Policy Guide
Policies and discussion
- Gentoo Policy Guide
- Meeting agenda — topics to be discussed by the QA team at its next meeting.
- Meeting summaries — summarizes previous QA team meetings.
- UID/GID assignment — a list of existing fixed UID/GID assignments in Gentoo.
- Upstream remote-id types — a list of remote-id types that can be used in the
<upstream>element in package metadata.
Participation
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 Current_projects.
Joining the team
To join the team (as an existing developer), email qa@gentoo.org or the current team leader with a short summary of what you want to do as a QA team member and your qualifications.