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)`	806
Name of the user account `(user_name)`	'Alicef'
Age of the user account `(user_age)`	56931962
Page ID `(page_id)`	192930
Page namespace `(page_namespace)`	510
Page title (without namespace) `(page_title)`	'Mentors'
Full page title `(page_prefixedtitle)`	'Project:Mentors'
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=Mentors \|Description=The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. \|Email=mentors@gentoo.org \|IRC=#gentoo-mentors \|ParentProject=Project:ComRes \|PropagatesMembers=Yes \|Members={{Project Member \|Developer=User:Aliceinwire \|IsLead=No }} }} The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. It provides general support for candidates who are working on the recruitment quizzes and preparing for interviews. It also offers guidance to those who are interested in applying to become a Gentoo developer but not exactly sure where to begin. There is an appeal for developers who are interested in becoming mentors as well. Mentoring is of both social and technical in nature. Even though the technical topics are well documented, the social aspect of mentoring is usually kept between mentor and mentoree, and not shared between mentors. We hope to attract senior developers with strong mentoring experience who are willing to pass down their knowledge, assist, and advise prospective mentors. We seek to maintain healthy collaborations with other community facing project such as [[Project:Recruiters\|Recruiters]] and [[Project:Proxy Maintainers\|Proxy Maintainers]]. We do not intend to be a replacement for developer help resources and channels, but rather an addition that focuses more on the recruitment and quiz side of things. == Information for prospective developers == === What is a Gentoo developer === A large distro such as Gentoo consists of many diverse components. While software packaging and writing ebuilds is the main focus, sustainability demands proper infrastructure, documentation and healthy relations with the community. Some developers work on the wiki, forums, infrastructure, GLSAs and other non-ebuild related areas of Gentoo. Other developers write code for various projects such as Portage package manager or package software by writing ebuilds and committing to the [https://gitweb.gentoo.org/repo/gentoo.git official package repository]. === Perks of being a Gentoo developer === By becoming a Gentoo developer, you will be granted the following privileges: * A '''@gentoo.org''' email address * Developer status in Gentoo Bugzilla (adds a shiny badge under your name and allows editing of all bugs) * Developer status in Gentoo Wiki (allows article deletion and editing of protected Project and Handbook articles) * A developer cloak ('''gentoo/developer/username''') on freenode IRC * Developer status in Gentoo Forums (adds a shiny badge under your name) * A personal blog and listing on [https://planet.gentoo.org/ Planet Gentoo] Additionally, there are numerous role-specific privileges that can be granted depending on which areas you are working in. Some examples: * Commit access to the main package repository * Commit access to project-specific repositories * Additional site-specific accesses (forums, wiki, planet, ...) === A brief overview of the recruitment process === The Recruiters project determines the [[Project:Recruiters/Mentoring#The_recruitment_process\|details of the recruitment process]] and its requirements. We only provide a brief overview here. The recruitment consists of mainly these steps: * Finding a mentor * Answering the developer quizzes, which are: (more information can be found on the [[Project:Recruiters/Mentoring#The_recruitment_process\|Recruiters page]]) [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/developer-quiz.txt Developer quiz]: The initial quiz that all developer candidates must answer [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/ebuild-quiz.txt Ebuild quiz]: The quiz for candidates who will be doing ebuild development for the official Gentoo repository ** [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/end-quiz.txt End quiz]: The final quiz for the developer candidates who will be doing ebuild development for the official Gentoo repository * Interviewing with a recruiter Finding a mentor is one of the most essential elements of recruitment. The mentor is responsible for helping the candidate out the quizzes, making sure that the candidate gains sufficient knowledge and practice, and is ready for the interviews with the recruiters. The mentor also assists the candidate with working in a multi-national multi-disciplinary environment such as Gentoo and makes sure that the candidate develops the necessary social skills for it. No candidate may become a developer without the approval of their mentor. === Where to begin? === Mentoring is volunteer work, an arrangement between a developer and a user seeking recruitment. There is no authority (including this project) that will assign you a mentor upon request. Instead, you need to get yourself noticed with your contributions. Note that not having an official mentor doesn't mean you can't reach out to developers and ask questions; on the contrary, that's a good way to find yourself a mentor. A good way to begin the journey is by looking for [[Contributing to Gentoo\|areas to contribute]]. The wiki has a [[Project:Gentoo \| list of all the projects in Gentoo]], including this one. If you spot a project that you can contribute to, get in touch with them through the contact information listed on the project's wiki page. If you are interested in writing ebuilds and maintaining packages, the [[Project:Proxy_Maintainers \| Proxy Maintainers]] project can help you get started. There is also a [[Project:Gentoo/Staffing_Needs \| list of staffing needs]] for various projects. In summary, instead of looking for a mentor to contribute to Gentoo, look for contribution opportunities to find a mentor.'
New page wikitext, after the edit `(new_wikitext)`	'{{Project \|Name=Mentors \|Description=The Mentors project acts as a matchmaking service between prospectivedevelopers and volunteer mentors. \|Email=mentors@gentoo.org \|IRC=#gentoo-mentors \|ParentProject=Project:ComRes \|PropagatesMembers=Yes }} The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. It provides general support for candidates who are working on the recruitment quizzes and preparing for interviews. It also offers guidance to those who are interested in applying to become a Gentoo developer but not exactly sure where to begin. There is an appeal for developers who are interested in becoming mentors as well. Mentoring is of both social and technical in nature. Even though the technical topics are well documented, the social aspect of mentoring is usually kept between mentor and mentoree, and not shared between mentors. We hope to attract senior developers with strong mentoring experience who are willing to pass down their knowledge, assist, and advise prospective mentors. We seek to maintain healthy collaborations with other community facing project such as [[Project:Recruiters\|Recruiters]] and [[Project:Proxy Maintainers\|Proxy Maintainers]]. We do not intend to be a replacement for developer help resources and channels, but rather an addition that focuses more on the recruitment and quiz side of things. == Information for prospective developers == === What is a Gentoo developer === A large distro such as Gentoo consists of many diverse components. While software packaging and writing ebuilds is the main focus, sustainability demands proper infrastructure, documentation and healthy relations with the community. Some developers work on the wiki, forums, infrastructure, GLSAs and other non-ebuild related areas of Gentoo. Other developers write code for various projects such as Portage package manager or package software by writing ebuilds and committing to the [https://gitweb.gentoo.org/repo/gentoo.git official package repository]. === Perks of being a Gentoo developer === By becoming a Gentoo developer, you will be granted the following privileges: * A '''@gentoo.org''' email address * Developer status in Gentoo Bugzilla (adds a shiny badge under your name and allows editing of all bugs) * Developer status in Gentoo Wiki (allows article deletion and editing of protected Project and Handbook articles) * A developer cloak ('''gentoo/developer/username''') on freenode IRC * Developer status in Gentoo Forums (adds a shiny badge under your name) * A personal blog and listing on [https://planet.gentoo.org/ Planet Gentoo] Additionally, there are numerous role-specific privileges that can be granted depending on which areas you are working in. Some examples: * Commit access to the main package repository * Commit access to project-specific repositories * Additional site-specific accesses (forums, wiki, planet, ...) === A brief overview of the recruitment process === The Recruiters project determines the [[Project:Recruiters/Mentoring#The_recruitment_process\|details of the recruitment process]] and its requirements. We only provide a brief overview here. The recruitment consists of mainly these steps: * Finding a mentor * Answering the developer quizzes, which are: (more information can be found on the [[Project:Recruiters/Mentoring#The_recruitment_process\|Recruiters page]]) [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/developer-quiz.txt Developer quiz]: The initial quiz that all developer candidates must answer [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/ebuild-quiz.txt Ebuild quiz]: The quiz for candidates who will be doing ebuild development for the official Gentoo repository ** [https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/end-quiz.txt End quiz]: The final quiz for the developer candidates who will be doing ebuild development for the official Gentoo repository * Interviewing with a recruiter Finding a mentor is one of the most essential elements of recruitment. The mentor is responsible for helping the candidate out the quizzes, making sure that the candidate gains sufficient knowledge and practice, and is ready for the interviews with the recruiters. The mentor also assists the candidate with working in a multi-national multi-disciplinary environment such as Gentoo and makes sure that the candidate develops the necessary social skills for it. No candidate may become a developer without the approval of their mentor. === Where to begin? === Mentoring is volunteer work, an arrangement between a developer and a user seeking recruitment. There is no authority (including this project) that will assign you a mentor upon request. Instead, you need to get yourself noticed with your contributions. Note that not having an official mentor doesn't mean you can't reach out to developers and ask questions; on the contrary, that's a good way to find yourself a mentor. A good way to begin the journey is by looking for [[Contributing to Gentoo\|areas to contribute]]. The wiki has a [[Project:Gentoo \| list of all the projects in Gentoo]], including this one. If you spot a project that you can contribute to, get in touch with them through the contact information listed on the project's wiki page. If you are interested in writing ebuilds and maintaining packages, the [[Project:Proxy_Maintainers \| Proxy Maintainers]] project can help you get started. There is also a [[Project:Gentoo/Staffing_Needs \| list of staffing needs]] for various projects. In summary, instead of looking for a mentor to contribute to Gentoo, look for contribution opportunities to find a mentor.'
Unified diff of changes made by edit `(edit_diff)`	'@@ -1,14 +1,9 @@ {{Project \|Name=Mentors -\|Description=The Mentors project acts as a matchmaking service between prospective -developers and volunteer mentors. +\|Description=The Mentors project acts as a matchmaking service between prospectivedevelopers and volunteer mentors. \|Email=mentors@gentoo.org \|IRC=#gentoo-mentors \|ParentProject=Project:ComRes \|PropagatesMembers=Yes -\|Members={{Project Member -\|Developer=User:Aliceinwire -\|IsLead=No -}} }} The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. It provides general support for candidates who are working on the recruitment quizzes and preparing for interviews. It also offers guidance to those who are interested in applying to become a Gentoo developer but not exactly sure where to begin. '
Old page size `(old_size)`	5787
Lines added in edit `(added_lines)`	[ 0 => '\|Description=The Mentors project acts as a matchmaking service between prospectivedevelopers and volunteer mentors.' ]
Lines removed in edit `(removed_lines)`	[ 0 => '\|Description=The Mentors project acts as a matchmaking service between prospective', 1 => 'developers and volunteer mentors.', 2 => '\|Members={{Project Member', 3 => '\|Developer=User:Aliceinwire', 4 => '\|IsLead=No', 5 => '}}' ]
New page text, stripped of any markup `(new_text)`	' Mentors Description The Mentors project acts as a matchmaking service between prospectivedevelopers and volunteer mentors. Project email mentors@gentoo.org IRC channel #gentoo-mentors Lead(s) none No lead election date set Member(s) [[User:Aliceinwire\|]] Subproject(s)(and inherited member(s)) (none) Parent Project Community Resources Project listing The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. It provides general support for candidates who are working on the recruitment quizzes and preparing for interviews. It also offers guidance to those who are interested in applying to become a Gentoo developer but not exactly sure where to begin. There is an appeal for developers who are interested in becoming mentors as well. Mentoring is of both social and technical in nature. Even though the technical topics are well documented, the social aspect of mentoring is usually kept between mentor and mentoree, and not shared between mentors. We hope to attract senior developers with strong mentoring experience who are willing to pass down their knowledge, assist, and advise prospective mentors. We seek to maintain healthy collaborations with other community facing project such as Recruiters and Proxy Maintainers. We do not intend to be a replacement for developer help resources and channels, but rather an addition that focuses more on the recruitment and quiz side of things. Contents 1 Information for prospective developers 1.1 What is a Gentoo developer 1.2 Perks of being a Gentoo developer 1.3 A brief overview of the recruitment process 1.4 Where to begin? Information for prospective developers[edit] What is a Gentoo developer[edit] A large distro such as Gentoo consists of many diverse components. While software packaging and writing ebuilds is the main focus, sustainability demands proper infrastructure, documentation and healthy relations with the community. Some developers work on the wiki, forums, infrastructure, GLSAs and other non-ebuild related areas of Gentoo. Other developers write code for various projects such as Portage package manager or package software by writing ebuilds and committing to the official package repository. Perks of being a Gentoo developer[edit] By becoming a Gentoo developer, you will be granted the following privileges: A @gentoo.org email address Developer status in Gentoo Bugzilla (adds a shiny badge under your name and allows editing of all bugs) Developer status in Gentoo Wiki (allows article deletion and editing of protected Project and Handbook articles) A developer cloak (gentoo/developer/username) on freenode IRC Developer status in Gentoo Forums (adds a shiny badge under your name) A personal blog and listing on Planet Gentoo Additionally, there are numerous role-specific privileges that can be granted depending on which areas you are working in. Some examples: Commit access to the main package repository Commit access to project-specific repositories Additional site-specific accesses (forums, wiki, planet, ...) A brief overview of the recruitment process[edit] The Recruiters project determines the details of the recruitment process and its requirements. We only provide a brief overview here. The recruitment consists of mainly these steps: Finding a mentor Answering the developer quizzes, which are: (more information can be found on the Recruiters page) Developer quiz: The initial quiz that all developer candidates must answer Ebuild quiz: The quiz for candidates who will be doing ebuild development for the official Gentoo repository End quiz: The final quiz for the developer candidates who will be doing ebuild development for the official Gentoo repository Interviewing with a recruiter Finding a mentor is one of the most essential elements of recruitment. The mentor is responsible for helping the candidate out the quizzes, making sure that the candidate gains sufficient knowledge and practice, and is ready for the interviews with the recruiters. The mentor also assists the candidate with working in a multi-national multi-disciplinary environment such as Gentoo and makes sure that the candidate develops the necessary social skills for it. No candidate may become a developer without the approval of their mentor. Where to begin?[edit] Mentoring is volunteer work, an arrangement between a developer and a user seeking recruitment. There is no authority (including this project) that will assign you a mentor upon request. Instead, you need to get yourself noticed with your contributions. Note that not having an official mentor doesn't mean you can't reach out to developers and ask questions; on the contrary, that's a good way to find yourself a mentor. A good way to begin the journey is by looking for areas to contribute. The wiki has a list of all the projects in Gentoo, including this one. If you spot a project that you can contribute to, get in touch with them through the contact information listed on the project's wiki page. If you are interested in writing ebuilds and maintaining packages, the Proxy Maintainers project can help you get started. There is also a list of staffing needs for various projects. In summary, instead of looking for a mentor to contribute to Gentoo, look for contribution opportunities to find a mentor. '
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;"> <tr> <th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Mentors</big> </th></tr> <tr valign="top"> <th> Description </th> <td style="text-align: justify;"> The Mentors project acts as a matchmaking service between prospectivedevelopers and volunteer mentors. </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:mentors@gentoo.org">mentors@gentoo.org</a> </td></tr> <tr> <th> <span title="The link opens a webchat to this project's Freenode IRC channel.">IRC channel</span> </th> <td> <a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-mentors">#gentoo-mentors</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>[[User:Aliceinwire\|]] </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:ComRes" title="Project:ComRes">Community Resources</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></table> <p>The Mentors project acts as a matchmaking service between prospective developers and volunteer mentors. It provides general support for candidates who are working on the recruitment quizzes and preparing for interviews. It also offers guidance to those who are interested in applying to become a Gentoo developer but not exactly sure where to begin. </p><p>There is an appeal for developers who are interested in becoming mentors as well. Mentoring is of both social and technical in nature. Even though the technical topics are well documented, the social aspect of mentoring is usually kept between mentor and mentoree, and not shared between mentors. We hope to attract senior developers with strong mentoring experience who are willing to pass down their knowledge, assist, and advise prospective mentors. </p><p>We seek to maintain healthy collaborations with other community facing project such as <a href="/wiki/Project:Recruiters" title="Project:Recruiters">Recruiters</a> and <a href="/wiki/Project:Proxy_Maintainers" title="Project:Proxy Maintainers">Proxy Maintainers</a>. We do not intend to be a replacement for developer help resources and channels, but rather an addition that focuses more on the recruitment and quiz side of things. </p> <div id="toc" class="toc"><div class="toctitle"><h2>Contents</h2></div> <ul> <li class="toclevel-1 tocsection-1"><a href="#Information_for_prospective_developers"><span class="tocnumber">1</span> <span class="toctext">Information for prospective developers</span></a> <ul> <li class="toclevel-2 tocsection-2"><a href="#What_is_a_Gentoo_developer"><span class="tocnumber">1.1</span> <span class="toctext">What is a Gentoo developer</span></a></li> <li class="toclevel-2 tocsection-3"><a href="#Perks_of_being_a_Gentoo_developer"><span class="tocnumber">1.2</span> <span class="toctext">Perks of being a Gentoo developer</span></a></li> <li class="toclevel-2 tocsection-4"><a href="#A_brief_overview_of_the_recruitment_process"><span class="tocnumber">1.3</span> <span class="toctext">A brief overview of the recruitment process</span></a></li> <li class="toclevel-2 tocsection-5"><a href="#Where_to_begin.3F"><span class="tocnumber">1.4</span> <span class="toctext">Where to begin?</span></a></li> </ul> </li> </ul> </div> <h2><span class="mw-headline" id="Information_for_prospective_developers">Information for prospective developers</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Mentors&action=edit&section=1" title="Edit section: Information for prospective developers">edit</a><span class="mw-editsection-bracket">]</span></span></h2> <h3><span class="mw-headline" id="What_is_a_Gentoo_developer">What is a Gentoo developer</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Mentors&action=edit&section=2" title="Edit section: What is a Gentoo developer">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>A large distro such as Gentoo consists of many diverse components. While software packaging and writing ebuilds is the main focus, sustainability demands proper infrastructure, documentation and healthy relations with the community. </p><p>Some developers work on the wiki, forums, infrastructure, GLSAs and other non-ebuild related areas of Gentoo. Other developers write code for various projects such as Portage package manager or package software by writing ebuilds and committing to the <a rel="nofollow" class="external text" href="https://gitweb.gentoo.org/repo/gentoo.git">official package repository</a>. </p> <h3><span class="mw-headline" id="Perks_of_being_a_Gentoo_developer">Perks of being a Gentoo developer</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Mentors&action=edit&section=3" title="Edit section: Perks of being a Gentoo developer">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>By becoming a Gentoo developer, you will be granted the following privileges: </p> <ul><li> A <b>@gentoo.org</b> email address</li> <li> Developer status in Gentoo Bugzilla (adds a shiny badge under your name and allows editing of all bugs)</li> <li> Developer status in Gentoo Wiki (allows article deletion and editing of protected Project and Handbook articles)</li> <li> A developer cloak (<b>gentoo/developer/username</b>) on freenode IRC</li> <li> Developer status in Gentoo Forums (adds a shiny badge under your name)</li> <li> A personal blog and listing on <a rel="nofollow" class="external text" href="https://planet.gentoo.org/">Planet Gentoo</a></li></ul> <p>Additionally, there are numerous role-specific privileges that can be granted depending on which areas you are working in. Some examples: </p> <ul><li> Commit access to the main package repository</li> <li> Commit access to project-specific repositories</li> <li> Additional site-specific accesses (forums, wiki, planet, ...)</li></ul> <h3><span class="mw-headline" id="A_brief_overview_of_the_recruitment_process">A brief overview of the recruitment process</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Mentors&action=edit&section=4" title="Edit section: A brief overview of the recruitment process">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>The Recruiters project determines the <a href="/wiki/Project:Recruiters/Mentoring#The_recruitment_process" title="Project:Recruiters/Mentoring">details of the recruitment process</a> and its requirements. We only provide a brief overview here. The recruitment consists of mainly these steps: </p> <ul><li> Finding a mentor</li> <li> Answering the developer quizzes, which are: (more information can be found on the <a href="/wiki/Project:Recruiters/Mentoring#The_recruitment_process" title="Project:Recruiters/Mentoring">Recruiters page</a>) <ul><li> <a rel="nofollow" class="external text" href="https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/developer-quiz.txt">Developer quiz</a>: The initial quiz that all developer candidates must answer</li> <li> <a rel="nofollow" class="external text" href="https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/ebuild-quiz.txt">Ebuild quiz</a>: The quiz for candidates who will be doing ebuild development for the official Gentoo repository</li> <li> <a rel="nofollow" class="external text" href="https://gitweb.gentoo.org/sites/projects/comrel.git/tree/recruiters/quizzes/end-quiz.txt">End quiz</a>: The final quiz for the developer candidates who will be doing ebuild development for the official Gentoo repository</li></ul></li> <li> Interviewing with a recruiter</li></ul> <p>Finding a mentor is one of the most essential elements of recruitment. The mentor is responsible for helping the candidate out the quizzes, making sure that the candidate gains sufficient knowledge and practice, and is ready for the interviews with the recruiters. The mentor also assists the candidate with working in a multi-national multi-disciplinary environment such as Gentoo and makes sure that the candidate develops the necessary social skills for it. No candidate may become a developer without the approval of their mentor. </p> <h3><span class="mw-headline" id="Where_to_begin.3F">Where to begin?</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Mentors&action=edit&section=5" title="Edit section: Where to begin?">edit</a><span class="mw-editsection-bracket">]</span></span></h3> <p>Mentoring is volunteer work, an arrangement between a developer and a user seeking recruitment. There is no authority (including this project) that will assign you a mentor upon request. Instead, you need to get yourself noticed with your contributions. Note that not having an official mentor doesn't mean you can't reach out to developers and ask questions; on the contrary, that's a good way to find yourself a mentor. </p><p>A good way to begin the journey is by looking for <a href="/wiki/Contributing_to_Gentoo" title="Contributing to Gentoo">areas to contribute</a>. The wiki has a <a href="/wiki/Project:Gentoo" title="Project:Gentoo"> list of all the projects in Gentoo</a>, including this one. If you spot a project that you can contribute to, get in touch with them through the contact information listed on the project's wiki page. If you are interested in writing ebuilds and maintaining packages, the <a href="/wiki/Project:Proxy_Maintainers" title="Project:Proxy Maintainers"> Proxy Maintainers</a> project can help you get started. There is also a <a href="/wiki/Project:Gentoo/Staffing_Needs" title="Project:Gentoo/Staffing Needs"> list of staffing needs</a> for various projects. </p><p>In summary, instead of looking for a mentor to contribute to Gentoo, look for contribution opportunities to find a mentor. </p> <!-- NewPP limit report Cached time: 20181206162315 Cache expiry: 86400 Dynamic content: false [SMW] In‐text annotation parser time: 0.006 seconds CPU time usage: 0.092 seconds Real time usage: 0.100 seconds Preprocessor visited node count: 138/1000000 Preprocessor generated node count: 736/1000000 Post‐expand include size: 1826/2097152 bytes Template argument size: 266/2097152 bytes Highest expansion depth: 7/40 Expensive parser function count: 0/100 --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 71.529 1 -total 100.00% 71.529 1 Template:Project 23.31% 16.672 1 Template:ProjectMemberLine 10.86% 7.768 1 Template:ProjectMemberLineNickname --> </div>'
Unix timestamp of change `(timestamp)`	1544113395