A: An introduction
- Self description
- My name is P Sudeepam. I like to code and make music. - I am a second year student at Jaypee Institute of Information Technology, Noida, Uttar Pradesh, India. - I am pursuing a majors in Electronics and Communication Engineering. - I am comfortable with communicating in Hindi and English?
- Overall background?
- I have been coding since my 6th standard and as such, I have developed a working knowledge of how programming problems should be approached. - My areas of interest include Machine Learning, Digital Signal processing, and Algorithms. - I learn Machine Learning through online resources such as open research papers, blogs and MOOCs since my college does not offer a course on this subject till the final year. - Digital Signal Processing is one of the core subjects of my major. I have been learning that, and related subjects, such as 'Basics of Signals and Systems' for an year now. - Knowledge of Algorithms is something that I have learned through practice and repeated attempts to optimize code since the time I started coding. I will be taking a formal course on this subject in my next semester.
- Reasons for participating in GSoC
- The projects that I have been or will be doing as part of my major have a good part that they will be mentored and judged by a professor who will have a deep understanding of that subject to which the project is related. The bad part will be that the projects will restrict me to use the concepts that I have been taught. Similarly, in self undertaken projects, I have a flexibility to use whatever I want but then there will be no one to oversee the project. - My main reason to participate in the GSoC is directly related to this. A mentor will be available to oversee my project and as long as it is optimal, (which I ensure it will be), I will have an opportunity to approach a problem, the way 'I' would like to. The tools I'd be allowed to use (like the version control system) will probably be limited but that is a fair thing. - In addition to that I will have a great opportunity to contribute to the Open source community and learn how professional development work is carried out.
- Please also describe your previous experience with the GSoC, if any.
- This is my first time applying for GSoC.
- Why are you choosing Octave?
- When I took up the course on 'Basics of signals and systems' as a part of my college coursework about an year ago, I was required to use MATLAB for coding assignments. I never wanted to use MATLAB under a student's license as this would have landed me in a very uncomfortable situation when I no longer would have been a student. That was when, the open source enthusiast within me told me to go for GNU Octave. Since then, I have been using Octave as one of my primary languages, I use it for Signal processing and Machine Learning as do some of my peers. - GNU Octave is a software that has become an integrated part of my academic life. It would be an honour for me to be able to contribute to a software that is so important for me. As a GSoC student, I will be able to entirely dedicate my time in contributing to Octave. Hopefully I will end up making some noteworthy contributions. Then I would genuinely be able to brag to my peers who use Octave, that a small part of the software that they are using has been written by me.
- Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. We really want unique nicks. You might want to bold it.
- Which time zone do you live in? Will that change over GSoC duration? Perhaps DST adjustment or a relocation. Note that both UTC and GMT are not aware of daylight saving time! Please state UTC+x or -x.
- Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
- Example: I usually code around 9.00 to 18.00 and could also try to start earlier (~7.00) for few days ;-)
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, …
- Please state the operating system you work with.
- Please estimate an average time per day you will be able to access
- an internet connection
- a computer
- a computer with your progressing work on
- Please describe the degree to which you can install new software on computers you have access to.
- Please describe how useful criticism looks from your point of view as committing student.
- How autonomous are you when developing:
- 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.
- 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"). If possible, include two or three milestones you expect.