Examine individual changes

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

Variable	Value
Whether or not the edit is marked as minor (no longer in use) `(minor_edit)`	false
Edit count of the user `(user_editcount)`	64
Name of the user account `(user_name)`	'Soap'
Age of the user account `(user_age)`	123308168
Page ID `(page_id)`	116624
Page namespace `(page_namespace)`	510
Page title (without namespace) `(page_title)`	'Treecleaner'
Full page title `(page_prefixedtitle)`	'Project:Treecleaner'
Action `(action)`	'edit'
Edit summary/reason `(summary)`	'Add myself to Treecleaner project'
Old content model `(old_content_model)`	'wikitext'
New content model `(new_content_model)`	'wikitext'
Old page wikitext, before the edit `(old_wikitext)`	'{{Project \|Name=Treecleaner \|Description=The Tree Cleaning Team is primarily concerned with removing unmaintained and broken packages from the tree. \|Email=treecleaner@gentoo.org \|ParentProject=Project:Quality Assurance \|PropagatesMembers=No \|Members={{Project Member \|Developer=User:Pacho \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:Johu \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:MGorny \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:Bman \|Role=Member \|IsLead=No }} }} Gentoo currently has a number of packages that lack maintainers and are broken in one or more ways. Due to the large number of packages that exhibit this behavior in the gentoo package database the tree cleaner subproject was created. The overall goal of this subproject is to reduce the number of unmaintained and broken packages in the tree. This is accomplished by either finding a maintainer for the package, fixing the package, or removing the package from the package database. We aim to make less work for everyone by reducing the number of broken and unmaintained packages in the tree. We also aim to increase the user experience by removing broken packages from the tree; therefore users have less hair-raising experiences with packages in-tree that just don't work. == Goals == To find and remove broken and unmaintained packages from the tree. == Orphaned packages == Packages that do not have an active maintainer to take care of them are marked as maintainer-needed. This means that they will rot or be removed from the main Gentoo repository unless someone steps up to take care of them. You are free to do it yourself if you feel like it. Gentoo developers and users are encouraged to pick up maintenance for maintainer-needed packages. Users can become maintainers for packages via the [[Project:Proxy_Maintainers]] process. The Treecleaner project maintains [https://qa-reports.gentoo.org/output/maintainer-needed.html a list of orphaned (aka maintainer-needed) packages]. Feel free to grab and maintain one if you want to. === Git history / CVS Attic === All ebuilds, including deleted ones, are available from the web interface to Gentoo's ebuild repository: * all development work done in git (i.e. since 9 Aug 2015) is available at: https://gitweb.gentoo.org/repo/gentoo.git/; * preceding ebuild history (done in CVS) is available at: http://sources.gentoo.org/viewcvs.py/gentoo-x86/; ** alternatively, the git conversion of the CVS history is available at: https://gitweb.gentoo.org/repo/gentoo/historical.git/; however, note that it is imperfect and some parts are missing. If you know the package name, the easiest way to find the past package versions is to look at git log for the specific directory, e.g.: {{Cmd\|git log -- app-foo/bar}} For CVS, the removed files appear in the Attic. They can be accessed by clicking the (Show <n> dead files) link at the top of the folder view. You can then download any ebuilds you may need from gitweb/ViewCVS and place them in a local overlay, where they can be installed as normal. Any distribution files will remain on Gentoo's mirrors for at least two weeks after the ebuild is removed from the tree, and even after removal from our mirrors they will in most cases continue to be available from the original source. === But I love that package! === We are glad you like that package, however without a maintainer it sits stale in the tree. Maintaining a package involves a time commitment, even if your ebuild you submitted to [[Bugzilla]] works, or the patch works, it takes time fixing other bugs, testing the package, checking for updates, and so on. Sometimes there is no one to take this responsibility. If you are confident there are enough users for the package, feel free to contact the [[Project:Proxy_Maintainers]] team for assistance. == Policy == Policies can be found in the [[Project:Treecleaner/Policy\|policy article]]. {{Migrated\|originalauthors=Alec Warner, Charlie Shepherd, Markos Chandras, scarabeus}}'
New page wikitext, after the edit `(new_wikitext)`	'{{Project \|Name=Treecleaner \|Description=The Tree Cleaning Team is primarily concerned with removing unmaintained and broken packages from the tree. \|Email=treecleaner@gentoo.org \|ParentProject=Project:Quality Assurance \|PropagatesMembers=No \|Members={{Project Member \|Developer=User:Pacho \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:Johu \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:MGorny \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:Bman \|Role=Member \|IsLead=No }}{{Project Member \|Developer=User:Soap \|IsLead=No }} }} Gentoo currently has a number of packages that lack maintainers and are broken in one or more ways. Due to the large number of packages that exhibit this behavior in the gentoo package database the tree cleaner subproject was created. The overall goal of this subproject is to reduce the number of unmaintained and broken packages in the tree. This is accomplished by either finding a maintainer for the package, fixing the package, or removing the package from the package database. We aim to make less work for everyone by reducing the number of broken and unmaintained packages in the tree. We also aim to increase the user experience by removing broken packages from the tree; therefore users have less hair-raising experiences with packages in-tree that just don't work. == Goals == To find and remove broken and unmaintained packages from the tree. == Orphaned packages == Packages that do not have an active maintainer to take care of them are marked as maintainer-needed. This means that they will rot or be removed from the main Gentoo repository unless someone steps up to take care of them. You are free to do it yourself if you feel like it. Gentoo developers and users are encouraged to pick up maintenance for maintainer-needed packages. Users can become maintainers for packages via the [[Project:Proxy_Maintainers]] process. The Treecleaner project maintains [https://qa-reports.gentoo.org/output/maintainer-needed.html a list of orphaned (aka maintainer-needed) packages]. Feel free to grab and maintain one if you want to. === Git history / CVS Attic === All ebuilds, including deleted ones, are available from the web interface to Gentoo's ebuild repository: * all development work done in git (i.e. since 9 Aug 2015) is available at: https://gitweb.gentoo.org/repo/gentoo.git/; * preceding ebuild history (done in CVS) is available at: http://sources.gentoo.org/viewcvs.py/gentoo-x86/; ** alternatively, the git conversion of the CVS history is available at: https://gitweb.gentoo.org/repo/gentoo/historical.git/; however, note that it is imperfect and some parts are missing. If you know the package name, the easiest way to find the past package versions is to look at git log for the specific directory, e.g.: {{Cmd\|git log -- app-foo/bar}} For CVS, the removed files appear in the Attic. They can be accessed by clicking the (Show <n> dead files) link at the top of the folder view. You can then download any ebuilds you may need from gitweb/ViewCVS and place them in a local overlay, where they can be installed as normal. Any distribution files will remain on Gentoo's mirrors for at least two weeks after the ebuild is removed from the tree, and even after removal from our mirrors they will in most cases continue to be available from the original source. === But I love that package! === We are glad you like that package, however without a maintainer it sits stale in the tree. Maintaining a package involves a time commitment, even if your ebuild you submitted to [[Bugzilla]] works, or the patch works, it takes time fixing other bugs, testing the package, checking for updates, and so on. Sometimes there is no one to take this responsibility. If you are confident there are enough users for the package, feel free to contact the [[Project:Proxy_Maintainers]] team for assistance. == Policy == Policies can be found in the [[Project:Treecleaner/Policy\|policy article]]. {{Migrated\|originalauthors=Alec Warner, Charlie Shepherd, Markos Chandras, scarabeus}}'
Unified diff of changes made by edit `(edit_diff)`	'@@ -20,4 +20,7 @@ \|Developer=User:Bman \|Role=Member +\|IsLead=No +}}{{Project Member +\|Developer=User:Soap \|IsLead=No }} '
Old page size `(old_size)`	4024
Lines added in edit `(added_lines)`	[ 0 => '\|IsLead=No', 1 => '}}{{Project Member', 2 => '\|Developer=User:Soap' ]
Lines removed in edit `(removed_lines)`	[]
New page text, stripped of any markup `(new_text)`	' Treecleaner Description The Tree Cleaning Team is primarily concerned with removing unmaintained and broken packages from the tree. Project email treecleaner@gentoo.org Lead(s) none No lead election date set Member(s) Aaron Bauman (bman)MemberJohannes Huber (johu)MemberMichał Górny (mgorny)MemberPacho Ramos (Pacho)Member Subproject(s)(and inherited member(s)) (none) Parent Project Quality Assurance Project listing Gentoo currently has a number of packages that lack maintainers and are broken in one or more ways. Due to the large number of packages that exhibit this behavior in the gentoo package database the tree cleaner subproject was created. The overall goal of this subproject is to reduce the number of unmaintained and broken packages in the tree. This is accomplished by either finding a maintainer for the package, fixing the package, or removing the package from the package database. We aim to make less work for everyone by reducing the number of broken and unmaintained packages in the tree. We also aim to increase the user experience by removing broken packages from the tree; therefore users have less hair-raising experiences with packages in-tree that just don't work. Contents 1 Goals 2 Orphaned packages 2.1 Git history / CVS Attic 2.2 But I love that package! 3 Policy Goals[edit] To find and remove broken and unmaintained packages from the tree. Orphaned packages[edit] Packages that do not have an active maintainer to take care of them are marked as maintainer-needed. This means that they will rot or be removed from the main Gentoo repository unless someone steps up to take care of them. You are free to do it yourself if you feel like it. Gentoo developers and users are encouraged to pick up maintenance for maintainer-needed packages. Users can become maintainers for packages via the Project:Proxy_Maintainers process. The Treecleaner project maintains a list of orphaned (aka maintainer-needed) packages. Feel free to grab and maintain one if you want to. Git history / CVS Attic[edit] All ebuilds, including deleted ones, are available from the web interface to Gentoo's ebuild repository: all development work done in git (i.e. since 9 Aug 2015) is available at: https://gitweb.gentoo.org/repo/gentoo.git/; preceding ebuild history (done in CVS) is available at: http://sources.gentoo.org/viewcvs.py/gentoo-x86/; alternatively, the git conversion of the CVS history is available at: https://gitweb.gentoo.org/repo/gentoo/historical.git/; however, note that it is imperfect and some parts are missing. If you know the package name, the easiest way to find the past package versions is to look at git log for the specific directory, e.g.: user $git log -- app-foo/bar For CVS, the removed files appear in the Attic. They can be accessed by clicking the (Show <n> dead files) link at the top of the folder view. You can then download any ebuilds you may need from gitweb/ViewCVS and place them in a local overlay, where they can be installed as normal. Any distribution files will remain on Gentoo's mirrors for at least two weeks after the ebuild is removed from the tree, and even after removal from our mirrors they will in most cases continue to be available from the original source. But I love that package![edit] We are glad you like that package, however without a maintainer it sits stale in the tree. Maintaining a package involves a time commitment, even if your ebuild you submitted to Bugzilla works, or the patch works, it takes time fixing other bugs, testing the package, checking for updates, and so on. Sometimes there is no one to take this responsibility. If you are confident there are enough users for the package, feel free to contact the Project:Proxy_Maintainers team for assistance. Policy[edit] Policies can be found in the policy article. This page is based on a document formerly found on our main website gentoo.org. The following people contributed to the original document: Alec Warner, Charlie Shepherd, Markos Chandras, scarabeusThey are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page. '
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>Treecleaner</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">The Tree Cleaning Team is primarily concerned with removing unmaintained and broken packages from the tree. </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:treecleaner@gentoo.org">treecleaner@gentoo.org</a> </td></tr> <tr valign="top"> <th>Lead(s) </th> <td>none <br />No lead election date set </td></tr> <tr valign="top"> <th>Member(s) </th> <td><ul><li><a href="/wiki/User:Bman" title="User:Bman">Aaron Bauman</a> (bman)<br /><i>Member</i></li><li><a href="/wiki/User:Johu" title="User:Johu">Johannes Huber</a> (johu)<br /><i>Member</i></li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a> (mgorny)<br /><i>Member</i></li><li><a href="/wiki/User:Pacho" title="User:Pacho">Pacho Ramos</a> (Pacho)<br /><i>Member</i></li></ul> </td></tr> <tr valign="top"> <th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small> </th> <td>(none) </td></tr> <tr> <th>Parent Project </th> <td><a href="/wiki/Project:Quality_Assurance" title="Project:Quality Assurance">Quality Assurance</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>Gentoo currently has a number of packages that lack maintainers and are broken in one or more ways. Due to the large number of packages that exhibit this behavior in the gentoo package database the tree cleaner subproject was created. The overall goal of this subproject is to reduce the number of unmaintained and broken packages in the tree. This is accomplished by either finding a maintainer for the package, fixing the package, or removing the package from the package database. </p><p>We aim to make less work for everyone by reducing the number of broken and unmaintained packages in the tree. We also aim to increase the user experience by removing broken packages from the tree; therefore users have less hair-raising experiences with packages in-tree that just don't work. </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="#Orphaned_packages"><span class="tocnumber">2</span> <span class="toctext">Orphaned packages</span></a> <ul> <li class="toclevel-2 tocsection-3"><a href="#Git_history_.2F_CVS_Attic"><span class="tocnumber">2.1</span> <span class="toctext">Git history / CVS Attic</span></a></li> <li class="toclevel-2 tocsection-4"><a href="#But_I_love_that_package.21"><span class="tocnumber">2.2</span> <span class="toctext">But I love that package!</span></a></li> </ul> </li> <li class="toclevel-1 tocsection-5"><a href="#Policy"><span class="tocnumber">3</span> <span class="toctext">Policy</span></a></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:Treecleaner&action=edit&section=1" title="Edit section: Goals">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>To find and remove broken and unmaintained packages from the tree. </p> <h2><span class="mw-headline" id="Orphaned_packages">Orphaned packages</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Treecleaner&action=edit&section=2" title="Edit section: Orphaned packages">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Packages that do not have an active maintainer to take care of them are marked as maintainer-needed. This means that they will rot or be removed from the main Gentoo repository unless someone steps up to take care of them. You are free to do it yourself if you feel like it. Gentoo developers and users are encouraged to pick up maintenance for maintainer-needed packages. Users can become maintainers for packages via the <a href="/wiki/Project:Proxy_Maintainers" title="Project:Proxy Maintainers">Project:Proxy_Maintainers</a> process. </p><p>The Treecleaner project maintains <a rel="nofollow" class="external text" href="https://qa-reports.gentoo.org/output/maintainer-needed.html">a list of orphaned (aka maintainer-needed) packages</a>. Feel free to grab and maintain one if you want to. </p> <h3><span id="Git_history_/_CVS_Attic"></span><span class="mw-headline" id="Git_history_.2F_CVS_Attic">Git history / CVS Attic</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Treecleaner&action=edit&section=3" title="Edit section: Git history / CVS Attic">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>All ebuilds, including deleted ones, are available from the web interface to Gentoo's ebuild repository: </p> <ul><li>all development work done in git (i.e. since 9 Aug 2015) is available at: <a rel="nofollow" class="external free" href="https://gitweb.gentoo.org/repo/gentoo.git/">https://gitweb.gentoo.org/repo/gentoo.git/</a>;</li> <li>preceding ebuild history (done in CVS) is available at: <a rel="nofollow" class="external free" href="http://sources.gentoo.org/viewcvs.py/gentoo-x86/">http://sources.gentoo.org/viewcvs.py/gentoo-x86/</a>; <ul><li>alternatively, the git conversion of the CVS history is available at: <a rel="nofollow" class="external free" href="https://gitweb.gentoo.org/repo/gentoo/historical.git/">https://gitweb.gentoo.org/repo/gentoo/historical.git/</a>; however, note that it is imperfect and some parts are missing.</li></ul></li></ul> <p>If you know the package name, the easiest way to find the past package versions is to look at git log for the specific directory, e.g.: </p> <div class="cmd-box"><div><code style="color: #4E9A06; font-weight: bold;">user $</code><span class="tripleclick-separator"></span><code>git log -- app-foo/bar</code></div></div> <p>For CVS, the removed files appear in the Attic. They can be accessed by clicking the (Show <n> dead files) link at the top of the folder view. </p><p>You can then download any ebuilds you may need from gitweb/ViewCVS and place them in a local overlay, where they can be installed as normal. Any distribution files will remain on Gentoo's mirrors for at least two weeks after the ebuild is removed from the tree, and even after removal from our mirrors they will in most cases continue to be available from the original source. </p> <h3><span id="But_I_love_that_package!"></span><span class="mw-headline" id="But_I_love_that_package.21">But I love that package!</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Treecleaner&action=edit&section=4" title="Edit section: But I love that package!">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>We are glad you like that package, however without a maintainer it sits stale in the tree. Maintaining a package involves a time commitment, even if your ebuild you submitted to <a href="/wiki/Bugzilla" title="Bugzilla">Bugzilla</a> works, or the patch works, it takes time fixing other bugs, testing the package, checking for updates, and so on. Sometimes there is no one to take this responsibility. If you are confident there are enough users for the package, feel free to contact the <a href="/wiki/Project:Proxy_Maintainers" title="Project:Proxy Maintainers">Project:Proxy_Maintainers</a> team for assistance. </p> <h2><span class="mw-headline" id="Policy">Policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Treecleaner&action=edit&section=5" title="Edit section: Policy">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Policies can be found in the <a href="/wiki/Project:Treecleaner/Policy" title="Project:Treecleaner/Policy">policy article</a>. </p><p><br /> </p> <hr /><p><small>This page is based on a document formerly found on our main website <a rel="nofollow" class="external text" href="https://www.gentoo.org/">gentoo.org</a>. <br />The following people contributed to the original document: <b>Alec Warner, Charlie Shepherd, Markos Chandras, scarabeus</b><br /><span style="color: #555;">They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do <b>not</b> add yourself here; your contributions are recorded on each article's associated history page.</span></small> </p> <!-- NewPP limit report Cached time: 20191207220228 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.002 seconds CPU time usage: 0.101 seconds Real time usage: 0.122 seconds Preprocessor visited node count: 411/1000000 Preprocessor generated node count: 2297/1000000 Post‐expand include size: 4289/2097152 bytes Template argument size: 733/2097152 bytes Highest expansion depth: 10/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% 95.682 1 -total 91.89% 87.924 1 Template:Project 36.92% 35.330 4 Template:ProjectMemberLine 16.31% 15.604 4 Template:ProjectMemberLineNickname 12.67% 12.126 5 Template:Project_Member 6.55% 6.268 1 Template:Cmd 4.69% 4.492 1 Template:GenericCmd 1.33% 1.269 1 Template:GenericCmd/Line 1.05% 1.004 1 Template:Migrated --> </div>'
Unix timestamp of change `(timestamp)`	1575756148