From SMC Wiki
Revision as of 14:17, 28 March 2013 by Harisibrahimkv (talk | contribs)

GSoC 2013 Application Template

Things to do

  • Join the `SMC mailing list Introduce yourself over there so that the community can get to know you. Feel free to discuss your project ideas as well as to ask for any help that you may require as you start hacking our code base.
  • Prepare a detailed proposal regarding your project and submit it on the Google Summer of Code website ( Even though you could use our wiki ( to draft your project ideas, this is not mandatory. However, we can help you proofread your submission if you do use our wiki. See the section below for how to name and link to your application so we can easily find it.You may take a look at the old applications to see how they did things, links to pages containing old applications can be found on the wiki main page.

Writing your proposal

To be considered, a GSoC application must have a written proposal submitted to

If you want, you can start a wiki page to work on your proposal at Every applicant should create an account in SMC wiki. If you add your proposal there, we will help you edit it and provide feedback (though understand that we will not help you write it).You can add your application to our [[list of current applications|GSoC-2013-Current-Applications]].To maintain a consistent naming scheme, title your application: "GSoC 2013 Application <Your Name>: <Project Name>".

Note that your final application must be submitted at, so do not worry about the formatting of your application on the wiki, as you will have to reformat it there.You should not be too concerned with the formatting in Melange either, as we understand that the text editor there is not the best for making things look nice formatting-wise.We are more concerned with the content of your application, and that it is readable.

You may be able to get equivalent formatting in Melange from the wiki by copying the webpage contents or messing with the HTML source, but you shouldn't worry about it too much.

You should include the following information in your proposal:

Who are you?

Start your proposal with this information.

  • Your full name
  • Your university and current education
  • A short background story of who you are
  • Where can we find you? Kindly share your email, GitHub username, IRC handle, etc, so that we can know all these point to the same you.

What is your programming experience?

In your project proposal let us know about your programming experience. Many of our students start fresh. We will teach you what you need to know.

  • What platform do you use to code? What editor do you prefer and why?
  • How good can you use Malayalam and how good is your Malayalam reading and typing skills?
  • Tell us about something you have created.
  • What makes you excited about SMC? Have you worked before with SMC? If yes, when and on what?
  • Have you ever used git or another version control system?

What is your project?

Answer the following questions in your proposal:

  • What do you want to achieve?
  • What excites you about this project? Why did you choose it?
  • What qualifications do you have to implement your idea? For example, if you are developing an Android app,

then what is your prior programming experience in Android? Links to any apps that you have created already using Android. Why are you suited to work on this project?

  • What have other people done on this idea? Has it been implemented before?

(hint: it probably has) Are there any papers or blog posts about it?

  • How much time do you plan to invest in the project before, during, and after

the Summer of Code? (we expect full time 40h/week during GSoC, but better make this explicit) If you plan to take any vacations over the summer, let us know about it here.

  • Please provide a schedule of how this time will be spent on sub-tasks

of the project over the period of the summer. While this is only preliminary, we will use it to help monitor your progress throughout the program.Also understand that during the project you will issue weekly progress reports against that plan on your blog.

  • In planning your project, it is good to note where along the way you could

formulate a pull request. These would be points where you can have a self contained and well documented and tested piece of functionality. Doing this at several points during the summer helps to keep branch merges reasonable and code reviews manageable. A big code dump at the end of the summer will likely be hard to review and merge before the project deadline.

  • 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.

You do not need to format your application as a question/answer format for the above questions, but we expect to see all of the above questions answered in your application somewhere.

Other requirements

In addition to the written proposal, we require every GSoC applicant to do this:

  • Do create an account on the SMC wiki and start a wiki page for your proposal. Keep it updated.
  • We expect every GSoC participant to maintain a blog (If not, already) and post about their project's status, development, etc.
  • **In your application, please provide a brief summary of your contributions to

SMC (if any) so far.**