You are here: 52°North>Wiki>Projects Web>GSoC>GSoCForStudents (15 Feb 2016, SimonJirka)Edit Attach

GSoC at 52°North For Students

Main Page: GSoC

Basics

"Flip bits, not burgers."

Important steps for students:

  • Read the GSoC FAQs and the student guide. Seriously, read it! If you do not read it then you will not know how to present yourself in a way that any project would accept you.
  • Subscribe to the GSoC mailing list for 52°North: http://list.52north.org/mailman/listinfo/gsoc.
  • Go to the GSoC2016ProjectIdeas and see if your find a project that interests you.
  • Follow the guidelines in DOs and DON'Ts of Google Summer of Code: Student Edition.
  • Solve the code challenge for your project. Important: Submitting the code challenge does not suffice as an application.
  • Use the application template below to create your application on Melange and submit it on time. Feel free to contact mentors directly if you are interested in a project, but writing to the GSoC mailing list ist strongly preferred because all students can profit from your questions.
  • Subscribe to the respective mailing list of the community your idea is related to, introduce yourself and present your idea during the community bonding period.
  • The 52°North licensing model requires you to sign a contributors license agreement to collect usage rights (you keep your copyright). This means no disadvantage to you at all! It just makes sure your contributions can become part of a long-term software development.
If you have any questions, please ask then on the GSoC mailing list at 52°North or contact Jan and Simon (j.schulte@52north.org and jirka@52north.org)

Preparing for an application

Apart from the guidelines linked above (read them!) you can show your capabilities in general, your interest in a particular project idea, and your qualifications as a software developer by doing the following:
  • Check your eligibility by carefully reading the programme's rules: https://developers.google.com/open-source/gsoc/rules
    • Important: Due to section *3.4 (a) (ii) b)* of the student agreement 52°North cannot accept students that are employed by one of 52°North's partner organisations. This includes contract work, internships, and immediate family members of employees of 52°North and its partner organisations.
  • Read this information about the Student Proposal Period: http://en.flossmanuals.net/melange/students-students-application-phase/
  • If you want to ask questions about projects and project ideas, please do so on the GSoC mailing list gsoc@52north.org so that all students can learn from the answers.
  • Read the respective community mailing list carefully to see what is currently ongoing (see link in previous section). Then introduce yourself on the community mailing list.
  • If the project extends an existing software, download and install the software, get acquainted. If it is a web service, try to make yours publically available. If not, send us screenshots of your local deployment, or why not a screencast on Youtube? Ask a very precise question to a potential mentor - good developers have and appreciate an eye for detail. See if there are open bugs you can fix or small features to implement - contact the code manager for details!
  • Share software that you already developed (yourself, or with clearly marked contributions if it is a larger project) with the mentors and org admins.
  • Send us a link to your GitHub user account.
These things are very important if you want to make a great impression.

Application Template

Please use the following template if you want to participate in GSoC with 52°North. If you need further information or have questions regarding the template please contact Jan and Simon (j.schulte@52north.org and jirka@52north.org).

We are looking forward to your application!

Please include the following contents in your application. There is no further template to give you the space for a creative and persuasive application, but you could check out the Wordpress GSoC 2011 application template for some hints. Please do not verbatim copy text from the ideas page, or from other people's discussions about your project, but rewrite it in your own words. If you include any significant text or code from another source in your application, it must be accompanied with a proper citation. All papers or references that you use or plan to use must also be cited. Put all this in a "References" section at the bottom of your application.

Personal Details
  • Name
  • Country
  • Contact details (email, personal website, Skype, IRC nick, phone number, location/time zone)
  • University/School name and degree
  • Short bio
  • Why are you interested in open source
Project
  • Description: Include a link to the description on the ideas page or make clear if this is your own suggestion. Also include potential mentors in the latter case.
  • Preliminary Schedule (milestones and deliverables, planned working hours, and potential other commitments)
    Note: The mentors rely on you to create a first schedule which will be revised during the project. The first schedule is there to demonstrate that you are able to create a reasonable first draft and can prioritize tasks.
  • If you want to impress the mentors: include a Scrum backlog and a sprint schedule.
  • Motivation (This might, but does not have to, include answers to questions such as: Why 52°North? Why this project? Why Open Source? Why are you suited to carry the project?)
  • Relation of project to ongoing studies (if applicable)
  • Report on code challenge
  • Do you understand this as a serious commitment equivalent to a full-time paid job?
  • Do you have any known time conflicts in the coding period?
Experience
  • (Open Source) software development experience (including example applications)
  • Programming level
  • Work experience
  • Academic experience and performance
  • References (software projects, advisors, teachers, colleauges, former mentors on Google Summer of Code)
    • Describe previous projects you worked on, including your own tasks if there were several committers!
ALERT! Important: You have to submit your project proposal on the Google Summer of Code website. It is not sufficient to send an email to the mentors or any of the 52°North mailing lists.

A good proposal...

Check the following items with your proposal before submitting it, and submit it if you can say "yes" to most questions.
  • checked-square Is my project description longer and more detailed than the one on the ideas page?
  • checked-square Did I complete the programming challenge and describe my findings and results in the proposal?
  • checked-square Do I use text formatting (links are hyperlinks, headlines bold) to make the text more readable?
  • checked-square Do I use the correct names (e.g. "52°North", not "52 North", "the 52", ...) and pay attention to details?
  • checked-square Do I include all the content suggested in the template, but still have my own style/partitioning to stand out?
  • checked-square Does the proposal contain enough details to show that I understood the task and have the required skills (or that I am aware where I do not have them yet)?

During the summer

Your end of the bargain
  • Follow our internal GSoCGuidelines.
  • Active communication with mentors and within the community (direct email contact with mentors, mailing lists, IRC).
  • Full time work on an interesting software development assignment.
  • Weekly status reports on Mondays before 18:00 CEST to the 52N GSoC mailing list.
  • Maintain a wiki page or blog to document your project.
  • Write three extensive (images, screencasts) blog articles (beginning, around mid-term evaluation/first prototype, after project is finished) for the 52°North Blog UPDATED
  • Follow our internal GSoCGuidelines (really!).
  • A lot of fun coding!
Our end of the bargain
  • Mentors and org admins communicate respectfully with you and focus on your learning experience.
  • Your mentors respond in a timely manner.
  • You are introduced to a open source commnity which also supports your project.
  • The org administrators give support for organisational issues and in case a mentor cannot perform his duties.
Topic revision: r17 - 15 Feb 2016 16:14:22, SimonJirka - This page was cached on 20 Jul 2016 - 12:26.

This site is powered by FoswikiCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback