/[gentoo]/xml/htdocs/proj/en/qa/index.xml
Gentoo

Contents of /xml/htdocs/proj/en/qa/index.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.46 - (hide annotations) (download) (as text)
Thu Jan 20 10:47:01 2011 UTC (8 years, 3 months ago) by halcy0n
Branch: MAIN
Changes since 1.45: +0 -1 lines
File MIME type: application/xml
Removing myself

1 seemant 1.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 flameeyes 1.3 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 seemant 1.1 </description>
16    
17 neysx 1.24 <longdescription><p>
18 halcy0n 1.13 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 neysx 1.24 </p></longdescription>
24 seemant 1.1
25     <goals>
26 halcy0n 1.13 <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 seemant 1.1 </goals>
42    
43 halcy0n 1.29
44 flameeyes 1.43 <dev role="Lead">flameeyes</dev>
45 halcy0n 1.5 <dev role="Member" description="autorepoman">swegener</dev>
46 halcy0n 1.8 <dev role="Member">solar</dev>
47 tove 1.9 <dev role="Member">tove</dev>
48 lu_zero 1.40 <dev role="Member">lu_zero</dev>
49 halcy0n 1.10 <dev role="Member" description="Support Personnel">vapier</dev>
50 peper 1.23 <dev role="Member">peper</dev>
51 scarabeus 1.35 <dev role="Member">scarabeus</dev>
52 halcy0n 1.36 <dev role="Member">idl0r</dev>
53 halcy0n 1.38 <dev role="Member">hwoarang</dev>
54 halcy0n 1.39 <dev role="Member">ssuominen</dev>
55     <dev role="Member">darkside</dev>
56 seemant 1.1
57 antarus 1.16 <!--<subproject ref="/proj/en/qa/something/index.xml"/>-->
58 halcy0n 1.15 <subproject ref="/proj/en/qa/devmanual.xml"/>
59 spb 1.21 <subproject ref="/proj/en/qa/pms.xml"/>
60 antarus 1.16 <subproject ref="/proj/en/qa/treecleaners/index.xml"/>
61 halcy0n 1.32 <subproject ref="/proj/en/qa/bug-wranglers/index.xml"/>
62 antarus 1.16
63 seemant 1.1 <extraproject name="RepoSuperMan">
64 flameeyes 1.3 Repoman is a tool that is used by Gentoo developers to perform pre-commit
65     quality checks. It is available as part of <c>portage</c> package.
66 halcy0n 1.6 Sven has taken the code and updated it to perform better and more thorough
67 flameeyes 1.3 checks on a tree wide basis.
68 seemant 1.1 </extraproject>
69    
70 flameeyes 1.3 <extrachapter position="bottom"> <!-- I Want to Participate -->
71 seemant 1.1 <title>I Want to Participate</title>
72 flameeyes 1.3
73 seemant 1.1 <section>
74     <body>
75 flameeyes 1.3 <p>
76     All current and future Gentoo developers should endeavour to be a part of the
77     QA project in some fashion. This includes helping to come up with a QA policy,
78     as well as doing your part to ensure that your packages meet a certain set of QA
79     standards. Additionally, we hope that all Gentoo developers will be co-operative
80     in finding and fixing QA issues. Future and prospective developers can contact
81     our <uri link="http://www.gentoo.org/proj/en/devrel">recruiters</uri>.
82 seemant 1.1 </p>
83     </body>
84     </section>
85 flameeyes 1.3
86 seemant 1.1 </extrachapter>
87    
88 halcy0n 1.14 <resource link="/proj/en/glep/glep-0048.html">
89     GLEP 48: QA Team's Role and Purpose
90     </resource>
91    
92 flameeyes 1.2 <resource link="/proj/en/qa/asneeded.xml">
93     --as-needed introduction and fixing guide
94     </resource>
95 flameeyes 1.4
96 flameeyes 1.2 <resource link="/proj/en/qa/automagic.xml">
97     Automagic dependencies, what they are and how to fix them
98     </resource>
99    
100 flameeyes 1.4 <resource link="/proj/en/qa/autofailure.xml">
101     How to fix autotools failures
102     </resource>
103    
104 flameeyes 1.12 <resource link="/proj/en/qa/backtraces.xml">
105     How to get meaningful backtraces in Gentoo
106     </resource>
107    
108 darkside 1.42 <resource link="mailto:gentoo-qa@lists.gentoo.org">
109     gentoo-qa mailing lists
110     </resource>
111    
112     <resource link="irc://irc.gentoo.org/#gentoo-qa">
113     #gentoo-qa channel on FreeNode
114     </resource>
115    
116 seemant 1.1 </project>
117 flameeyes 1.3
118     <!-- kate: space-indent on; indent-width 2; replace-tabs on; indent-mode normal; -->

  ViewVC Help
Powered by ViewVC 1.1.20