Mentoring: Difference between revisions

2,318 bytes added ,  9 years ago
no edit summary
imported>Shauna
No edit summary
imported>Shauna
No edit summary
Line 19:
* 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.)
 
=== Proposed Structure ===
 
==== Mailing List ====
 
In order to facilitate a '''community of peers''' and not just mentor-mentee relationships, we will create a private mailing list through which mentees can talk to each other. Part of their mentorship agreement will be to post at least once a month to this list, although hopefully they will post more often. Usage guidelines, including a code of conduct, will be given to students. These guidelines will not discourage off-topic conversation, as off-topic conversation can help list members connect with each other. Depending on how well people take to the list, I may or may not come up with a list of ice-breaker type prompts.
 
==== Hangouts & IRC Meetups ====
 
We will arrange monthly IRC meetups. These will be a chance for mentees to converse in real time.
 
==== Goal-setting Process ====
 
Mentees will work with their mentor to define one or more goals they want to meet as part of the mentorship program. Many students will likely choose "Apply to Google Summer of Code" (or a similar program) as their goal, but additional goals can include:
 
* Getting contributions merged. (Specific projects and kinds of contributions may vary - specificity is encouraged in goal-setting!)
* Help 3 newcomers to a project.
* Learn a particular skill such as git branching, resolving merge conflicts, or to achieve basic use a specific open source project such as R.
* Write an article about getting started in open source (and get it published on the OpenHatch blog, opensource.com, etc).
* Attend an in-person open source meetup.
* Make their own project open source and accessible to newcomers.
 
Students will be considered to have "graduated" when they successfully complete their stated goals.
 
==== ObstaclesPairing ====
 
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.
 
=== Selection ===
 
==== How Mentors Are Selected ====
 
I'm planning to run a pilot of the mentorship program this fall with just myself (and potentially also Asheesh, as needed) as mentors. People who are interested in being mentors in future iterations of the program should contact Shauna.
 
==== How Mentees Are Selected ====
 
Mentees will fill out an application
 
 
 
 
=== Action Items ===
 
* Create application form for mentees.
* Create announcement to send to past students.
* Create mailing list & usage guidelines for mailing list.
 
=== Open Questions ===
=== Further reading ===
 
Line 29 ⟶ 75:
 
 
=== Obstacles ===
 
lack of time, difficulty finding a good project match, imposter syndrome (especially re: programs like GSoC but also contributing generally), integrating into the community
 
=== Structure ===
Line 39 ⟶ 81:
- 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)
 
Still need to address a lot of the obstacles...
Anonymous user