Mentoring: Difference between revisions

2,939 bytes added ,  9 years ago
imported>Shauna
No edit summary
imported>Shauna
 
(One intermediate revision by the same user not shown)
Line 45:
 
As part of achieving their goals, students will be encouraged to pair with their mentors and with each other. We will aim for one pairing experience per mentee per month, ideally starting early in the mentorship program.
 
=== How Structure Meets Needs ===
 
<blockquote>* More instruction/repetition on the skills we teach at our events (IRC, version control, issue trackers, etc.)</blockquote>
 
This should be achieved, informally, through pairing and discussions with their mentor and perhaps also via the mailing list. However the program as currently defined does not ''inherently'' or ''systemically'' reinforce/extend our instruction.
 
<blockquote>* Help finding good projects (learning which ones exist, how to evaluate them, benefiting from our community's informal knowledge about which projects are most welcoming/responsive, etc)</blockquote>
 
This should be achieved, informally, through discussions with their mentor and perhaps also via the mailing list. However the program as currently defined does not ''inherently'' or ''systemically'' reinforce/extend our instruction.
 
<blockquote>* Help understanding community norms and structures that may be otherwise invisible (how long is normal for someone to respond to you and is it okay to ping them again, how FOSS projects functions without deadlines and assignments in an academic sense, development environment setup is frequently difficult it's not just you, FOSS can be harder for reflective learners than active learners, etc)</blockquote>
 
This should be achieved, informally, through discussions with their mentor and perhaps also via the mailing list. However the program as currently defined does not ''inherently'' or ''systemically'' reinforce/extend our instruction.
 
<blockquote>* A social network to increase feelings of belonging and enjoyment of participation. (Peers at a similar level of experience, role models who they can identify with and who feel approachable, a source of positive feedback for their work not just from the projects they're contributing to, a sense of shared values, a place to turn when they feel discouraged or like an impostor).</blockquote>
 
This is the main purpose of the mailing list and IRC meetups. Discussion prompts may be needed to direct the community towards these characteristics.
 
<blockquote>* Help finding "easy wins" to increase feelings of competence and belonging. (An easy win may be fixing an issue for a specific project we've helped them find, but could also involve helping others, or doing setup sprints or user feedback or other contributions that rely on and require their new-ness.)</blockquote>
 
The program is not currently set up to provide this.
 
<blockquote>* Help setting achievable goals. (Many students want to apply for GSoC/OPW but are intimidated, most aren't sure what they can contribute to a given project at their experience/skill level, many are confused/concerned about what kind of time commitment they're making, etc.)</blockquote>
 
This is the main purpose of the goal-setting portion of the program.
 
=== Selection ===
Line 54 ⟶ 80:
==== How Mentees Are Selected ====
 
Students interested in the program will fill out an application. This allows students to demonstrate a significant interest while allowing us to determine if they're a good fit for the program.
Mentees will fill out an application
 
===== Diversity =====
 
It's unclear how popular this program will be, but if there is more demand than we can meet, we may want to prioritize mentoring under-represented students.
 
 
Line 64 ⟶ 92:
* Create announcement to send to past students.
* Create mailing list & usage guidelines for mailing list.
* Create website (or sub-page of campus.oh.org or oh.org) to host application and FAQ?
* Create metrics for measuring success.
 
=== Open Questions ===
=== Further reading ===
 
Line 71 ⟶ 100:
 
[https://openhatch.org/wiki/Open_Source_Reading_List#Mentorship_and_Community-building_in_FLOSS Mentoring in Floss Resources]
 
=== Goals ===
 
 
=== Structure ===
- mailing list and monthly IRC meetings: build community, allow me to keep track of/follow up with students
- IRC meetings with individual recommended projects?
- activities that are more thorough than we can do at workshops?
- remote pair programming/mentoring (prob need to get a list of people to mentor)
Anonymous user