Editing User:Ivcore

== Introduction ==
Hello, I'm Ivan Gonzalez Polanco, a Mechanical Engineering middler student at Simón Bolívar University, in Caracas, Venezuela. I've got a passion for programming, science and philosophy, and I'm interested in CFD and FEA. Spanish is my native language but I'm proficient in english.

Participating in the GSoC I hope to:
* Learn more about the process of developing software while contributing to the community.
* Gain experience from and develop networks with people in the field.
* Get ''work'' experience I can add to my C.V. As this might (hopefully will) be my first time participating in a large project, as well as participating in the GSoC.

I've always been interested in computers, after various attempts in 2012 and 2013 to move (dual booting) from Windows to GNU/Linux, just recently (more mature and with more knowledge) went full-in and fell in love with the whole of it: the FOSSM, the UNIX philosophy, the sense of community and the passion for programming, for software. 

I chose Octave because in my sophomore year I saw Computational Mechanics I and II, and there we learned about Matlab and algorithms used in numerical analysis, being the last subject Differential Equations.

So now, with this opportunity to work in software development, to practice what I love, deepen the knowledge I was taught and help the community, all at the same time, I chose Octave.

== Contact ==
I'm not used to IRC yet but you can find me through '''ivcore''' there as well as in almost all social networks (say Github and Twitter)

My timezone is UTC -4:00 Caracas time, and on my free days I code from 6 p.m. to 3 a.m. or from 1 a.m. to 9 a.m. (UTC+0)

== Coding experience ==
* I have zero experience with OpenGL, Qt and C++. I did two terms of Matlab m-scripts plus some minor works for friends in the career and I'm currently getting to know Octave scripts.
* I've been working with Lua (LuaJIT) for over a year doing game development in my free time. Practiced a little of vanilla Javascript, and have done some scripts in Shell.
* I don't have any experience in a development team and in terms of open source and free projects I did a bug fix for a minor Atom Text Editor plugin.
* The biggest project I have written code for was the aforementioned Atom plugin ''love-launcher''[https://github.com/footballhead/love-launcher]. There, I saw two issues, the first being a request for a "save-all on launch" function, and the second, that launching the program even from the plugin with the console flag didn't work. Considering that both issues were simple enough, I read the Atom and npm documentation on child processes and after a few hours I was submitting a pull request with the feature and the fix. There I learned about spawning processes and that fixing bugs is more than simply writing code: you have to talk to the project manager, read documentation, and be patient.
* ''Gotta see what I can contribute to Octave as of now.''

== Experience with tools ==
* I'm not familiar yet with IRC and mailing lists.
* Haven't used Mercurial but I know the basics of git.
* I don't have experience with Mediawiki nor with other wiki software.
* Jesus Christ this amount of inexperience is humiliating.
* I still don't know, I think it would depend on the community and the relationships that develop during the GSoC.

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

== Prerequisites ==
* I'm currently using Solus release 2017.01.01.0
* On a daily average, I'll be able to access:
** Internet connection: 24 hours.
** A computer: 16 hours.
** A computer with internet connection: 16 hours.
* I have complete freedom to install any and every software.

== Self-assessment ==
* Please describe how useful criticism looks from your point of view as committing student.
* How autonomous are you when developing:
** 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?

== 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"). If possible, include two or three milestones you expect.''
[[Category: Summer of Code]]