Examine individual changes

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search

This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.

Variables generated for this change

VariableValue
Whether or not the edit is marked as minor (no longer in use) (minor_edit)
false
Edit count of the user (user_editcount)
175
Name of the user account (user_name)
'Zlogene'
Age of the user account (user_age)
245947753
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)
''
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 |IRC=#gentoo-qa |ParentProject=Project:Gentoo |PropagatesMembers=No |LeadElectionDate=2019/06/14 |Members={{Project Member |Developer=User:Ulm |Role=Developer |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Developer |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:Dilfridge |Role=Developer |IsLead=No }} }} The Gentoo Quality Assurance Project aims to keep the portage tree 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] * [[Project:Quality_Assurance/Current_projects|Current projects]] === Communication === * [[Project:Quality Assurance/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 Freenode. === Documentation === * [[Project:Quality Assurance/As-needed|--as-needed introduction and fixing guide]] * [[Project:Quality_Assurance/Handling Libtool Archives|Handling Libtool archives in Gentoo]] * [[Project:Quality Assurance/Automagic dependencies|Automagic dependencies, what they are and how to fix them]] * [[Project:Quality Assurance/Autotools failures|How to fix autotools failures]] * [[Project:Quality Assurance/Backtraces|How to get meaningful backtraces in Gentoo]] * [[Project:Quality Assurance/Subslots|How to use subslots and slot operators]] === Policies and Discussion === * [https://projects.gentoo.org/qa/policy-guide/ Gentoo Policy Guide] * [[Project:Quality_Assurance/Meeting_Agenda|Meeting Agenda]] * [[Project:Quality_Assurance/Meeting_Summaries|Meeting Summaries]] * [[Project:Quality_Assurance/UID_GID_Assignment|UID/GID assignment]] == 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 [[Project:Quality_Assurance/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 |IRC=#gentoo-qa |ParentProject=Project:Gentoo |PropagatesMembers=No |LeadElectionDate=2019/06/14 |Members={{Project Member |Developer=User:Ulm |Role=Developer |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Developer |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:Dilfridge |Role=Developer |IsLead=No }}{{Project Member |Developer=User:ASturm |Role=Developer |IsLead=No }} }} The Gentoo Quality Assurance Project aims to keep the portage tree 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] * [[Project:Quality_Assurance/Current_projects|Current projects]] === Communication === * [[Project:Quality Assurance/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 Freenode. === Documentation === * [[Project:Quality Assurance/As-needed|--as-needed introduction and fixing guide]] * [[Project:Quality_Assurance/Handling Libtool Archives|Handling Libtool archives in Gentoo]] * [[Project:Quality Assurance/Automagic dependencies|Automagic dependencies, what they are and how to fix them]] * [[Project:Quality Assurance/Autotools failures|How to fix autotools failures]] * [[Project:Quality Assurance/Backtraces|How to get meaningful backtraces in Gentoo]] * [[Project:Quality Assurance/Subslots|How to use subslots and slot operators]] === Policies and Discussion === * [https://projects.gentoo.org/qa/policy-guide/ Gentoo Policy Guide] * [[Project:Quality_Assurance/Meeting_Agenda|Meeting Agenda]] * [[Project:Quality_Assurance/Meeting_Summaries|Meeting Summaries]] * [[Project:Quality_Assurance/UID_GID_Assignment|UID/GID assignment]] == 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 [[Project:Quality_Assurance/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,8 @@ }}{{Project Member |Developer=User:Dilfridge +|Role=Developer +|IsLead=No +}}{{Project Member +|Developer=User:ASturm |Role=Developer |IsLead=No '
Old page size (old_size)
3601
Lines added in edit (added_lines)
[ 0 => '|Role=Developer', 1 => '|IsLead=No', 2 => '}}{{Project Member', 3 => '|Developer=User:ASturm' ]
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 Lead(s) David Seifert (soap)Lead Last elected: 2019/06/14 Member(s) Andreas K. Hüttel (dilfridge)DeveloperMichał Górny (mgorny)Deputy LeadUlrich Müller (ulm)DeveloperMikle Kolyada (Zlogene)Developer 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 portage tree 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] 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] Resources offered by the QA project are: Role, purpose and projects[edit] GLEP 48: QA team's role and purpose Current projects Communication[edit] When and how do I ask the Quality Assurance team to look into a problem? gentoo-qa mailing lists #gentoo-qa channel on Freenode. Documentation[edit] --as-needed introduction and fixing guide Handling Libtool archives in Gentoo Automagic dependencies, what they are and how to fix them How to fix autotools failures How to get meaningful backtraces in Gentoo How to use subslots and slot operators Policies and Discussion[edit] Gentoo Policy Guide Meeting Agenda Meeting Summaries UID/GID assignment Participation[edit] 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 Project:Quality_Assurance/Current_projects Joining the Team[edit] 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 a webchat to this project&#39;s Freenode IRC channel.">IRC channel</span> </th> <td><a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-qa">#gentoo-qa</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: 2019/06/14 </td></tr> <tr valign="top"> <th>Member(s) </th> <td><ul><li><a href="/wiki/User:Dilfridge" title="User:Dilfridge">Andreas K. Hüttel</a> (dilfridge)<br /><i>Developer</i></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:Ulm" title="User:Ulm">Ulrich Müller</a> (ulm)<br /><i>Developer</i></li><li><a href="/wiki/User:Zlogene" title="User:Zlogene">Mikle Kolyada</a> (Zlogene)<br /><i>Developer</i></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 portage tree 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"><div class="toctitle" lang="en" dir="ltr"><h2>Contents</h2></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_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&amp;action=edit&amp;section=1" title="Edit section: Goals">edit</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&amp;action=edit&amp;section=2" title="Edit section: Resources">edit</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_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&amp;action=edit&amp;section=3" title="Edit section: Role, purpose and projects">edit</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></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&amp;action=edit&amp;section=4" title="Edit section: Communication">edit</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="irc://irc.gentoo.org/gentoo-qa">#gentoo-qa</a></span> channel on Freenode.</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&amp;action=edit&amp;section=5" title="Edit section: Documentation">edit</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></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></li> <li><a href="/wiki/Project:Quality_Assurance/Backtraces" title="Project:Quality Assurance/Backtraces">How to get meaningful backtraces in Gentoo</a></li> <li><a href="/wiki/Project:Quality_Assurance/Subslots" title="Project:Quality Assurance/Subslots">How to use subslots and slot operators</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&amp;action=edit&amp;section=6" title="Edit section: Policies and Discussion">edit</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></li> <li><a href="/wiki/Project:Quality_Assurance/Meeting_Summaries" title="Project:Quality Assurance/Meeting Summaries">Meeting Summaries</a></li> <li><a href="/wiki/Project:Quality_Assurance/UID_GID_Assignment" title="Project:Quality Assurance/UID GID Assignment">UID/GID assignment</a></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&amp;action=edit&amp;section=7" title="Edit section: Participation">edit</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">Project:Quality_Assurance/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&amp;action=edit&amp;section=8" title="Edit section: Joining the Team">edit</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> <!-- NewPP limit report Cached time: 20200606115131 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.007 seconds CPU time usage: 0.133 seconds Real time usage: 0.178 seconds Preprocessor visited node count: 508/1000000 Preprocessor generated node count: 1921/1000000 Post‐expand include size: 4126/2097152 bytes Template argument size: 958/2097152 bytes Highest expansion depth: 7/40 Expensive parser function count: 0/100 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 0/5000000 bytes --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 144.261 1 -total 93.92% 135.491 1 Template:Project 28.21% 40.700 5 Template:ProjectMemberLine 15.68% 22.622 5 Template:SubprojectLine 12.11% 17.467 5 Template:ProjectMemberLineNickname 9.09% 13.117 6 Template:Project_Member 5.10% 7.364 1 Template:Mail 4.34% 6.262 1 Template:DevName 0.66% 0.958 1 Template:IRC --> </div>'
Unix timestamp of change (timestamp)
1591444291