From Fedora Project Wiki

(Created page with "= INFORMATION FOR MENTORS = Please let the coordinators of this program for Fedora, Máirín Duffy and Laura Abbott, know if you would like ...")
 
 
Line 2: Line 2:


Please let the coordinators of this program for Fedora, [[User:Duffy|Máirín Duffy]] and [[User:labbott | Laura Abbott]], know if you would like to help out mentoring for the program.
Please let the coordinators of this program for Fedora, [[User:Duffy|Máirín Duffy]] and [[User:labbott | Laura Abbott]], know if you would like to help out mentoring for the program.
Outreachy has an [https://www.outreachy.org/mentor/mentor-faq/ FAQ] page containing information for mentors. Please review this carefully to make sure you are willing and able to meet the requirements.


All applicants are required to make a small contribution to the project they are applying to work on. As a mentor, you will need to help applicants identify a suitable first task and help them out with it during the application process.
All applicants are required to make a small contribution to the project they are applying to work on. As a mentor, you will need to help applicants identify a suitable first task and help them out with it during the application process.

Latest revision as of 17:45, 5 September 2017

INFORMATION FOR MENTORS

Please let the coordinators of this program for Fedora, Máirín Duffy and Laura Abbott, know if you would like to help out mentoring for the program.

Outreachy has an FAQ page containing information for mentors. Please review this carefully to make sure you are willing and able to meet the requirements.

All applicants are required to make a small contribution to the project they are applying to work on. As a mentor, you will need to help applicants identify a suitable first task and help them out with it during the application process.

Please discuss with the applicants the details of the work they'll be doing during the internship period. It is best if the accepted participants work as part of the team, starting with smaller tasks (i.e. bugs) and progressing over time to more complex tasks (i.e. features), with each task being suggested by you based on the current priorities of the team. So the applicants just need to know what areas of the project they are likely to work on and a tentative timeline.

The project should consist of manageable and relevant tasks that can be incorporated into the project throughout the internship period. Stand-alone projects proposed by an applicant are not suitable at all for people who are not established contributors. Please try to avoid situations when participants work on features that are not yet designed or agreed-upon, have too many moving parts, and would only land in the main code-base after the internship is over as a best-case scenario. This rarely works out. Instead, look for agreed-upon manageable bugs and small features that have a shared theme and would allow the participant to feel the satisfaction of landing her changes throughout the internship.

Good mentorship is a cornerstone of this program. These resources are very useful for prospective mentors to review prior to participating in the program for the first time: