Editing Template:Student application template public

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
#REDIRECT [[Summer of Code - Getting Started]]
= Public application template =
This part is answered in public on your [[Special:MyPage|user page]]. Please copy its source ('''edit''') and then fill. Delete any examples and annotations (''this markup'') afterwards. Same for questions that do not apply to your situation.
 
== A: An introduction ==
 
Ambitious and someone who wants to achieve the maximum heights in career. When given a specific task, I can figure out the best ways to solve the problem with a creative approach. I am very determined and optimistic person and can produce results under any circumstances. I am currently a 3rd year undergraduate student at Indian Institute of Technology, Roorkee pursuing career in Geophysics. 
 
 
I speak Hindi and English.
 
 
I am currently studying geophysics and signal processing.
 
 
Google Summer of Code is the perfect platform to enhance your coding skills and contribute your work to the real world where you can actually make the difference. I hope to be a better and mature programmer by participating in this program.
 
 
This will be my first experience with the Google Summer of Codes.
 
 
I am choosing Octave as I am very much familiar with the concepts of C++ and the current field of my studying constantly requires use of Matlab, which is very much similar to Octave. I have gained a lot of experience working on Matlab and want to work and contribute for development of Octave.
 
== C: Contact ==
 
My nick on IRC channel is '''lm10''' .
 
I live in India Time Zone (UTC +05:30) and it will be same during GSoC.
 
I feel comfortable working during 08.00 to 18.00. But I can extend my timing till the work demands :). (UTC +05:30)
 
== E: Coding experience ==
This part is one of the more important ones in your application. You are allowed to be as verbose as you want, as long as you stay on topic ;-)
* Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.
* Please describe your experience with other programming languages.
* Please describe your experience with being in a development team. ''Do you have experience working with open source or free projects?''
* Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time.
* Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do.''
 
== F: Feeling fine ==
* Please describe (in short) your experience with the following tools: ''We only use this question to determine where you need guidance, not for rating!  We by no means expect you to be familiar with all of these and you'll won't necessarily need them while working with us.''
** IRC and mailing lists
** Mercurial or other source code management systems
** Mediawiki or other wiki software
** make, gcc, gdb or other development tools
* What will make you actively stay in our community after this GSoC is over? ''You can also tell us after applications close and we'll happily try to fulfill :-)''
 
== O: Only out of interest ==
* Did you ever hear about Octave before?
** If so, when and where? How far have you been involved already?
** If not, where would you expect or advise us to do advertising?
* What was the first question concerning Octave you could not find an answer to rather quickly? ''Of course more than one question can be stated. We try to improve based on this each year! Includes learning how to use it, code, website, GSoC application, …''
 
== P: Prerequisites ==
* Please state the operating system you work with.
** If you have access to more than one, please state them and the conditions under which you are granted this access.
* Please estimate an average time per day you will be able to ''(if separated)'' access
** an internet connection
** a computer
** a computer with your progressing work on
* Please describe the degree up to which you can install new software on computers you have access to.
 
== S: Self-assessment ==
* Please describe how useful criticism looks from your point of view as committing student.
* How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)''
** Do you like to discuss changes intensively and not start coding until you know what you want to do?
** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind?
 
== Y: Your task ==
* Did you select a task from our list of proposals and ideas?
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.''
** If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list?
* Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). Optionally include two or three milestones you expect.''
[[Category: Summer of Code]]
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)