/[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.44 - (hide annotations) (download) (as text)
Wed Jan 12 00:36:22 2011 UTC (8 years, 3 months ago) by c1pher
Branch: MAIN
Changes since 1.43: +1 -0 lines
File MIME type: application/xml
Added self to QA project.

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

  ViewVC Help
Powered by ViewVC 1.1.20