-
Notifications
You must be signed in to change notification settings - Fork 120
/
mentors.html
407 lines (352 loc) · 26.2 KB
/
mentors.html
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
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
<!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">
<meta name="google-site-verification" content="EVShtJLdVKN58OupOAYPkH6QRA3i-J8q4ZEklgFiZhE" />
<title>Python GSoC – Home</title>
<link rel="stylesheet" href="https://unpkg.com/purecss@1.0.0/build/pure-min.css"
integrity="sha384-nn4HPE8lTHyVtfCBi5yW9d20FjT8BJwUXyWZT9InLYax14RDjBj46LmSztkmNP9w" 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://cdnjs.cloudflare.com/ajax/libs/font-awesome/5.8.1/css/all.min.css"
integrity="sha384-50oBUHEmvpQ+1lW4y57PTFmhCaXp0ML5d60M1M7uH2+nqUivzIebhndOJK28anvf" 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="layout">
<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="contributors.html" class="pure-menu-link">Contributors</a></li>
<li class="pure-menu-item"><a href="mentors.html" class="pure-menu-link">Mentors</a></li>
<li class="pure-menu-item"><a href="ideas.html" 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="contributors.html#faq" class="pure-menu-link">FAQ</a></li>
<li class="pure-menu-item"><a href="mentors.html#sub-orgs" class="pure-menu-link">Info for Sub-orgs</a></li>
<li class="pure-menu-item"><a href="blogs.html" 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 new contributors</strong>: Mentoring a
GSoC contributor 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 GSoC contributor 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>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 GSoC contributor and mentor
questions in various time zones. We are particularly looking for volunteers
who can read and comment on contributor posts, remind contributors if they haven't
posted, and promote the work our GSoC contributors do to the larger Python community.
Or maybe you have another skillset you'd like to contribute? (Proofreading?
Recruiting diverse contributor 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-ribbon 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 content-head-ribbon">
<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 contributors, and selecting
contributors from their proposals. After contributors 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 GSoC contributor: experienced contributors may need
very little supervision, inexperienced contributors may need more. It also depends on you: You
and your co-mentor(s) select the person and project you mentor, so you can choose
according to the time commitment you have. Some mentors even do pair programming with
their GSoC contributors!)</p>
<p>I recommend at least one mentor has a <strong>weekly 1hr meeting with the GSoC contributor</strong>
so
they get to
know each other, keep everyone on track, and give a chance to talk about other stuff. Lots
of contributors have questions about jobs, courses, architecture, open source, etc. and it's
nice for contributors to have someone to talk to especially since many of them will not have
worked
remotely
on their own for any length of time before. 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 content-head-ribbon">
<i class="fas fa-people-carry"></i>
Work Together
</h3>
<p>We want <strong>at least two mentors per project</strong>, 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 contributors 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 content-head-ribbon">
<i class="fas fa-brain"></i>
Knowledge required
</h3>
<p><strong>Our most successful mentors are those who are already developers or community
members of
their open source project.</strong> If you're joining a new project for GSoC, expect to
take time
to learn the ropes yourself so you can help GSoC contributors. </p>
<p>Mentors don't have to be the Best At Everything. A lot of what mentors do is keep contributors
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
contributors understand why features make sense (or dont!), system administrators can help
contributors
understand how deployment works in practice, experts in areas like accessibility,
usability,
and security could help guide contributors 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 content-head-ribbon">
<i class="fas fa-calendar-check"></i>
Evaluating GSoC contributors
</h3>
<p>Mentors do have to do multiple evaluations on each GSoC contributor, 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 GSoC contributor is doing and then a pass/fail that determines if the
GSoC contributor gets paid and continues in the program.</p>
</div>
</div>
</div>
</div>
<a id="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>
<div class="warning">
<div class="pure-u-1 pure-u-md-1-1 pure-u-lg-1-1">
Looking for the list of currently accepted sub-orgs? It's <a href="index.html#ideas">the project ideas list</a>.
</div>
</div>
<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>Email gsoc-admins@python.org for the registration application
<li>Have one sub-org admin and at least two mentors who are willing to commit
to the full GSoC period. (More is awesome!) Thats a minimum of 3 people total, although your sub-org admin is allowed to also be a mentor or backup mentor.
<ul>
<li>If you want to connect with more potential volunteers,
email gsoc-admins@python.org
to see if we can match you with volunteers who don't have a project.</li>
</ul>
<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
GSoC contributor applicant later and want to sign up just for them).
<li>Have a good ideas page. <a href="#orgtemplate">We have a template below.</a> Getting a
really
great page
sometimes takes a few rounds of revisions; We will work with you to make
sure your page is ready!
<li>Be able to handle <a href="deadlines.html">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 core volunteer burnout.
<li>Disclose all potential conflicts of interest to the Python admins <b>BEFORE</b> accepting a
GSoC contributor. If you are unsure, ask. If a conflict is found after the fact the GSoC contributor and
sub-org may be dropped from the program. (Examples: GSoC contributor is involved in your research
group,
GSoC contributor is your child, GSoC contributor owes you money, etc.)
<li>Give access to any private communication channels to the PSF admins for the duration of
GSoC that are used for the project, ie slack, private git repo, discord etc. This is mostly
so we
can reach you where you're already looking for gsoc-related messages, but could also be used
if a GSoC contributor has a dispute with a mentor and asks for our help.
</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 GSoC contributors 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 GSoC contributors to find projects that best suit them!</p>
<p>Please note: The funds Google gives Python as mentor stipends are given to the
<a href="https://www.python.org/psf/grants/">PSF grants program</a> rather than
dispensed per sub-org.
</p>
</div>
</div>
<a id="orgtemplate"></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-ribbon is-center">Python Sub-org Ideas Template
</h2>
<p>There are not very many strict requirements for Google Summer of Code Ideas pages, but
there are some things that GSoC contributors often ask us for. This page is intended as a starting
template for organizations so you don't forget those things.
<p>Warning: In 2014, many orgs got rejected because their ideas pages were offline when
Google checked. <strong>Make sure your ideas page is hosted somewhere that Google's Open
Source
Programs Office will be able to access when they check!</strong>
<h3 class="content-head-ribbon content-subhead">About MyOrg</h3>
<p>Tell the prospective contributors a bit about your organization. Here's some questions you might want to
answer:
<ul>
<li>What software are you creating?
<li>Why is it interesting?
<li>Who uses it?
<li>What languages is it written in?
<li>How is it going to change the world?
</ul>
<h3 class="content-head-ribbon content-subhead">Contacting MyOrg</h3>
<ul>
<li>IRC channel:
<li>Mailing list(s):
<li>List contact methods you actually use and will have mentors monitoring!
</ul>
<p>Include any special instructions/info about communicating: e.g. what time zones are
your
mentors in? do you prefer it if GSoC contributors introduce themselves first or just
dive
in?
are there any common mistakes contributors make when making a first impression?
<h3 class="content-head-ribbon content-subhead">Getting Started</h3>
<p>Links to setup instructions go here. Some suggested things to answer:
<ul>
<li>Where is the link to a setup guide for new developers?
<li>Are there any unusual libraries/applications that need to be installed
first?
<li>What type of source control do you use? (include links to help and
setup
guides!)
<li>What's the process for submitting your first bug fix?
<li>Where should new contributors look to find easy bugs to try out?
</ul>
<h3 class="content-head-ribbon content-subhead">Writing your GSoC application
</h3>
<p>Links to advice about applications and the application template goes here.
<ul>
<li>Remind your GSoC contributors that your sub-org name must be in the title of
their
applications!
<li>Here's a link to the <a href="index.html#apply">GSoC contributor application
information for Python</a>
</ul>
<h3 class="content-head-ribbon content-subhead">Project Ideas</h3>
<p>You should usually have a couple of project ideas, ranging in difficulty
from beginner to
expert. Please do try to have at least one, preferably several beginner
tasks: GSoC gets a
lot of new contributors with minimal open source experience who feel very
discouraged (and
sometimes even complain to Google) if orgs don't any have projects at
their
level.
<h4 style="color: white;">1. Project name</h4>
<ul>
<li><strong>Project description</strong>: Make sure you have a
high-level description that any new GSoC contributor can
understand, as well as deeper details
<li><strong>Skills</strong>: programming languages? specific domain
knowledge?
<li><strong>Difficulty level</strong>: Easy/Intermediate/Hard
classification (contributors ask for this info
frequently to help them narrow down their choices. Difficulty
levels are something Google
wants to see, so they aren't optional; make your best guess.)
<li><strong>Related Readings/Links</strong>: was there a mailing
list
discussion about this topic?
standards you want new contributors to read first? bugs/feature
requests?
<li><strong>Potential mentors</strong>: A list of mentors likely to
be
involved with this project, so
GSoC contributors know who to look for on IRC/mailing lists if they have
questions. (If you've had
trouble with GSoC contributors overwhelming specific mentors, feel free
to
re-iterate here if
GSoC contributors should contact the mailing list to reach all mentors.)
<li><strong>Project Length</strong>: Medium size projects should take about
175 hours to complete while large projects should take about 350 hours to
complete, you should put if the project idea would be a medium or a large
project.
</ul>
<h4 style="color: white;">2. Project name</h4>
<p>As above. etc. Unless there's a compelling reason to sort in some
other
order, ideas
should be ordered approximately from easiest to hardest.
<p>If you're open to other
project ideas from contributors, say so and make sure there's a clear path for
contributors to discuss ideas with mentors before submitting an application.
Otherwise, we've found that you'll get a lot of project ideas that aren't
suitable for GSoC: too small, too large, bad fit for the project, no mentors
interested in taking them on, etc. You may have an open discussion thread in
your bug tracker/forums, a chat channel or mailing list, or contact info for a
mentor who's open to discussing new ideas in private.</p>
</div>
</div>
</div> <!-- content -->
</div>
<script src="js/ui.js"></script>
</body>
</html>