User:Cardinot: Difference between revisions

From Octave
Jump to navigation Jump to search
No edit summary
No edit summary
Line 23: Line 23:


== 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.''
* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave.  
* 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.''
:My nickname is '''cardinot'''.
* 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 ;-)''
 
* Which time zone do you live in? Will that change over GSoC duration?  
:My time zone along the whole GSoC is UTC-3.
 
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?  
:'''I usually code around 12.00 to 22.00!'''


== E: Coding experience ==
== E: Coding experience ==

Revision as of 04:09, 29 April 2013

GSoC 2013 - Application

A: An introduction

  • Please describe yourself in three sentences, one of them regarding your current studies.
My name is Marcos Cardinot, I study Computer Engineering and Physics. I am fascinated by mathematics and computing, I love making new friends, work in groups and learn new things.
  • Which languages do you speak?
  1. English
  2. Portuguese
  3. Spanish
  • What's your overall background?
I am in the fourth year of Computer Engineering at the Rio de Janeiro State University and Physics at Federal Center Of Technological Education Of Rio De Janeiro, Brazil.
  • Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
The GSoC is important to place the student in a powerful community, providing support for a student to work fully for this community. Therefore, I want to participate in GSoC because I want to be part of this community and I want to use my experience to develop many things and also to learn from the high-level programmers that are present in this community. I hope to make new friends in the community and continue contributing after GSoC.
  • Please also describe your previous experience with the GSoC.
I participated in GSoC last year, my project aimed to develop new interactive tools for Scilab. I developed a new and complete graphics editor, plot browser and gave new possibilities as interactive, object selection, copy, delete and move.
  • Why are you choosing Octave?
Octave is extremely used at my university and I really would very much like use my experience to contribute new features!

C: Contact

  • Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave.
My nickname is cardinot.
  • Which time zone do you live in? Will that change over GSoC duration?
My time zone along the whole GSoC is UTC-3.
  • Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
I usually code around 12.00 to 22.00!

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, …

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.