Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d4f7df4

Browse files
committed
Add markdown version of 2018 application template
1 parent 7ee2a98 commit d4f7df4

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

2018/application2018.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
Please get the latest version of this template from http://python-gsoc.org/
2+
3+
# Sub-org name
4+
e.g. Dipy, MNE-Python. Projects without a valid sub-org will be rejected.
5+
6+
# Student info
7+
* Name/Nicknames (e.g. on github, irc):
8+
* Email, telephone, alternate contact methods:
9+
* Time Zone:
10+
* GSoC Blog (you will be asked to blog about your project)
11+
* code sample: Link to a patch/code sample, preferably one you have
12+
* submitted to your sub-org. Must be publicly available. Applications without
13+
* a valid code sample will be rejected.
14+
15+
# Project info
16+
* Proposal Title: Include the name of your sub-org and explain in a few
17+
* words what you plan to do.
18+
* Proposal Abstract:
19+
* Proposal Detailed Description/Timeline:
20+
* Please include timeline with milestones, preferably weekly ones. All pre-work such as setup and reading documentation should take place during community bonding.
21+
22+
# other commitments
23+
* Do you have any other commitments during the main GSoC time period? For
24+
example: Exams, classes, jobs, holidays, weddings. Be up-front: we can work
25+
around minor scheduling issues, but if you lie about your availability and
26+
then fall behind on your work you will be failed.
27+
28+
* Have you applied with any other organizations? If so, do you have a preferred
29+
project/org? (This will help us in the event that more than one organization
30+
decides they wish to accept your proposal.)

0 commit comments

Comments
 (0)