Skip to content

Commit bcbe11c

Browse files
terrikoterriko
committed
Add templates for 2018
1 parent 5f01b58 commit bcbe11c

File tree

3 files changed

+281
-3
lines changed

3 files changed

+281
-3
lines changed

‎index.html

+4-3
Original file line numberDiff line numberDiff line change
@@ -319,8 +319,9 @@ <h3>How do I apply?</h3>
319319

320320
<li>Set up a blog where you will keep track of your GSoC progress</li>
321321

322-
<li>Write your application (with help from your mentors!) Make sure to include the
323-
sub-org name in the title so your mentors can find it in the system.</li>
322+
<li><a href="studenttemplate.html">Write your application</a> (with help from your mentors!) Make sure to include the
323+
sub-org name in the title so your mentors can find it in the system, and make it easy for
324+
your mentors to comment on your doc (e.g. enable comments if you're using google docs)</li>
324325

325326
<li> Submit your application to Google before the deadline. We actually
326327
recommend you submit a few days early in case you have internet problems or
@@ -387,7 +388,7 @@ <h3>Sub-orgs</h3>
387388
student applicant later and want to sign up just for them)
388389

389390
<li>Have a good ideas page. <a
390-
href="https://wiki.python.org/moin/SummerOfCode/OrgIdeasPageTemplate">Here's a template.</a> Getting a really great page
391+
href="orgtemplate.html">Here's a template.</a> Getting a really great page
391392
sometimes takes a few rounds of revisions; Meflin will work with you to make
392393
sure your page is ready!
393394

‎orgtemplate.html

+117
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
<!DOCTYPE html>
2+
<html lang=en>
3+
<head>
4+
<title>Python Google Summer of Code Frequently Asked Questions</title>
5+
<link rel="stylesheet" href="style.css">
6+
</head>
7+
8+
<body>
9+
<!-- Top navigation bar -->
10+
<nav class="fixed-nav-bar">
11+
<div id="menu" class="menu">
12+
<ul class="menu">
13+
<li style="float:left"><a href="index.html#"><img src="python-logo-45px.png"
14+
alt="Python logo" height="45" /></a>
15+
</ul>
16+
</div>
17+
</nav>
18+
19+
<div class="content">
20+
21+
22+
<h1>Python Sub-org Ideas Template</h1>
23+
24+
<p>There are not very many strict requirements for Google Summer of Code Ideas pages, but
25+
there are some things that students often ask us for. This page is intended as a starting
26+
template for organizations so you don't forget those things.
27+
28+
<p>Warning: In 2014, many orgs got rejected because their ideas pages were offline when
29+
Google checked. <strong>Make sure your ideas page is hosted somewhere that Google's Open Source
30+
Programs Office will be able to access when they check!</strong>
31+
32+
<h2>About MyOrg</h2>
33+
34+
<p>Tell the students a bit about your organization. Here's some questions you might want to
35+
answer:
36+
37+
<ul>
38+
<li>What software are you creating?
39+
<li>Why is it interesting?
40+
<li>Who uses it?
41+
<li>What languages is it written in?
42+
<li>How is it going to change the world?
43+
</ul>
44+
45+
46+
<h2>Contacting MyOrg</h2>
47+
48+
<ul>
49+
<li>IRC channel:
50+
<li>Mailing list(s):
51+
<li>List contact methods you actually use and will have mentors monitoring!
52+
</ul>
53+
54+
55+
<p>Include any special instructions/info about communicating: e.g. what time zones are your
56+
mentors in? do you prefer it if gsoc students introduce themselves first or just dive in?
57+
are there any common mistakes students make when making a first impression?
58+
59+
<h2>Getting Started</h2>
60+
61+
<p>Links to setup instructions go here. Some suggested things to answer:
62+
63+
<ul>
64+
<li>Where is the link to a setup guide for new developers?
65+
<li>Are there any unusual libraries/applications that need to be installed first?
66+
<li>What type of source control do you use? (include links to help and setup guides!)
67+
<li>What's the process for submitting your first bug fix?
68+
<li>Where should students look to find easy bugs to try out?
69+
</ul>
70+
71+
<h2>Writing your GSoC application</h2>
72+
73+
<p>Links to advice about applications and the application template goes here.
74+
75+
<ul>
76+
<li>Remind your students that your sub-org name must be in the title of their
77+
applications!
78+
<li>Here's a link to the <a href="studenttemplate.html">Student Application
79+
Template for Python</a>
80+
</ul>
81+
82+
<h2>Project Ideas</h2>
83+
84+
<p>You should usually have a couple of project ideas, ranging in difficulty from beginner to
85+
expert. Please do try to have at least one, preferably several beginner tasks: GSoC gets a
86+
lot of students with minimal open source experience who feel very discouraged (and
87+
sometimes even complain to google) if orgs don't any have projects at their level.
88+
89+
<h3>1. Project name</h3>
90+
91+
<ul>
92+
<li><strong>Project description</strong>: Make sure you have a high-level description that any student can
93+
understand, as well as deeper details
94+
95+
<li><strong>Skills</strong>: programming languages? specific domain knowledge?
96+
97+
<li><strong>Difficulty level</strong>: Easy/Intermediate/Hard classification (students ask for this info
98+
frequently to help them narrow down their choices. Difficulty levels are something google
99+
wants to see, so they aren't optional; make your best guess.)
100+
101+
<li><strong>Related Readings/Links</strong>: was there a mailing list discussion about this topic?
102+
standards you want the students to read first? bugs/feature requests?
103+
104+
<li><strong>Potential mentors</strong>: A list of mentors likely to be involved with this project, so
105+
students know who to look for on IRC/mailing lists if they have questions. (If you've had
106+
trouble with students overwhelming specific mentors, feel free to re-iterate here if
107+
students should contact the mailing list to reach all mentors.)
108+
</ul>
109+
110+
<h3>2. Project name</h3>
111+
112+
<p>As above. etc. Unless there's a compelling reason to sort in some other order, ideas
113+
should be ordered approximately from easiest to hardest.
114+
115+
</div>
116+
</body>
117+
</html>

‎studenttemplate.html

+160
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,160 @@
1+
<!DOCTYPE html>
2+
<html lang=en>
3+
<head>
4+
<title>Python Google Summer of Code Frequently Asked Questions</title>
5+
<link rel="stylesheet" href="style.css">
6+
</head>
7+
8+
<body>
9+
<!-- Top navigation bar -->
10+
<nav class="fixed-nav-bar">
11+
<div id="menu" class="menu">
12+
<ul class="menu">
13+
<li style="float:left"><a href="index.html#"><img src="python-logo-45px.png"
14+
alt="Python logo" height="45" /></a>
15+
</ul>
16+
</div>
17+
</nav>
18+
19+
<div class="content">
20+
21+
22+
<h1>Python Student Application Template (2018)</h1>
23+
<p>Fields at the top of this form are required. Please contact your mentors if you have
24+
any questions, and to make sure that your application is complete after it is submitted.
25+
Ideally, a GSoC application is a <strong>collaborative</strong> process, so please adjust
26+
based on any feedback you are given, and start early so you can get that feedback!
27+
28+
<div class="warning"><strong>Use a good project title in Google's submission
29+
system</strong>
30+
31+
<p>Your project title should explain in a few words what you plan to do and
32+
<strong>include the name of your sub-org</strong>. e.g. "QTile: Refactor window focusing"
33+
or "Kivy: Matplotlib Integration."
34+
35+
<p>Python gets 100+ submissions some years, and it can be very hard for mentors to find your
36+
projects if they all have generic titles like "my gsoc application." A good title can help
37+
you get early feedback that will make you more likely to get accepted, and a bad title
38+
could result in your application getting marked as spam and ignored!
39+
</div>
40+
41+
<h2>Sub-org Information</h2>
42+
<ul>
43+
<li>Which python sub-org are you applying to work with? (e.g. Mailman, SciPy)
44+
<ul>
45+
<li>You MUST specify this. If we have to guess, your application could be rejected in
46+
favour of students who followed instructions.
47+
<li>You must apply to work with <a href="index.html#ideas">a valid sub-org who is
48+
signed up to participate this year</a>. If they're not signed up, we have no mentors for
49+
you, and will likely reject your application.
50+
</ul>
51+
</ul>
52+
53+
<h2>Student Information</h2>
54+
55+
<ul>
56+
<li>Name:
57+
<li>Alternate names: (e.g. github username, irc nick, any other preferred names)
58+
<li>Email:
59+
<li>Telephone:
60+
<li>Time Zone:
61+
<li>GSoC Blog RSS Feed URL:
62+
<ul>
63+
<li>You will be <strong>required</strong> to blog about your GSoC experience approximately every 2
64+
weeks through the summer. The RSS feed is used to aggregate student blogs; we recommend
65+
using a tag like "python" or "gsoc" if you use this blog for anything other than GSoC.
66+
</ul>
67+
</ul>
68+
69+
<h2>Code Sample</h2>
70+
71+
<ul>
72+
<li>Link to a patch/code sample, preferably one you have submitted to your sub-org (*)
73+
74+
<ul>
75+
<li>Note: <strong>Python requires all students to submit a patch</strong>. This does not need to be
76+
accepted and merged into your project, but it does need to be online and available for
77+
potential mentors to inspect. Contact your mentors if you have questions about what
78+
constitutes an appropriate sample. <strong>Applications without a valid code sample will be
79+
rejected.</strong>
80+
<li>The code sample must be an example of your own work.
81+
</ul>
82+
</ul>
83+
84+
<h2>Project Info</h2>
85+
86+
<ul>
87+
<li>Proposal Title:
88+
<ul>
89+
<li>The name of your proposal. This should explain in a few words what you plan to do
90+
and include the name of your sub-org. e.g. "QTile: Refactor window focusing" or "Kivy:
91+
Matplotlib Integration." (Including the name of your sub-org makes it much easier for
92+
mentors to find your proposal!)
93+
</ul>
94+
<li>Proposal Abstract:
95+
<ul>
96+
<li>A short description of your proposed project
97+
</ul>
98+
<li>Proposal Detailed Description/Timeline (*)
99+
<ul>
100+
<li>Please include timeline with milestones, preferably weekly ones. You may wish to
101+
read the GSoC student guide which includes several examples of good proposals with
102+
timelines, or our own information at SummerOfCode/Application
103+
<li>Note that any pre-work such as setup and reading documentation should take place
104+
during the community bonding period, not after coding has started.
105+
</ul>
106+
</ul>
107+
108+
<h2>Other Commitments</h2>
109+
110+
<ul>
111+
<li>Do you have any other commitments during the main GSoC time period?
112+
<ul>
113+
<li><strong>We don't penalize students for needing adjustments to schedule if they're up-front
114+
about them and have a plan to mitigate any issues. However, we *have* failed students for
115+
lying about their availability and subsequently falling behind in their work. Be
116+
honest!</strong>
117+
<li>Do you have exams or classes that overlap with this period?
118+
<li>Do you plan to apply for or have any other jobs or internships during this period?
119+
120+
<ul>
121+
<li>This is highly NOT RECOMMENDED as GSoC is intended to be a full-time job, but
122+
sometimes if a student is starting or finishing an internship with a week or two overlap
123+
something can be worked out.
124+
</ul>
125+
126+
<li>Do you have any other short term commitments during this period?
127+
e.g family wedding, conference, volunteer projects, planned vacation days
128+
</ul>
129+
<li>Have you applied with any other organizations? If so, do you have a preferred
130+
project/org? (This will help us in the event that more than one organization decides they
131+
wish to accept your proposal.)
132+
</ul>
133+
134+
<h2>extra information</h2>
135+
136+
<p>This additional information isn't needed by the PSF, but can help your sub-orgs learn more
137+
about you. All fields in this extra information section are optional.
138+
139+
<ul>
140+
<li>Link to resume:
141+
<li>University info
142+
<ul>
143+
<li>University Name:
144+
<li>Major:
145+
<li>Current Year and Expected Graduation date:
146+
<li>Degree (e.g. BSc, PhD):
147+
</ul>
148+
<li>Other Contact info:
149+
<ul>
150+
<li>Alternate contact info in case your primary email above stops working:
151+
<li>Homepage:
152+
<li>Instant messaging:
153+
<li>Twitter:
154+
</ul>
155+
<li>Don't forget to add any sub-org specific information here.
156+
</ul>
157+
158+
</div>
159+
</body>
160+
</html>

0 commit comments

Comments
 (0)