| Variable | Value |
|---|
Edit count of the user (user_editcount) | 77 |
Name of the user account (user_name) | 'Arthurzam' |
Age of the user account (user_age) | 83540883 |
Page ID (page_id) | 31899 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Quality Assurance' |
Full page title (page_prefixedtitle) | 'Project:Quality Assurance' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'Add arthurzam, after ACK from soap' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Quality Assurance
|Description=The Gentoo Quality Assurance team
|Email=qa@gentoo.org
|Bug assignment=Yes
|Packages=No
|IRC=#gentoo-qa
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2023-07-23
|Members={{Project Member
|Developer=User:Ulm
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:MGorny
|Role=Deputy Lead
|IsLead=No
}}{{Project Member
|Developer=User:ASturm
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=No
}}
}}
The Gentoo Quality Assurance Project [[Article description::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 ===
* [https://www.gentoo.org/glep/glep-0048.html GLEP 48: QA team's role and purpose]
* {{See also|Project:Quality Assurance/Current projects|text=Current projects}}
=== Communication ===
* [[/Inquiry|When and how do I ask the Quality Assurance team to look into a problem?]]
* [mailto:gentoo-qa@lists.gentoo.org gentoo-qa mailing lists]
* {{IRC|gentoo-qa}} channel on Libera.Chat.
=== Documentation ===
* {{See also|Project:Quality Assurance/As-needed|text=--as-needed introduction and fixing guide}}
* {{See also|Project:Quality Assurance/Handling Libtool Archives|text=Handling Libtool archives in Gentoo}}
* {{See also|Project:Quality Assurance/Automagic dependencies|text=Automagic dependencies, what they are and how to fix them}}
* {{See also|Project:Quality Assurance/Autotools failures|text=How to fix autotools failures}}
* {{See also|Project:Quality Assurance/Backtraces|text=How to get meaningful backtraces in Gentoo}}
* {{See also|Project:Quality Assurance/Subslots|text=How to use subslots and slot operators}}
* {{See also|Project:Quality Assurance/Updating Policy Guide|text=Updating Policy Guide}}
=== Policies and discussion ===
* [https://projects.gentoo.org/qa/policy-guide/ Gentoo Policy Guide]
* {{See also|Project:Quality Assurance/Meeting Agenda|text=Meeting agenda}}
* {{See also|Project:Quality Assurance/Meeting Summaries|text=Meeting summaries}}
* {{See also|Project:Quality Assurance/UID_GID_Assignment|text=UID/GID assignment}}
* {{See also|Project:Quality Assurance/Upstream remote-id types|text=Upstream remote-id types}}
== 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 [[Project:Recruiters| recruiters]]. Ongoing QA projects may be found at [[/Current_projects/]].
=== Joining the team ===
To join the team (as an existing developer), email {{Mail|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.' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Quality Assurance
|Description=The Gentoo Quality Assurance team
|Email=qa@gentoo.org
|Bug assignment=Yes
|Packages=No
|IRC=#gentoo-qa
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|LeadElectionDate=2023-07-23
|Members={{Project Member
|Developer=User:Ulm
|IsLead=No
}}{{Project Member
|Developer=User:Soap
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:MGorny
|Role=Deputy Lead
|IsLead=No
}}{{Project Member
|Developer=User:ASturm
|IsLead=No
}}{{Project Member
|Developer=User:Sam
|IsLead=No
}}{{Project Member
|Developer=User:Arthurzam
|IsLead=No
}}
}}
The Gentoo Quality Assurance Project [[Article description::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 ===
* [https://www.gentoo.org/glep/glep-0048.html GLEP 48: QA team's role and purpose]
* {{See also|Project:Quality Assurance/Current projects|text=Current projects}}
=== Communication ===
* [[/Inquiry|When and how do I ask the Quality Assurance team to look into a problem?]]
* [mailto:gentoo-qa@lists.gentoo.org gentoo-qa mailing lists]
* {{IRC|gentoo-qa}} channel on Libera.Chat.
=== Documentation ===
* {{See also|Project:Quality Assurance/As-needed|text=--as-needed introduction and fixing guide}}
* {{See also|Project:Quality Assurance/Handling Libtool Archives|text=Handling Libtool archives in Gentoo}}
* {{See also|Project:Quality Assurance/Automagic dependencies|text=Automagic dependencies, what they are and how to fix them}}
* {{See also|Project:Quality Assurance/Autotools failures|text=How to fix autotools failures}}
* {{See also|Project:Quality Assurance/Backtraces|text=How to get meaningful backtraces in Gentoo}}
* {{See also|Project:Quality Assurance/Subslots|text=How to use subslots and slot operators}}
* {{See also|Project:Quality Assurance/Updating Policy Guide|text=Updating Policy Guide}}
=== Policies and discussion ===
* [https://projects.gentoo.org/qa/policy-guide/ Gentoo Policy Guide]
* {{See also|Project:Quality Assurance/Meeting Agenda|text=Meeting agenda}}
* {{See also|Project:Quality Assurance/Meeting Summaries|text=Meeting summaries}}
* {{See also|Project:Quality Assurance/UID_GID_Assignment|text=UID/GID assignment}}
* {{See also|Project:Quality Assurance/Upstream remote-id types|text=Upstream remote-id types}}
== 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 [[Project:Recruiters| recruiters]]. Ongoing QA projects may be found at [[/Current_projects/]].
=== Joining the team ===
To join the team (as an existing developer), email {{Mail|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.' |
Unified diff of changes made by edit (edit_diff) | '@@ -25,4 +25,7 @@
}}{{Project Member
|Developer=User:Sam
+|IsLead=No
+}}{{Project Member
+|Developer=User:Arthurzam
|IsLead=No
}}
' |
Old page size (old_size) | 3898 |
Lines added in edit (added_lines) | [
0 => '|IsLead=No',
1 => '}}{{Project Member',
2 => '|Developer=User:Arthurzam'
] |
Lines removed in edit (removed_lines) | [] |
New page text, stripped of any markup (new_text) | '
Quality Assurance
Description
The Gentoo Quality Assurance team
Project email
qa@gentoo.org
IRC channel
#gentoo-qa (webchat)
Bugs
Related bugs
Lead(s)
David Seifert
(soap)Lead Last elected: 2023-07-23
Member(s)
Andreas Sturmlechner
(asturm)Michał Górny
(mgorny)Deputy LeadSam James
(sam)Ulrich Müller
(ulm)
Subproject(s)(and inherited member(s))
Bug Wranglers
Bug cleaners
Devmanual
Package Manager Specification
Treecleaner
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.
Contents
1 Goals
2 Resources
2.1 Role, purpose, and projects
2.2 Communication
2.3 Documentation
2.4 Policies and discussion
3 Participation
3.1 Joining the team
Goals[edit | edit source]
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[edit | edit source]
Resources offered by the QA project are:
Role, purpose, and projects[edit | edit source]
GLEP 48: QA team's role and purpose
Current projects — to list ongoing projects upon which QA members and contributors may work.
Communication[edit | edit source]
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[edit | edit source]
--as-needed introduction and fixing guide — explains how the --as-needed LDFLAG works and provides the steps needed to fix simple cases where --as-needed fails 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[edit | edit source]
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[edit | edit source]
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[edit | edit source]
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.' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Quality Assurance</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">The Gentoo Quality Assurance team
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:qa@gentoo.org">qa@gentoo.org</a>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-qa">#gentoo-qa</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-qa">webchat</a></span>)
</td></tr>
<tr>
<th><span title="The link opens to a bugs.gentoo.org search based on the projects email address.">Bugs</span>
</th>
<td><span class="fa fa-bug fa-fw"></span> <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=PLEASETEST&bug_status=IN_PROGRESS&email1=qa@gentoo.org&emailassigned_to1=1&order=bug_id%20DESC">Related bugs</a>
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td><ul><li><a href="/wiki/User:Soap" title="User:Soap">David Seifert</a>
(soap)<br /><i>Lead</i></li></ul> <br />Last elected: 2023-07-23
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:ASturm" title="User:ASturm">Andreas Sturmlechner</a>
(asturm)</li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a>
(mgorny)<br /><i>Deputy Lead</i></li><li><a href="/wiki/User:Sam" title="User:Sam">Sam James</a>
(sam)</li><li><a href="/wiki/User:Ulm" title="User:Ulm">Ulrich Müller</a>
(ulm)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td><ul><li><a href="/wiki/Project:Bug-wranglers" title="Project:Bug-wranglers">Bug Wranglers</a>
</li><li><a href="/wiki/Project:Bug-cleaners" title="Project:Bug-cleaners">Bug cleaners</a>
</li><li><a href="/wiki/Project:Devmanual" title="Project:Devmanual">Devmanual</a>
</li><li><a href="/wiki/Project:Package_Manager_Specification" title="Project:Package Manager Specification">Package Manager Specification</a>
</li><li><a href="/wiki/Project:Treecleaner" title="Project:Treecleaner">Treecleaner</a>
</li></ul>
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>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.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Goals"><span class="tocnumber">1</span> <span class="toctext">Goals</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#Resources"><span class="tocnumber">2</span> <span class="toctext">Resources</span></a>
<ul>
<li class="toclevel-2 tocsection-3"><a href="#Role.2C_purpose.2C_and_projects"><span class="tocnumber">2.1</span> <span class="toctext">Role, purpose, and projects</span></a></li>
<li class="toclevel-2 tocsection-4"><a href="#Communication"><span class="tocnumber">2.2</span> <span class="toctext">Communication</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#Documentation"><span class="tocnumber">2.3</span> <span class="toctext">Documentation</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#Policies_and_discussion"><span class="tocnumber">2.4</span> <span class="toctext">Policies and discussion</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-7"><a href="#Participation"><span class="tocnumber">3</span> <span class="toctext">Participation</span></a>
<ul>
<li class="toclevel-2 tocsection-8"><a href="#Joining_the_team"><span class="tocnumber">3.1</span> <span class="toctext">Joining the team</span></a></li>
</ul>
</li>
</ul>
</div>
<h2><span class="mw-headline" id="Goals">Goals</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Goals">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=1" title="Edit section: Goals">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li>Keep the tree in a state which benefits all of our users and developers alike.</li>
<li>Create documentation to assist developers.</li>
<li>Work with other teams to overcome deficiencies in tools Gentoo uses to better suit the needs of all developers and users.</li>
<li>Develop QA policies with the interest of improving the quality of Gentoo overall.</li></ul>
<h2><span class="mw-headline" id="Resources">Resources</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: Resources">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=2" title="Edit section: Resources">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Resources offered by the QA project are:
</p>
<h3><span id="Role,_purpose,_and_projects"></span><span class="mw-headline" id="Role.2C_purpose.2C_and_projects">Role, purpose, and projects</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: Role, purpose, and projects">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=3" title="Edit section: Role, purpose, and projects">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a rel="nofollow" class="external text" href="https://www.gentoo.org/glep/glep-0048.html">GLEP 48: QA team's role and purpose</a></li>
<li><a href="/wiki/Project:Quality_Assurance/Current_projects" title="Project:Quality Assurance/Current projects">Current projects</a> — to list ongoing projects upon which QA members and contributors may work.</li></ul>
<h3><span class="mw-headline" id="Communication">Communication</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: Communication">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=4" title="Edit section: Communication">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a href="/wiki/Project:Quality_Assurance/Inquiry" title="Project:Quality Assurance/Inquiry">When and how do I ask the Quality Assurance team to look into a problem?</a></li>
<li><a rel="nofollow" class="external text" href="mailto:gentoo-qa@lists.gentoo.org">gentoo-qa mailing lists</a></li>
<li><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-qa">#gentoo-qa</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-qa">webchat</a></span>) channel on Libera.Chat.</li></ul>
<h3><span class="mw-headline" id="Documentation">Documentation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=5" class="mw-editsection-visualeditor" title="Edit section: Documentation">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=5" title="Edit section: Documentation">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a href="/wiki/Project:Quality_Assurance/As-needed" title="Project:Quality Assurance/As-needed">--as-needed introduction and fixing guide</a> — explains how the <code>--as-needed</code> <var>LDFLAG</var> works and provides the steps needed to fix simple cases where <code>--as-needed</code> fails to build a package.</li>
<li><a href="/wiki/Project:Quality_Assurance/Handling_Libtool_Archives" title="Project:Quality Assurance/Handling Libtool Archives">Handling Libtool archives in Gentoo</a></li>
<li><a href="/wiki/Project:Quality_Assurance/Automagic_dependencies" title="Project:Quality Assurance/Automagic dependencies">Automagic dependencies, what they are and how to fix them</a></li>
<li><a href="/wiki/Project:Quality_Assurance/Autotools_failures" title="Project:Quality Assurance/Autotools failures">How to fix autotools failures</a> — describes the common situations which makes autotools fail to run in an ebuild and gives advice on how to fix the associated issues.</li>
<li><a href="/wiki/Project:Quality_Assurance/Backtraces" title="Project:Quality Assurance/Backtraces">How to get meaningful backtraces in Gentoo</a> — 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.</li>
<li><a href="/wiki/Project:Quality_Assurance/Subslots" title="Project:Quality Assurance/Subslots">How to use subslots and slot operators</a></li>
<li><a href="/wiki/Project:Quality_Assurance/Updating_Policy_Guide" title="Project:Quality Assurance/Updating Policy Guide">Updating Policy Guide</a></li></ul>
<h3><span class="mw-headline" id="Policies_and_discussion">Policies and discussion</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=6" class="mw-editsection-visualeditor" title="Edit section: Policies and discussion">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=6" title="Edit section: Policies and discussion">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<ul><li><a rel="nofollow" class="external text" href="https://projects.gentoo.org/qa/policy-guide/">Gentoo Policy Guide</a></li>
<li><a href="/wiki/Project:Quality_Assurance/Meeting_Agenda" title="Project:Quality Assurance/Meeting Agenda">Meeting agenda</a> — topics to be discussed by the QA team at its next meeting.</li>
<li><a href="/wiki/Project:Quality_Assurance/Meeting_Summaries" title="Project:Quality Assurance/Meeting Summaries">Meeting summaries</a> — summarizes previous QA team meetings.</li>
<li><a href="/wiki/Project:Quality_Assurance/UID_GID_Assignment" title="Project:Quality Assurance/UID GID Assignment">UID/GID assignment</a> — a list of existing fixed UID/GID assignments in Gentoo.</li>
<li><a href="/wiki/Project:Quality_Assurance/Upstream_remote-id_types" title="Project:Quality Assurance/Upstream remote-id types">Upstream remote-id types</a> — a list of remote-id types that can be used in the <code><upstream></code> element in package metadata.</li></ul>
<h2><span class="mw-headline" id="Participation">Participation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=7" class="mw-editsection-visualeditor" title="Edit section: Participation">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=7" title="Edit section: Participation">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>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 <a href="/wiki/Project:Recruiters" title="Project:Recruiters"> recruiters</a>. Ongoing QA projects may be found at <a href="/wiki/Project:Quality_Assurance/Current_projects" title="Project:Quality Assurance/Current projects">Current_projects</a>.
</p>
<h3><span class="mw-headline" id="Joining_the_team">Joining the team</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Quality_Assurance&veaction=edit&section=8" class="mw-editsection-visualeditor" title="Edit section: Joining the team">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:Quality_Assurance&action=edit&section=8" title="Edit section: Joining the team">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>To join the team (as an existing developer), email <a rel="nofollow" class="external text" href="mailto:qa@gentoo.org">qa@gentoo.org</a> or the current team leader with a short summary of what you want to do as a QA team member and your qualifications.
</p>
' |
Unix timestamp of change (timestamp) | 1712508295 |
Wiki