-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmentors.html
More file actions
229 lines (200 loc) · 13.5 KB
/
mentors.html
File metadata and controls
229 lines (200 loc) · 13.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Python's Google Summer of Code Page">
<title>Python GSoC – Mentors</title>
<link rel="stylesheet" href="https://unpkg.com/purecss@1.0.0/build/pure-min.css" integrity="sha384-" crossorigin="anonymous">
<!--[if lte IE 8]>
<link rel="stylesheet" href="https://unpkg.com/purecss@1.0.0/build/grids-responsive-old-ie-min.css">
<![endif]-->
<!--[if gt IE 8]><!-->
<link rel="stylesheet" href="https://unpkg.com/purecss@1.0.0/build/grids-responsive-min.css">
<!--<![endif]-->
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.5.0/css/all.css" integrity="sha384-B4dIYHKNBt8Bc12p+WXckhzcICo0wtJAoU8YZTY5qE0Id1GSseTk6S+L3BlXeVIU"
crossorigin="anonymous">
<!--[if lte IE 8]>
<link rel="stylesheet" href="css/side-menu-old-ie.css">
<![endif]-->
<!--[if gt IE 8]><!-->
<link rel="stylesheet" href="css/side-menu.css">
<!--<![endif]-->
<link rel="stylesheet" href="css/python-gsoc.css">
</head>
<body>
<!-- Menu toggle -->
<a href="#menu" id="menuLink" class="menu-link">
<!-- Hamburger icon -->
<span></span>
</a>
<div id="menu">
<div class="pure-menu">
<a class="pure-menu-heading" href="index.html">Python GSoC</a>
<ul class="pure-menu-list">
<li class="pure-menu-item"><a href="index.html#gettingstarted" class="pure-menu-link">Getting Started</a></li>
<li class="pure-menu-item"><a href="students.html" class="pure-menu-link">Students</a></li>
<li class="pure-menu-item pure-menu-selected"><a href="mentors.html" class="pure-menu-link">Mentors</a></li>
<li class="pure-menu-item"><a href="index.html#ideas" class="pure-menu-link">Project Ideas</a></li>
<li class="pure-menu-item"><a href="deadlines.html" class="pure-menu-link">Deadlines</a></li>
<li class="pure-menu-item"><a href="https://blogs.python-gsoc.org" class="pure-menu-link">Blogs</a></li>
<li class="pure-menu-item"><a href="index.html#contact" class="pure-menu-link">Contact</a></li>
</ul>
</div>
</div> <!-- menu -->
<div class="content">
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h2 class="content-head content-head is-center">Mentors</h2>
<p>Interested in volunteering with the Python Software Foundation?</p>
<p><strong>The biggest job is mentoring students</strong>: Mentoring a
student as a primary mentor can be a pretty big time commitment (see
"<a href="#whatmentor">What does it take to be a mentor?</a>" for more information) but it's a very
rewarding chance to give a student an open source apprenticeship.
We mentor in teams, so if all you can handle is a few code reviews or taking
over for a week while someone's on vacation, you can team up with someone with more time.</p>
<p><strong>The easiest way to become a mentor is to be part of one of the sub-orgs
that plan to be involved</strong>, so get in touch with them directly if you want to
help. If you're part of a group that would like to participate as a sub-org,
please read the section for sub-orgs below.</p>
<p></p>If you're not already part of a group
that wants to participate, we can try to match you with one, but be aware that to do
the best job of mentoring you're going to need to know the open source project pretty
well yourself. If you're not already a developer, you should be prepared to become
an active community member.
</p>
<p><strong>But we often need other volunteers!</strong> We're also looking for
friendly community members to help with other tasks! We'd love to have more
people available on IRC/Mailing lists to answer student and mentor
questions in various time zones. We are particularly looking for volunteers
who can read and comment on student blogs, remind students if they haven't
posted, and promote the work our students do to the larger Python community.
Or maybe you have another skillset you'd like to contribute? (Proofreading?
Recruiting diverse student applicants?) If you want to help, we can try to
find a way to make that happen.</p>
<p><strong>If you'd like to volunteer, get in touch with a sub-org admin or
email the Python org admins at gsoc-admins(at)python(dot)org </strong></p>
</div>
</div>
<a name="whatmentor"></a>
<div class="ribbon l-box-lrg pure-g">
<div class="content">
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h2 class="content-head content-head is-center">What does it take to be a mentor?</h2>
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h3 class="content-subhead">
<i class="fas fa-clock"></i>
Time commitment
</h3>
<p><strong>We expect around a 0-10hr/week commitment</strong>, which sounds scary, but it's not
actually that
variable. You usually spend up to lots of time for the first few weeks, where you're
fleshing out your ideas page, discussing projects with many students, and selecting
students from their proposals. After students are selected and settled in, it becomes more
like
a 1hr
commitment per week for a weekly meeting, and maybe a few more hours here and there for
code review or questions. (That depends on your student: experienced students may need
very little supervision, inexperienced students may need more. It also depends on you: You
and your co-mentor(s) select the student and project you mentor, so you can choose
according to the time commitment you have. Some mentors even do pair programming with
their students!)</p>
<p>I recommend at least one mentor has a <strong>weekly 1hr meeting with the student</strong> so
they get to
know each other, keep everyone on track, and give a chance to talk about other stuff (lots
of students have questions about jobs, courses, architecture, open source, etc. and it's
nice to have someone to talk to especially if you're working remote on your own). Some
weeks
this meeting may be the only mentoring time
needed.</p>
</div>
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h3 class="content-subhead">
<i class="fas fa-people-carry"></i>
Work Together
</h3>
<p>We want at least two mentors per projects, so hopefully no one ever gets overwhelmed and
feels like they're always on call (Google does ask that we try to answer questions within
48h so students can't get stuck for too long), and no one mentor has to know all the
answers.</p>
</div>
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h3 class="content-subhead">
<i class="fas fa-brain"></i>
Knowledge required
</h3>
<p>Our most successful mentors are those who are already developers or community members of
their open source project. If you're joining a new project for GSoC, expect to take time
to learn the ropes yourself so you can help students. </p>
<p>Mentors don't have to be the Best At Everything. A lot of what mentors do is keep students
on track and keep them from getting stuck for too long. Sometimes that means just knowing
who to ask or where to look rather than knowing the answer yourself. </p>
<p>In an ideal world, at
least one mentor can answer at least basic architectural questions and knows how to get
code accepted upstream. Not every mentor has to be a coder: experienced users can help
students understand why features make sense (or dont!), system administrators can help student
understsand how deployment works in practice, experts in areas like accessibility, usability,
and security could help guide students in their areas of expertise.</p>
</div>
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h3 class="content-subhead">
<i class="fas fa-calendar-check"></i>
Evaluating students
</h3>
<p>Mentors do have to do multiple evaluations on the student, two mid-terms and one at the end.
Usually the mentors discuss
and then the "primary" mentor fills in the evaluation with input from all mentors.
There's a
few questions about how the student is doing and then a pass/fail that determines if the
student gets paid and continues in the program.</p>
</div>
</ul>
</div>
</div>
</div>
<a name="sub-orgs"></a>
<div class="content">
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
<h2 class="content-head content-head is-center">Sub Orgs</h2>
<p>To participate under the Python umbrella, a sub-org must do the following:
<ol>
<li>Be a Python-based open source project that <a href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_a_mentoring_organization">meets
Google's requirements
for GSoC</a>.
<li>Have one sub-org admin and at least two mentors who are willing to commit
to the full GSoC period. (More is awesome, though!)
<li>Accept the <a href="https://www.python.org/psf/codeofconduct/">Python
Community Code of Conduct</a> for the duration of the
program.
<li>Send an email indicating interest to gsoc-admins(at)python(dot)org before
the Python deadline (exceptions <em>can</em> be made if you get an amazing
student applicant later and want to sign up just for them).
<li>Have a good ideas page. <a href="orgtemplate.html">Here's a template.</a> Getting a really
great page
sometimes takes a few rounds of revisions; Meflin will work with you to make
sure your page is ready! Once you're ready for review, you can <a href="https://github.com/python-gsoc/python-gsoc.github.io">send
a pull request to get
added to this page</a>
<li>Be able to handle <a href="#schedule">meeting deadlines</a> and following both Google
and Python's rules. We try to send important reminders for big deadlines, but we only
have limited volunteer time for nagging and cajoling. Groups that cause repeated problems
may be asked to take time off to limit volunteer burnout.
<li>Disclose all potental conflicts of interest to the Python admins <b>BEFORE</b> accepting a
student. If you are unsure, ask. If a conflict is found after the fact the student and
sub-org may be dropped from the program. (Examples: student is involved in your research group,
student is your child, student owes you money, etc.)
</ol>
<p>We can't promise to take everyone who meets those criteria, but we do try to
take any group that we feel will give the students a great experience.
Terri has final say in which projects participate under the Python
umbrella, but please send any queries to all the admins at
gsoc-admins(at)python(dot)org to make sure we're all on the same page.</p>
<p><strong>Python projects are welcome and encouraged to apply as separate
mentoring organizations directly with Google.</strong> We're happy to help
you in any way we can and we don't mind being your backup plan. We're also
happy to help advertise python based organizations not under our umbrella: we
want students to find projects that best suit them!</p>
</div>
</div> <!-- content -->
</body>
</html>
<script src="js/ui.js"></script>