| 1 |
<?xml version="1.0" encoding="UTF-8"?> |
| 2 |
<?xml-stylesheet href="/xsl/project.xsl" type="text/xsl"?> |
| 3 |
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> |
| 4 |
<!DOCTYPE project SYSTEM "/dtd/project.dtd"> |
| 5 |
|
| 6 |
<project> |
| 7 |
<name>qa</name> |
| 8 |
<longname>Gentoo Quality Assurance</longname> |
| 9 |
<description> |
| 10 |
The Quality Assurance Project provides an umbrella project for keeping |
| 11 |
Gentoo's portage tree in a consistent state across all the architectures. |
| 12 |
This means that syntax, dependencies (both compile-time and run-time), |
| 13 |
file sizes, changelog and metadata entries are all kept up to date and as |
| 14 |
accurate as possible. |
| 15 |
</description> |
| 16 |
|
| 17 |
<longdescription><p> |
| 18 |
The Gentoo Quality Assurance Project aims to keep the portage tree in a consistent |
| 19 |
state. We work with other teams to address problems found with their packages, and |
| 20 |
create QA policies that reflect the best practices to follow when working on ebuilds. |
| 21 |
In addition to that, we keep up to date technical documentation to assist developers |
| 22 |
with working on packages in the tree, in a general sense. |
| 23 |
</p></longdescription> |
| 24 |
|
| 25 |
<goals> |
| 26 |
<ul> |
| 27 |
<li> |
| 28 |
Keep the tree in a state which benefits all of our users and developers alike |
| 29 |
</li> |
| 30 |
<li> |
| 31 |
Create documentation to assist developers |
| 32 |
</li> |
| 33 |
<li> |
| 34 |
Work with other teams to overcome deficiencies in tools Gentoo uses |
| 35 |
to better suit the needs of all developers and users |
| 36 |
</li> |
| 37 |
<li> |
| 38 |
Develop QA policies with the interest of improving the quality of Gentoo overall |
| 39 |
</li> |
| 40 |
</ul> |
| 41 |
</goals> |
| 42 |
|
| 43 |
|
| 44 |
<dev role="Lead">flameeyes</dev> |
| 45 |
<dev role="Member">c1pher</dev> |
| 46 |
<dev role="Member">solar</dev> |
| 47 |
<dev role="Member">tove</dev> |
| 48 |
<dev role="Member">lu_zero</dev> |
| 49 |
<dev role="Member">peper</dev> |
| 50 |
<dev role="Member">idl0r</dev> |
| 51 |
<dev role="Member">hwoarang</dev> |
| 52 |
<dev role="Member">darkside</dev> |
| 53 |
<dev role="Member">ulm</dev> |
| 54 |
|
| 55 |
<!--<subproject ref="/proj/en/qa/something/index.xml"/>--> |
| 56 |
<subproject ref="/proj/en/qa/devmanual.xml"/> |
| 57 |
<subproject ref="/proj/en/qa/pms.xml"/> |
| 58 |
<subproject ref="/proj/en/qa/treecleaners/index.xml"/> |
| 59 |
<subproject ref="/proj/en/qa/bug-wranglers/index.xml"/> |
| 60 |
|
| 61 |
<extraproject name="RepoSuperMan"> |
| 62 |
Repoman is a tool that is used by Gentoo developers to perform pre-commit |
| 63 |
quality checks. It is available as part of <c>portage</c> package. |
| 64 |
Sven has taken the code and updated it to perform better and more thorough |
| 65 |
checks on a tree wide basis. |
| 66 |
</extraproject> |
| 67 |
|
| 68 |
<extrachapter position="bottom"> <!-- I Want to Participate --> |
| 69 |
<title>I Want to Participate</title> |
| 70 |
|
| 71 |
<section> |
| 72 |
<body> |
| 73 |
<p> |
| 74 |
All current and future Gentoo developers should endeavour to be a part of the |
| 75 |
QA project in some fashion. This includes helping to come up with a QA policy, |
| 76 |
as well as doing your part to ensure that your packages meet a certain set of QA |
| 77 |
standards. Additionally, we hope that all Gentoo developers will be co-operative |
| 78 |
in finding and fixing QA issues. Future and prospective developers can contact |
| 79 |
our <uri link="http://www.gentoo.org/proj/en/devrel">recruiters</uri>. |
| 80 |
</p> |
| 81 |
</body> |
| 82 |
</section> |
| 83 |
|
| 84 |
</extrachapter> |
| 85 |
|
| 86 |
<resource link="/proj/en/glep/glep-0048.html"> |
| 87 |
GLEP 48: QA Team's Role and Purpose |
| 88 |
</resource> |
| 89 |
|
| 90 |
<resource link="/proj/en/qa/asneeded.xml"> |
| 91 |
--as-needed introduction and fixing guide |
| 92 |
</resource> |
| 93 |
|
| 94 |
<resource link="/proj/en/qa/automagic.xml"> |
| 95 |
Automagic dependencies, what they are and how to fix them |
| 96 |
</resource> |
| 97 |
|
| 98 |
<resource link="/proj/en/qa/autofailure.xml"> |
| 99 |
How to fix autotools failures |
| 100 |
</resource> |
| 101 |
|
| 102 |
<resource link="/proj/en/qa/backtraces.xml"> |
| 103 |
How to get meaningful backtraces in Gentoo |
| 104 |
</resource> |
| 105 |
|
| 106 |
<resource link="mailto:gentoo-qa@lists.gentoo.org"> |
| 107 |
gentoo-qa mailing lists |
| 108 |
</resource> |
| 109 |
|
| 110 |
<resource link="irc://irc.gentoo.org/#gentoo-qa"> |
| 111 |
#gentoo-qa channel on FreeNode |
| 112 |
</resource> |
| 113 |
|
| 114 |
</project> |
| 115 |
|
| 116 |
<!-- kate: space-indent on; indent-width 2; replace-tabs on; indent-mode normal; --> |
Parent Directory
| 
Revision Log