User:Yefllower

A: An introduction

• Please describe yourself in three sentences, one of them regarding your current studies.

I have participated in ACM for past two years with my teammates in Asian regional contest and won the first place in Changchun regional with team CamEo.

Math is amazing and beautiful, and I've learned basic college math well.

• • Which languages do you speak?

Chinese is my mother tongue, and English is my first foreign language. I had my GRE test last year and is confident with my reading skills.

• • What's your overall background?

I am a second-year college student from Shanghai Jiao Tong University, majoring in Computer Science.

• Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?

At first I was attracted by the experience and rewards to this Google project. When I scanning the suggested projects from other organizations, I found most of which are just coding a project or fix a few bugs. But this math and programming is really attractive to me. Combining code and math is my favorite part in acm contest. So here I am. This project would help me get familiar with the working ways of a real programmer of a community. And coding to make a software like octave better would be a pride to me, even the minor parts. If I have time and enjoyed myself during this project, I am willing to continue to contribute my effort to Octave afterwards.

• • Please also describe your previous experience with the GSoC, if any.

I am first time to this GSoC. I'll try to get familiar with the programs.

• Why are you choosing Octave?

Octave was used to do my Coursera homework of the course Machine Learning from Stanford. Matlab and Octave were suggested by Andrew Ng to complete the learning. MATLAB is really expensive but I really don't want to use pirated versions. And from almost all of the ideas pages I've only seen this one with something to do with my math learning besides coding.

C: Contact

• Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave.

My IRC nickname: yefllower

My e-mail address: yefllowers@gmail.com

Actually this name is almost always unique everywhere.

• Which time zone do you live in? Will that change over GSoC duration?

UTC+08:00

It will not change.

• Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?

I prefer to code in nights, (UTC+0)from 11:00 to 17:00. If no acm training or other meetings, I can start from afternoon like (UTC+0)7:00. (this happens three to four times a week)

E: Coding experience

• 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.

win8 on my laptop and a Ubuntu 12.04 LTS in Virtual machine.

• 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

All the time I have access to my laptop.

• Please describe the degree up to which you can install new software on computers you have access to.

I have the root or administrator account.

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.