Difference between revisions of "Template:Student application template public"

From Octave
Jump to navigation Jump to search
(Deprecate template.)
Tag: New redirect
 
(80 intermediate revisions by 14 users not shown)
Line 1: Line 1:
== A: An introduction ==
+
#REDIRECT [[Summer of Code - Getting Started]]
* Please describe yourself in three sentences, one of them regarding your current studies.
 
** Which languages do you speak?** What's your overall background?
 
''The general field you work in or are studying, e.g. computer science, physics, artificial intelligence, control theory...''
 
* Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
 
** Please also describe your previous experience with the GSoC, if any. ''Includes any community-bonding, mentor experience or application, not necessarily accepted. We use this subquestion to identify which students are unfamiliar with how the program goes, providing further support. It has no negative impact on your rating!''
 
* Why are you choosing Octave?
 
 
 
== 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.''
 
* Which time zone do you live in? Will that change over GSoC duration? ''UTC+2''
 
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
 
''I usually start at 9:00 and try not to spend more than 8 hours in front of the computer. I can also shift it into the eventing sometimes''
 
 
 
== 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.
 
I do a lot of scripting in Octave for my research and sometimes I have to port them to Matlab. I have quite good experience in C++. I know basics of Qt and have some minor experience in OpenGL.
 
* 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
 
I have not problem using them
 
** Mercurial or other source code management systems
 
I have some experience with SVN and GIT, I believe Hg is not much different
 
** Mediawiki or other wiki software
 
They do not seem to be difficult either.
 
** make, gcc, gdb or other development tools
 
I'm fine with them
 
* What will make you actively stay in our community after this GSoC is over?
 
 
 
 
 
== O: Only out of interest ==
 
* Did you ever hear about Octave before?
 
''Yes I did.''
 
** If so, when and where? How far have you been involved already?
 
''I am using Octave in daily basis for my research work and I actually prefer it over Matlab due to relaxed syntax, easy access to additional packages and lower price ;)''
 
** 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.
 
''I have one computer with Debian Linux (Now it's in a state between Wheezy and Jesse) and Windows 7 -- as an alternative boot configuration. I also have an access the OSX 10.10 on my other computer''
 
* Please estimate an average time per day you will be able to ''(if separated)'' access
 
** an internet connection
 
''16 hours -- I need to sleep sometimes''
 
** a computer
 
''8hours''
 
** a computer with your progressing work on
 
''8 hours''
 
* Please describe the degree up to which you can install new software on computers you have access to.
 
''I can install as long as I know what it does''
 
== 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.''
 
[[Category: Summer of Code]]
 

Latest revision as of 06:43, 21 January 2021