13
edits
User:Opalfonso: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
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 ;-) | 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 C++, Octave or Matlab m-scripts, OpenGL and Qt. | ||
In C++ i used OpenCV to program [http://e-archivo.uc3m.es/bitstream/10016/10524/1/PFC_Oscar_Perez_Alfonso.pdf] | In C++ i used OpenCV to program this [http://e-archivo.uc3m.es/bitstream/10016/10524/1/PFC_Oscar_Perez_Alfonso.pdf] , 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. | * 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?'' | * 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 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.'' | * 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.'' | ||
None | |||
== F: Feeling fine == | == 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.'' | * 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 | ** IRC and mailing lists | ||
Ok | |||
** Mercurial or other source code management systems | ** Mercurial or other source code management systems | ||
Ok | |||
** Mediawiki or other wiki software | ** Mediawiki or other wiki software | ||
Ok | |||
** make, gcc, gdb or other development tools | ** make, gcc, gdb or other development tools | ||
Ok | |||
* 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 :-)'' | * 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 == | == O: Only out of interest == | ||
* Did you ever hear about Octave before? | * Did you ever hear about Octave before? | ||
Yes | |||
** If so, when and where? How far have you been involved already? | ** If so, when and where? How far have you been involved already? | ||
** If not, where would you expect or advise us to do advertising? | ** If not, where would you expect or advise us to do advertising? | ||
| Line 49: | Line 58: | ||
== P: Prerequisites == | == P: Prerequisites == | ||
* Please state the operating system you work with. | * 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. | ** 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 | * Please estimate an average time per day you will be able to ''(if separated)'' access | ||
| Line 54: | Line 64: | ||
** a computer | ** a computer | ||
** a computer with your progressing work on | ** a computer with your progressing work on | ||
1 a 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 the degree up to which you can install new software on computers you have access to. | ||
Dayly. | |||
== S: Self-assessment == | == S: Self-assessment == | ||
* Please describe how useful criticism looks from your point of view as committing student. | * 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. ;-)'' | * How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)'' | ||
Very autonomous. | |||
** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ** 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? | ** 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 == | == Y: Your task == | ||