User:Arpit17792

From Octave
Revision as of 06:38, 6 March 2014 by Arpit17792 (talk | contribs)
Jump to navigation Jump to search

A: An introduction

  • Please describe yourself in three sentences, one of them regarding your current studies.
I am a 3rd year Computer Science and Engineering student from IIIT Hyderabad, India. My interests are web development, programming and data structure  and solving brain teaser problems.
  • Which languages do you speak?
I speak Hindi and English.
  • What's your overall background?
I am a student of Computer Science and Engineering with a good knowledge of Mathematics.
  • Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
By participating in GSoC I want to make my first open source contribution and i will get to interact and learn with real cool people from across the world.
    • Please also describe your previous experience with the GSoC, if any.

This is the first time I'm applying to GSoC. Google has ranked our institution at 8th position in world and 1st in india on the basis of number of students accepted for the program 2005-13 so here there is good circle of developers and programmers.

  • Why are you choosing Octave?

Since octave is primarily intended for numerical computations and have extensive tools for solving them which is my area of interest and pre-requisite for project Generalized eigenvalue problem matches with my skill set and interest.

C: Contact

  • Please state the nick you use on IRC and any other communication channel related to Octave.

arpit17792

  • Which time zone do you live in? Will that change over GSoC duration?

My time zone is GMT +5:30 and will remain the same over GSoC duration.

  • Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?

I feel most comfortable working from UTC 1:00PM to UTC 8:00PM.

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.

I am familiar and worked on c++, Matlab m-scripts and OpenGL. I have worked on C++ for nearly 2.5 years, made a 3D game based on OpenGL and wrote good amount of Matlab m-scripts on signal processing also.

  • Please describe your experience with other programming languages.

Along with C++ I have also worked on C, Python, Java, PHP and a little bit RoR.

  • Please describe your experience with being in a development team. Do you have experience working with open source or free projects?

I have worked on many projects in team and there is a huge advantage of being in a development team, I gained knowledge from other person that how problem could be solved more efficiently, bug solving takes much less time, meet new people and most important less work load on an individual.

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