You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. A **descriptive title** including the name of the **sub-org** you want to work with (if this is missing, your application may be rejected!)
3
+
2.**Information about you**, including contact information.
4
+
3. Link to a **code contribution** you have made to your organization. (Usually this is a link to a pull request.)
5
+
4. Information about your **proposed project**. This should be fairly detailed and include a **timeline**.
6
+
5. Information about **other commitments** that might affect your ability to work during the GSoC period. (exams, classes, holidays, other jobs, weddings, etc.) We can work around a lot of things, but it helps to know in advance.
7
+
8
+
Sample Application Template:
9
+
# Sub-org name: The thing I want to do this summer
10
+
11
+
**Note**: Make sure to include the sub-org name in the title both in Google's system and in your document.
12
+
13
+
## About me
14
+
1. Name (and nicknames like your github and irc usernames)
15
+
2. University / program / year / expected graduation date
16
+
3. Contact info (email, phone, etc.)
17
+
4. Time zone
18
+
5. Link to a resume (if you want)
19
+
20
+
## Code contribution
21
+
* Link to a pull request or code sample goes here.
22
+
* Ideally this should be code submitted to your chosen sub-org as a pull request or patch.
23
+
* It must represent your own work, although you can have help from developers to improve it.
24
+
* It must be publicly visible to your mentors and org admins.
25
+
* You can link more than one if you want.
26
+
27
+
## Project information
28
+
1. Sub-org name
29
+
2. Project Abstract
30
+
3. Detailed description
31
+
4. Weekly timeline
32
+
* The default schedule for GSoC is 12 weeks, either full-time or part-time. See [the GSoC timeline](https://developers.google.com/open-source/gsoc/timeline) for precise dates. This template assumes you'll be using those 12 weeks; if you're doing an alternate schedule you can adjust appropriately.
33
+
***Community Bonding**: List any prepwork you want to do before coding starts.
34
+
* For each coding week below, list planned code deliverables. Break the project into weeks and estimate what you will have complete at the end of each one. This schedule can be adjusted later if need be.
35
+
36
+
***Week 1** Note that usually even week 1's deliverables should include some code.
37
+
***Week 2**
38
+
***Week 3**
39
+
***Week 4**
40
+
***Week 5**
41
+
***Week 6** Midterm point. You need enough done at this point for your mentor to evaluate your progress and pass you. Usually you want to be a bit more than half done.
42
+
***Week 7**
43
+
***Week 8**
44
+
***Week 9**
45
+
***Week 10**
46
+
***Week 11** you may want to try to "code freeze" in week 11 and complete any tests/documentation in week 11-12.
47
+
***Week 12**
48
+
***Final week**: This week you will be submitting your projects
49
+
50
+
51
+
## Other commitments
52
+
* List of any things that might affect your ability to work this summer.
53
+
* List any exams, classes, holidays, other jobs, weddings, etc. We can work around a lot of things, but it helps to know in advance.
54
+
* If you're applying to more than one organization, you can let us know which one you prefer in case of a tie.
<p>Every week, we ask our contributors to answer three questions:</p>
68
+
<ol>
69
+
<li>What did you do this week?</li>
70
+
<li>What is coming up next?</li>
71
+
<li>Did you get stuck anywhere?</li>
72
+
</ol>
73
+
<p>These mini status reports help everyone keep track of how a project is going. It's particularly
74
+
important for the org admins to have these so they can oversee the whole program, but we also hope
75
+
that these public status reports will help the wider python community see the great work that comes
76
+
out of Google Summer of Code.</p>
77
+
<p>Contributors: To post your status report, log in to <a
78
+
href="https://social.python-gsoc.org/">https://social.python-gsoc.org/</a> and post it there. Please make your status report posts public, as Google may want to look at them. We expect at least one post that answers the three questions above every week that you're working. The post limit is 4004 characters but we expect most of your status reports will be much shorter than that! If you do not post consistently, we may assume that you have gone inactive and examine your other work to determine if you should be failed out of the program.</p>
<p>The fediverse is a collection of servers running a compatible protocol. We're running a fork of Mastodon, which allows you to do micro-blogging (similar to the service formerly known as Twitter or other text-based social media). We used to run a more traditional blog server for Google Summer of Code, but many pythonistas (including the <ahref="https://fosstodon.org/@ThePSF/">Python Software Foundation</a>, and <ahref="https://fosstodon.org/@fedidevs/112470206952068636">lots of folk at PyConUS 2024</a>) use the fediverse, and we felt using the fediverse might help our contributors feel more connected to the wider python community, and help the wider community find our contributors.
91
+
92
+
<p>Community folk: please feel free to follow our contributors and ask them questions about their projects!</p>
93
+
94
+
<p>A list of contributors will appear here after folk are set up.</p>
<p>Ben has <ahref="https://social.python-gsoc.org/@ben/112438320209195356">a thread on how to get
104
+
started in the Fediverse</a>.
105
+
106
+
<p>Feel free to follow other contributors, the server admins (see list below), folk on other servers, or hashtags. (You might enjoy <ahref="https://mastodon.social/tags/Python">#Python</a>, <ahref="https://mastodon.social/tags/OpenSource">#OpenSource</a>, and <ahref="https://mastodon.social/tags/GSoC">#GSoC</a> for example.) We encourage you to support other gsoc contributors and chat with them about their projects.</p>
107
+
108
+
<p>You can use your account for general chatting and stuff too, just remember to abide by the Python code of conduct, listed in the <ahref="https://social.python-gsoc.org/about">server rules</a>.</p>
0 commit comments