Changes

Jump to navigation Jump to search
1,106 bytes added ,  22:20, 22 April 2013
no edit summary
Line 10: Line 10:  
== C: Contact ==
 
== C: Contact ==
 
* ''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.'' '''unaudio@gmail.com''' on Octave maintainer mailing list.
 
* ''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.'' '''unaudio@gmail.com''' on Octave maintainer mailing list.
* 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.''
+
* ''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.'' I live in UTC/GMT +2 hours time zone which won't change during the duration of GSoC 2013.
* 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 ;-)''
+
* ''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 ;-)'' I am most comfortable coding 8.00 to 17.00.
    
== E: Coding experience ==
 
== 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 ;-)
 
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.'' I have extensive C++ experience, especially from developing and maintaining Neil tracker. I have some Matlab and Octave experience, I am not familiar with OpenGL and QT programming.
* Please describe your experience with other programming languages.
+
* ''Please describe your experience with other programming languages.'' I know Python really well. I have experience interfacing lower level languages to high level languages (e.g. C++ to Python). I can develop non trivial applications in Common Lisp and Scheme as well as in C.
* 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?'' I have experience working on open source projects (https://sites.google.com/site/neilsequencer/). I have contributed code to JACAL symbolic algebra package and to pandas project.
* 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.'' Again this will have to be Neil Modular Tracker which is a software package for creating electronic music similar to Jeskola Buzz. I am the main developer and maintainer of that software.
* 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.'' I haven't commited code to Octave yet, however I started implementing my proposed GSoC project and C++ code that compiles to oct files can be found here https://bitbucket.org/bucket_brigade/octave-sound.
    
== F: Feeling fine ==
 
== F: Feeling fine ==

Navigation menu