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,754

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

Changes made in edit

 
|Developer=User:MGorny
 
|Developer=User:MGorny
 
|Role=Python keywordreqs (on bogsucker/timberdoodle)
 
|Role=Python keywordreqs (on bogsucker/timberdoodle)
 +
|IsLead=No
 +
}}{{Project Member
 +
|Developer=User:Sam
 +
|Role=ppc/ppc64 keywording/stabilisation
 
|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)
119
Name of the user account (user_name)
'Sam'
Age of the user account (user_age)
94188179
Page ID (page_id)
105792
Page namespace (page_namespace)
510
Page title (without namespace) (page_title)
'PowerPC'
Full page title (page_prefixedtitle)
'Project:PowerPC'
Action (action)
'edit'
Edit summary/reason (summary)
'Join 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=PowerPC Development |Description=The PowerPC Development Project is devoted to keeping Gentoo in good shape on both 32-bit and 64-bit PowerPC architecture. |Email=ppc@gentoo.org |IRC=#gentoo-powerpc |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Blueness |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Ago |Role=ppc/ppc64 stabilization/security |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Mattst88 |IsLead=No }}{{Project Member |Developer=User:Lu zero |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Vapier |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Slyfox |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:JeR |Role=packages |IsLead=No }}{{Project Member |Developer=User:GYakovlev |Role=ppc64 keywording, talos II packages |IsLead=No }}{{Project Member |Developer=User:MGorny |Role=Python keywordreqs (on bogsucker/timberdoodle) |IsLead=No }} }} The Gentoo/PowerPC Project works to ensure that Gentoo is the most up to date and robust PowerPC distribution available for both server and desktop applications. Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] . For PowerPC bugs, please see this [https://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=ppc%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= link] . Correspondence is maintained on the PowerPC related mailing lists, gentoo-ppc-user and gentoo-ppc-dev. For more information on PowerPC mailing lists, please see [http://www.gentoo.org/main/en/lists.xml the Gentoo Mailing list overview] . Additionally, the PowerPC team is almost always available in #gentoo-powerpc on [http://freenode.net freenode]. == Goals == The goal of the Gentoo PowerPC development project is to guarantee that the PowerPC packages built using Gentoo meta-data (ebuilds) are functional and up to date. By continuously testing new packages, maintaining existing packages and providing user support, the Gentoo PowerPC team provides the PowerPC user with a modern distro based on community, performance and freedom. Utilizing Gentoo's meta-data based distribution allows a user to to be as bleeding edge or as conservative as is desired. Gentoo is unique because all of its supported architectures share the same generic meta-data information (ebuilds) which describe how to build packages. These packages are combined to form the foundation of this distribution. The PowerPC developers are responsible for building and testing ebuilds and marking them as tested ({{Keyword|~ppc}}/{{Keyword|~ppc64}}) or stable ({{Keyword|ppc}}/{{Keyword|ppc64}}). Our users can use this information, along with the Portage application, to build a system that suits their needs, whether it is a stable server, embedded system or a bleeding edge desktop system. == Participation == 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. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through our [https://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=ppc%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bugs] . There are always packages that need to be tested, bugs waiting to be found and fixed and enhancements waiting for someone to code them. Feel free to ask the PPC development team on IRC what ''you'' can help us with! For more information on how the PPC team recruits please read our [http://www.gentoo.org/recruitment.xml recruitment] page. == See also == * {{See also|PPC}}'
New page wikitext, after the edit (new_wikitext)
'{{Project |Name=PowerPC Development |Description=The PowerPC Development Project is devoted to keeping Gentoo in good shape on both 32-bit and 64-bit PowerPC architecture. |Email=ppc@gentoo.org |IRC=#gentoo-powerpc |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Blueness |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Ago |Role=ppc/ppc64 stabilization/security |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Mattst88 |IsLead=No }}{{Project Member |Developer=User:Lu zero |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Vapier |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:Slyfox |Role=ppc/ppc64 keywording/stabilization |IsLead=No }}{{Project Member |Developer=User:JeR |Role=packages |IsLead=No }}{{Project Member |Developer=User:GYakovlev |Role=ppc64 keywording, talos II packages |IsLead=No }}{{Project Member |Developer=User:MGorny |Role=Python keywordreqs (on bogsucker/timberdoodle) |IsLead=No }}{{Project Member |Developer=User:Sam |Role=ppc/ppc64 keywording/stabilisation |IsLead=No }} }} The Gentoo/PowerPC Project works to ensure that Gentoo is the most up to date and robust PowerPC distribution available for both server and desktop applications. Bugs are tracked and resolved from the [http://bugs.gentoo.org Gentoo bug tracker] . For PowerPC bugs, please see this [https://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=ppc%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= link] . Correspondence is maintained on the PowerPC related mailing lists, gentoo-ppc-user and gentoo-ppc-dev. For more information on PowerPC mailing lists, please see [http://www.gentoo.org/main/en/lists.xml the Gentoo Mailing list overview] . Additionally, the PowerPC team is almost always available in #gentoo-powerpc on [http://freenode.net freenode]. == Goals == The goal of the Gentoo PowerPC development project is to guarantee that the PowerPC packages built using Gentoo meta-data (ebuilds) are functional and up to date. By continuously testing new packages, maintaining existing packages and providing user support, the Gentoo PowerPC team provides the PowerPC user with a modern distro based on community, performance and freedom. Utilizing Gentoo's meta-data based distribution allows a user to to be as bleeding edge or as conservative as is desired. Gentoo is unique because all of its supported architectures share the same generic meta-data information (ebuilds) which describe how to build packages. These packages are combined to form the foundation of this distribution. The PowerPC developers are responsible for building and testing ebuilds and marking them as tested ({{Keyword|~ppc}}/{{Keyword|~ppc64}}) or stable ({{Keyword|ppc}}/{{Keyword|ppc64}}). Our users can use this information, along with the Portage application, to build a system that suits their needs, whether it is a stable server, embedded system or a bleeding edge desktop system. == Participation == 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. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through our [https://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=exact&email1=ppc%40gentoo.org&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bugs] . There are always packages that need to be tested, bugs waiting to be found and fixed and enhancements waiting for someone to code them. Feel free to ask the PPC development team on IRC what ''you'' can help us with! For more information on how the PPC team recruits please read our [http://www.gentoo.org/recruitment.xml recruitment] page. == See also == * {{See also|PPC}}'
Unified diff of changes made by edit (edit_diff)
'@@ -44,4 +44,8 @@ |Developer=User:MGorny |Role=Python keywordreqs (on bogsucker/timberdoodle) +|IsLead=No +}}{{Project Member +|Developer=User:Sam +|Role=ppc/ppc64 keywording/stabilisation |IsLead=No }} '
Old page size (old_size)
4873
Lines added in edit (added_lines)
[ 0 => '|IsLead=No', 1 => '}}{{Project Member', 2 => '|Developer=User:Sam', 3 => '|Role=ppc/ppc64 keywording/stabilisation' ]
Lines removed in edit (removed_lines)
[]
New page text, stripped of any markup (new_text)
' PowerPC Development Description The PowerPC Development Project is devoted to keeping Gentoo in good shape on both 32-bit and 64-bit PowerPC architecture. Project email ppc@gentoo.org IRC channel #gentoo-powerpc Lead(s) none No lead election date set Member(s) Agostino Sarubbo (ago)ppc/ppc64 stabilization/securityAnthony G. Basile (blueness)ppc/ppc64 keywording/stabilizationGeorgy Yakovlev (gyakovlev)ppc64 keywording, talos II packagesJeroen Roovers (jer)packagesLuca Barbato (lu_zero)ppc/ppc64 keywording/stabilizationMichał Górny (mgorny)Python keywordreqs (on bogsucker/timberdoodle)Matt Turner (mattst88)Sergei Trofimovich (slyfox)ppc/ppc64 keywording/stabilizationMike Frysinger (vapier)ppc/ppc64 keywording/stabilizationMikle Kolyada (Zlogene)ppc/ppc64 keywording/stabilization Subproject(s)(and inherited member(s)) (none) Parent Project Base System Project listing The Gentoo/PowerPC Project works to ensure that Gentoo is the most up to date and robust PowerPC distribution available for both server and desktop applications. Bugs are tracked and resolved from the Gentoo bug tracker . For PowerPC bugs, please see this link . Correspondence is maintained on the PowerPC related mailing lists, gentoo-ppc-user and gentoo-ppc-dev. For more information on PowerPC mailing lists, please see the Gentoo Mailing list overview . Additionally, the PowerPC team is almost always available in #gentoo-powerpc on freenode. Goals[edit] The goal of the Gentoo PowerPC development project is to guarantee that the PowerPC packages built using Gentoo meta-data (ebuilds) are functional and up to date. By continuously testing new packages, maintaining existing packages and providing user support, the Gentoo PowerPC team provides the PowerPC user with a modern distro based on community, performance and freedom. Utilizing Gentoo's meta-data based distribution allows a user to to be as bleeding edge or as conservative as is desired. Gentoo is unique because all of its supported architectures share the same generic meta-data information (ebuilds) which describe how to build packages. These packages are combined to form the foundation of this distribution. The PowerPC developers are responsible for building and testing ebuilds and marking them as tested (~ppc/~ppc64) or stable (ppc/ppc64). Our users can use this information, along with the Portage application, to build a system that suits their needs, whether it is a stable server, embedded system or a bleeding edge desktop system. Participation[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. If you are interested in helping, but don't have a niche that you are interested in filling, you can always look through our bugs . There are always packages that need to be tested, bugs waiting to be found and fixed and enhancements waiting for someone to code them. Feel free to ask the PPC development team on IRC what you can help us with! For more information on how the PPC team recruits please read our recruitment page. See also[edit] PPC — a landing page for those interested in the ppc and ppc64 architectures. '
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>PowerPC Development</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">The PowerPC Development Project is devoted to keeping Gentoo in good shape on both 32-bit and 64-bit PowerPC 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:ppc@gentoo.org">ppc@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-powerpc">#gentoo-powerpc</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:Ago" title="User:Ago">Agostino Sarubbo</a> (ago)<br /><i>ppc/ppc64 stabilization/security</i></li><li><a href="/wiki/User:Blueness" title="User:Blueness">Anthony G. Basile</a> (blueness)<br /><i>ppc/ppc64 keywording/stabilization</i></li><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a> (gyakovlev)<br /><i>ppc64 keywording, talos II packages</i></li><li><a href="/wiki/User:JeR" title="User:JeR">Jeroen Roovers</a> (jer)<br /><i>packages</i></li><li><a href="/wiki/User:Lu_zero" title="User:Lu zero">Luca Barbato</a> (lu_zero)<br /><i>ppc/ppc64 keywording/stabilization</i></li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a> (mgorny)<br /><i>Python keywordreqs (on bogsucker/timberdoodle)</i></li><li><a href="/wiki/User:Mattst88" title="User:Mattst88">Matt Turner</a> (mattst88)</li><li><a href="/wiki/User:Slyfox" title="User:Slyfox">Sergei Trofimovich</a> (slyfox)<br /><i>ppc/ppc64 keywording/stabilization</i></li><li><a href="/wiki/User:Vapier" title="User:Vapier">Mike Frysinger</a> (vapier)<br /><i>ppc/ppc64 keywording/stabilization</i></li><li><a href="/wiki/User:Zlogene" title="User:Zlogene">Mikle Kolyada</a> (Zlogene)<br /><i>ppc/ppc64 keywording/stabilization</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/PowerPC Project works to ensure that Gentoo is the most up to date and robust PowerPC distribution available for both server and desktop applications. </p><p>Bugs are tracked and resolved from the <a rel="nofollow" class="external text" href="http://bugs.gentoo.org">Gentoo bug tracker</a> . For PowerPC bugs, please see this <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?query_format=&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;long_desc_type=substring&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailassigned_to1=1&amp;emailtype1=exact&amp;email1=ppc%40gentoo.org&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailqa_contact2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">link</a> . Correspondence is maintained on the PowerPC related mailing lists, gentoo-ppc-user and gentoo-ppc-dev. For more information on PowerPC mailing lists, please see <a rel="nofollow" class="external text" href="http://www.gentoo.org/main/en/lists.xml">the Gentoo Mailing list overview</a> . Additionally, the PowerPC team is almost always available in #gentoo-powerpc on <a rel="nofollow" class="external text" href="http://freenode.net">freenode</a>. </p> <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:PowerPC&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 PowerPC development project is to guarantee that the PowerPC packages built using Gentoo meta-data (ebuilds) are functional and up to date. By continuously testing new packages, maintaining existing packages and providing user support, the Gentoo PowerPC team provides the PowerPC user with a modern distro based on community, performance and freedom. Utilizing Gentoo's meta-data based distribution allows a user to to be as bleeding edge or as conservative as is desired. </p><p>Gentoo is unique because all of its supported architectures share the same generic meta-data information (ebuilds) which describe how to build packages. These packages are combined to form the foundation of this distribution. The PowerPC developers are responsible for building and testing ebuilds and marking them as tested (<b><span style="font-family: monospace; font-size: 95%; color: #54487a">~ppc</span></b>/<b><span style="font-family: monospace; font-size: 95%; color: #54487a">~ppc64</span></b>) or stable (<b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc</span></b>/<b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc64</span></b>). Our users can use this information, along with the Portage application, to build a system that suits their needs, whether it is a stable server, embedded system or a bleeding edge desktop system. </p> <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:PowerPC&amp;action=edit&amp;section=2" title="Edit section: Participation">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. </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 our <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?query_format=&amp;short_desc_type=allwordssubstr&amp;short_desc=&amp;long_desc_type=substring&amp;long_desc=&amp;bug_file_loc_type=allwordssubstr&amp;bug_file_loc=&amp;keywords_type=allwords&amp;keywords=&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;emailassigned_to1=1&amp;emailtype1=exact&amp;email1=ppc%40gentoo.org&amp;emailassigned_to2=1&amp;emailreporter2=1&amp;emailqa_contact2=1&amp;emailcc2=1&amp;emailtype2=substring&amp;email2=&amp;bugidtype=include&amp;bug_id=&amp;votes=&amp;changedin=&amp;chfieldfrom=&amp;chfieldto=Now&amp;chfieldvalue=&amp;cmdtype=doit&amp;order=Reuse+same+sort+as+last+time&amp;field0-0-0=noop&amp;type0-0-0=noop&amp;value0-0-0=">bugs</a> . There are always packages that need to be tested, bugs waiting to be found and fixed and enhancements waiting for someone to code them. Feel free to ask the PPC development team on IRC what <i>you</i> can help us with! </p><p>For more information on how the PPC team recruits please read our <a rel="nofollow" class="external text" href="http://www.gentoo.org/recruitment.xml">recruitment</a> page. </p> <h2><span class="mw-headline" id="See_also">See also</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:PowerPC&amp;action=edit&amp;section=3" title="Edit section: See also">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <ul><li><a href="/wiki/PPC" title="PPC">PPC</a> — a landing page for those interested in the <b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc</span></b> and <b><span style="font-family: monospace; font-size: 95%; color: #54487a">ppc64</span></b> architectures.</li></ul> <!-- NewPP limit report Cached time: 20200725211822 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.004 seconds CPU time usage: 0.131 seconds Real time usage: 0.177 seconds Preprocessor visited node count: 668/1000000 Preprocessor generated node count: 2396/1000000 Post‐expand include size: 7234/2097152 bytes Template argument size: 1792/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% 153.406 1 -total 91.92% 141.015 1 Template:Project 48.00% 73.630 10 Template:ProjectMemberLine 20.20% 30.992 10 Template:ProjectMemberLineNickname 11.40% 17.481 11 Template:Project_Member 6.98% 10.708 1 Template:See_also 1.12% 1.724 4 Template:Langswitch 0.72% 1.098 4 Template:Keyword --> </div>'
Unix timestamp of change (timestamp)
1595711902