Abuse filter log

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search
Details for log entry 2,718

18:01, 9 July 2020: Sam (talk | contribs) triggered filter 13, performing the action "edit" on Project:ARM. Actions taken: Tag; Filter description: New Project Member (examine)

Changes made in edit

 
|Developer=User:Nerdboy
 
|Developer=User:Nerdboy
 
|Role=Member (Gentoo/ARM Kernel)
 
|Role=Member (Gentoo/ARM Kernel)
 +
|IsLead=No
 +
}}{{Project Member
 +
|Developer=User:Sam
 +
|Role=Gentoo/ARM
 
|IsLead=No
 
|IsLead=No
 
}}
 
}}

Action parameters

VariableValue
Whether or not the edit is marked as minor (no longer in use) (minor_edit)
false
Edit count of the user (user_editcount)
106
Name of the user account (user_name)
'Sam'
Age of the user account (user_age)
92793983
Page ID (page_id)
62124
Page namespace (page_namespace)
510
Page title (without namespace) (page_title)
'ARM'
Full page title (page_prefixedtitle)
'Project:ARM'
Action (action)
'edit'
Edit summary/reason (summary)
'Join the project, acked by member'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Project |Name=ARM Development |Description=The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture. |Email=arm@gentoo.org |IRC=#gentoo-arm |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Zero Chaos |Role=Lead (Gentoo/ARM) |IsLead=Yes }}{{Project Member |Developer=User:Ago |Role=Member (Security bugs primarily) |IsLead=No }}{{Project Member |Developer=User:Blueness |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Dilfridge |Role=inactive (no hardware) |IsLead=No }}{{Project Member |Developer=User:Dlan |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Maekke |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Vapier |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Alicef |Role=Member (Gentoo/ARM Kernel) |IsLead=No }}{{Project Member |Developer=User:Nerdboy |Role=Member (Gentoo/ARM Kernel) |IsLead=No }} }} The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata. Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] and correspondence is maintained on the various ARM related mailinglists. ({{IRC|gentoo-arm}} and those belonging to the sub-projects). __TOC__ == Goals == The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants: Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs. === Stabilization policy === As the Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7), the minimum requirements to mark a package stable for ARM are: * Successful compilation on all supported 32-bit ARM architectures (Use <code>CFLAGS="-march=$arch"</code> here if you don't have the required devices) * Runtime test on at least one of the supported 32-bit ARM architectures Please take additional care on packages that are not marked stable for ARM yet, as keywording only requires a test on at least one ARM architecture. * vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization * hardened-sources should be stablilized per the Hardened Project's whims since no official policy exists at this time https://wiki.gentoo.org/wiki/Project:Hardened == How to participate == Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through [http://bugs.gentoo.org bugs.gentoo.org]. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on [http://bugs.gentoo.org bugs.gentoo.org], and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in {{IRC|gentoo-arm}}. Finally, feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] on the wiki. It's always nice to know what gadgets are out there!'
New page wikitext, after the edit (new_wikitext)
'{{Project |Name=ARM Development |Description=The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture. |Email=arm@gentoo.org |IRC=#gentoo-arm |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Zero Chaos |Role=Lead (Gentoo/ARM) |IsLead=Yes }}{{Project Member |Developer=User:Ago |Role=Member (Security bugs primarily) |IsLead=No }}{{Project Member |Developer=User:Blueness |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Dilfridge |Role=inactive (no hardware) |IsLead=No }}{{Project Member |Developer=User:Dlan |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Maekke |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Vapier |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Member (Gentoo/ARM) |IsLead=No }}{{Project Member |Developer=User:Alicef |Role=Member (Gentoo/ARM Kernel) |IsLead=No }}{{Project Member |Developer=User:Nerdboy |Role=Member (Gentoo/ARM Kernel) |IsLead=No }}{{Project Member |Developer=User:Sam |Role=Gentoo/ARM |IsLead=No }} }} The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata. Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] and correspondence is maintained on the various ARM related mailinglists. ({{IRC|gentoo-arm}} and those belonging to the sub-projects). __TOC__ == Goals == The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants: Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs. === Stabilization policy === As the Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7), the minimum requirements to mark a package stable for ARM are: * Successful compilation on all supported 32-bit ARM architectures (Use <code>CFLAGS="-march=$arch"</code> here if you don't have the required devices) * Runtime test on at least one of the supported 32-bit ARM architectures Please take additional care on packages that are not marked stable for ARM yet, as keywording only requires a test on at least one ARM architecture. * vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization * hardened-sources should be stablilized per the Hardened Project's whims since no official policy exists at this time https://wiki.gentoo.org/wiki/Project:Hardened == How to participate == Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through [http://bugs.gentoo.org bugs.gentoo.org]. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on [http://bugs.gentoo.org bugs.gentoo.org], and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in {{IRC|gentoo-arm}}. Finally, feel free to add yourself with your IRC handle to our [[Embedded systems/ARM hardware list|ARM hardware list]] on the wiki. It's always nice to know what gadgets are out there!'
Unified diff of changes made by edit (edit_diff)
'@@ -45,4 +45,8 @@ |Developer=User:Nerdboy |Role=Member (Gentoo/ARM Kernel) +|IsLead=No +}}{{Project Member +|Developer=User:Sam +|Role=Gentoo/ARM |IsLead=No }} '
Old page size (old_size)
4480
Lines added in edit (added_lines)
[ 0 => '|IsLead=No', 1 => '}}{{Project Member', 2 => '|Developer=User:Sam', 3 => '|Role=Gentoo/ARM' ]
Lines removed in edit (removed_lines)
[]
New page text, stripped of any markup (new_text)
' ARM Development Description The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture. Project email arm@gentoo.org IRC channel #gentoo-arm Lead(s) Rick Farina (zerochaos)Lead (Gentoo/ARM) No lead election date set Member(s) Agostino Sarubbo (ago)Member (Security bugs primarily)Alice Ferrazzi (alicef)Member (Gentoo/ARM Kernel)Anthony G. Basile (blueness)Member (Gentoo/ARM)Andreas K. Hüttel (dilfridge)inactive (no hardware)Yixun Lan, Lan Yixun (dlan)Member (Gentoo/ARM)Markus Meier (maekke)Member (Gentoo/ARM)Steve Arnold (nerdboy)Member (Gentoo/ARM Kernel)Mike Frysinger (vapier)Member (Gentoo/ARM)Mikle Kolyada (Zlogene)Member (Gentoo/ARM) Subproject(s)(and inherited member(s)) (none) Parent Project Base System Project listing The Gentoo/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata. Bugs are tracked and resolved from the Gentoo bug tracker and correspondence is maintained on the various ARM related mailinglists. (#gentoo-arm and those belonging to the sub-projects). Contents 1 Goals 1.1 Stabilization policy 2 How to participate Goals[edit] The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants: Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs. Stabilization policy[edit] As the Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7), the minimum requirements to mark a package stable for ARM are: Successful compilation on all supported 32-bit ARM architectures (Use CFLAGS="-march=$arch" here if you don't have the required devices) Runtime test on at least one of the supported 32-bit ARM architectures Please take additional care on packages that are not marked stable for ARM yet, as keywording only requires a test on at least one ARM architecture. vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization hardened-sources should be stablilized per the Hardened Project's whims since no official policy exists at this time https://wiki.gentoo.org/wiki/Project:Hardened How to participate[edit] Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through bugs.gentoo.org. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on bugs.gentoo.org, and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in #gentoo-arm. Finally, feel free to add yourself with your IRC handle to our ARM hardware list on the wiki. It's always nice to know what gadgets are out there! '
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>ARM Development</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">The ARM Development Project is devoted to keeping Gentoo in good shape on the ARM architecture. </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:arm@gentoo.org">arm@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-arm">#gentoo-arm</a> </td></tr> <tr valign="top"> <th>Lead(s) </th> <td><ul><li><a href="/wiki/User:Zero_Chaos" title="User:Zero Chaos">Rick Farina</a> (zerochaos)<br /><i>Lead (Gentoo/ARM)</i></li></ul> <br />No lead election date set </td></tr> <tr valign="top"> <th>Member(s) </th> <td><ul><li><a href="/wiki/User:Ago" title="User:Ago">Agostino Sarubbo</a> (ago)<br /><i>Member (Security bugs primarily)</i></li><li><a href="/wiki/User:Alicef" title="User:Alicef">Alice Ferrazzi</a> (alicef)<br /><i>Member (Gentoo/ARM Kernel)</i></li><li><a href="/wiki/User:Blueness" title="User:Blueness">Anthony G. Basile</a> (blueness)<br /><i>Member (Gentoo/ARM)</i></li><li><a href="/wiki/User:Dilfridge" title="User:Dilfridge">Andreas K. Hüttel</a> (dilfridge)<br /><i>inactive (no hardware)</i></li><li><a href="/wiki/User:Dlan" title="User:Dlan">Yixun Lan, Lan Yixun</a> (dlan)<br /><i>Member (Gentoo/ARM)</i></li><li><a href="/wiki/User:Maekke" title="User:Maekke">Markus Meier</a> (maekke)<br /><i>Member (Gentoo/ARM)</i></li><li><a href="/wiki/User:Nerdboy" title="User:Nerdboy">Steve Arnold</a> (nerdboy)<br /><i>Member (Gentoo/ARM Kernel)</i></li><li><a href="/wiki/User:Vapier" title="User:Vapier">Mike Frysinger</a> (vapier)<br /><i>Member (Gentoo/ARM)</i></li><li><a href="/wiki/User:Zlogene" title="User:Zlogene">Mikle Kolyada</a> (Zlogene)<br /><i>Member (Gentoo/ARM)</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:Base" title="Project:Base">Base System</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/ARM Project works to keep Gentoo the most up to date and fastest ARM distribution available. We are responsible for the maintenance of all ARM specific metadata and the testing of all other non ARM specific meta-data on the ARM architecture to ensure portability. Portability implies reusable metadata. </p><p>Bugs are tracked and resolved from the <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">Gentoo bug tracker</a> and correspondence is maintained on the various ARM related mailinglists. (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="irc://irc.gentoo.org/gentoo-arm">#gentoo-arm</a></span> and those belonging to the sub-projects). </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> <ul> <li class="toclevel-2 tocsection-2"><a href="#Stabilization_policy"><span class="tocnumber">1.1</span> <span class="toctext">Stabilization policy</span></a></li> </ul> </li> <li class="toclevel-1 tocsection-3"><a href="#How_to_participate"><span class="tocnumber">2</span> <span class="toctext">How to participate</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:ARM&amp;action=edit&amp;section=1" title="Edit section: Goals">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>The goal of the Gentoo ARM development project is to guarantee that the ARM packages build using Gentoo metadata are up to date. By continuously enhancing the metadata, we provide the ARM user with the Gentoo community feeling, performance, freedom and up-to-dateness. The meta-distribution notion allows for a user to to be as bleeding edge as he/she wants: </p><p>Gentoo is unique because of its interpretation of the Meta-Distribution notion: all architectures share the same 'generic' metadata (information about how to build packages - how to build a distribution). The ARM developers are responsible for building and testing packages using this meta-data. The meta-data gets marked 'tested' or 'stable' afterwards, depending on the building and testing experience. Our users can use (but don't have to use) this information to build a system that suits their needs. </p> <h3><span class="mw-headline" id="Stabilization_policy">Stabilization policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&amp;action=edit&amp;section=2" title="Edit section: Stabilization policy">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>As the Gentoo ARM development project supports various flavors of the 32-bit ARM architecture (to be precise: armv4/armv5/armv6/armv7), the minimum requirements to mark a package stable for ARM are: </p> <ul><li>Successful compilation on all supported 32-bit ARM architectures (Use <code>CFLAGS="-march=$arch"</code> here if you don't have the required devices)</li> <li>Runtime test on at least one of the supported 32-bit ARM architectures</li></ul> <p>Please take additional care on packages that are not marked stable for ARM yet, as keywording only requires a test on at least one ARM architecture. </p> <ul><li>vanilla-sources and gentoo-sources should be stabilized per the Kernel Project stabilization policy <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization">https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization</a></li></ul> <ul><li>hardened-sources should be stablilized per the Hardened Project's whims since no official policy exists at this time <a rel="nofollow" class="external free" href="https://wiki.gentoo.org/wiki/Project:Hardened">https://wiki.gentoo.org/wiki/Project:Hardened</a></li></ul> <h2><span class="mw-headline" id="How_to_participate">How to participate</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:ARM&amp;action=edit&amp;section=3" title="Edit section: How to participate">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Can you make computers do amazing things? Are you excited about exploring areas of computing never explored before? We are continuously looking for volunteers willing to spend some of their free time on this project. In return for your work, you get the respect of the ARM community. </p><p>If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">bugs.gentoo.org</a>. There are many many bugs waiting to be found and fixed and many enhancements looking to find someone to code them. Figure out a fix, implement it, test it, and then keep trying to make the patch smaller. Post it for review on <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">bugs.gentoo.org</a>, and keep working on it. If it seems ignored, make a new comment in the bug and/or mention it in <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="irc://irc.gentoo.org/gentoo-arm">#gentoo-arm</a></span>. </p><p>Finally, feel free to add yourself with your IRC handle to our <a href="/wiki/Embedded_systems/ARM_hardware_list" title="Embedded systems/ARM hardware list">ARM hardware list</a> on the wiki. It's always nice to know what gadgets are out there! </p> <!-- NewPP limit report Cached time: 20200709180147 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.005 seconds CPU time usage: 0.150 seconds Real time usage: 0.191 seconds Preprocessor visited node count: 611/1000000 Preprocessor generated node count: 1913/1000000 Post‐expand include size: 5210/2097152 bytes Template argument size: 1523/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% 161.983 1 -total 98.82% 160.067 1 Template:Project 49.79% 80.650 10 Template:ProjectMemberLine 21.28% 34.476 10 Template:ProjectMemberLineNickname 13.20% 21.374 11 Template:Project_Member 0.95% 1.545 2 Template:IRC --> </div>'
Unix timestamp of change (timestamp)
1594317706