Public application template
This part is answered in public on your 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
- Please describe yourself in three sentences, one of them regarding your current studies.
I´m software developer, bs in computer engineering and now a master in statistics.
- Which languages do you speak?
Spanish native, english
- What's your overall background? The general field you work in or are studying, e.g. computer science, physics, artificial intelligence, control theory...
All information technology topics and data analysis.
- Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
Experience in open source collaboration project.
- Please also describe your previous experience with the GSoC, if any. Includes any community-bonding, mentor experience or application, not necessarily accepted. We use this subquestion to identify which students are unfamiliar with how the program goes, providing further support. It has no negative impact on your rating!
- Why are you choosing Octave?
It´s a very important project with recognition.
- 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.
UTC/GMT +1 hour
- 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.
In C++ i used OpenCV to program this  only spanish, with octave and matlab i do works in my master, i know opengl and qt but not programmed with them.
- Please describe your experience with other programming languages.
Programming application with java, and systems scripts with python and bash, and playing with ruby.
- Please describe your experience with being in a development team. Do you have experience working with open source or free projects?
None in 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 :-)
Interesting thinhs to do, some related issues with my work.
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.
Linux or windows.
- 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
All day with 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.
- Please describe how useful criticism looks from your point of view as committing student.
It´s neccesary, i will adapt to your coding policies.
- 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?
Sometimes better thinks and later code, sometimes just code and test if it work.
- 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?
It´s life, but maybe in this case better discuss a little more before code.
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.
I select several of your task list :
- Incomplete sparse factorizations ichol, ilu
- Various sparse matrix improvements
- Implement a Qt widget for manipulating plots
- Improve JIT compiling, i think this is the most difficult
- Improve memory management (pre-allocation could be the most fast and realiable way)
- Finish the Agora website
- Improvements to n-dimensional image processing
- High Precision Arithmetic Computation
I think in rough estimate in three months are : - around 3 weeks to study code - 6 weeks coding, debugging - 3 testing
But maybe more iterative, agile development.
Maybe you could select one of this by priorities of octave's community. I think performance is now a drawback for Octave.