This page is related to Summer of Code 2010

See the list of Summer of Code 2010 Ideas

This is a Summer of Code 2010 student page

Questionnaire

The questionnaire is not complete yet, I'll give more details later

1.1) Write a small introduction to yourself.

1.2) State your preferred email address:

nkurtov@gmail.com

1.3) If you have chosen a nick for IRC and Wesnoth forums, what is it?

orfest

1.4) Why do you want to participate in summer of code?

I'm getting more and more engaged into Open Source. Summer of code is a great opportunity for me to significantly contribute to Open Source and gain a lot of experience in programming and working with community.

1.5) What are you studying, subject, level and school?

I'm a Master student at Novosibirsk State University, Faculty of Information Technologies. My bachelor diploma is about hardcore optimization of a C++ library for shared-memory parallelism.

1.6) What country are you from, at what time are you most likely to be able to join IRC?

I'm living in Novosibirsk, Russia. My time zone is UTC+7. Every day I'm online for 4-8 hours, mainly at night.

1.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.

I'm going to have an exam session at the beginning of June. The exam session will consist of 2 exams. Also I have a part time job, I'm an intern software engineer at Intel corp.

2) Experience

2.1) What programs/software have you worked on before?

FlexyPool - a summer school on the first year of studying. There were four young and enthusiastic of us, who wanted to make a very original game. Personally I was responsible for the Physics Engine. The project was not released and only developers have its beta version somewhere.
Santa's Quest - a casual Christmas game developed by the same team as FlexyPool. I was responsible for level generation, balance, high scores etc. We even were firm to publish this game, but didn't succeed.
Eclipse DLTK - for half a year I worked at xored Inc. as QA, performing GUI testing, writing unit tests, etc. Submitted a lot of bugs and several patches.
TSP Flaming - a tiny academic project made for studying the method of Simulated Annealing. At that moment my interest to Open Source was growing and I wanted to try the process of managing a project at the SourceForge, that's why I made a full path to host it there.
Apache Harmony - a student project of bringing Edge Profiler to Jitrino.JET compiler. As a result I developed and submitted a patch. Results were published at the International Student Scientific Conference in Novosibirsk and were awarded 3rd degree diploma.
Intel(R) Concurrent Collections for C++ - an intern software engineer researching high-level performance optimizations.

2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)

2.3) Have you participated to the Google Summer of Code before? As a mentor or a student? In what project? Were you successful? If not, why?

2.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.

2.5) Gaming experience - Are you a gamer?

2.5.1) What type of gamer are you?

2.5.2) What type of games?

2.5.3) What type of opponents do you prefer?

2.5.4) Are you more interested in story or gameplay?

2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.

2.6) If you have contributed any patches to Wesnoth, please list them below. You can also list patches that have been submitted but not committed yet and patches that have not been specifically written for GSoC. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.

3) Communication skills

3.1) Though most of our developers are not native English speakers, English is the project's working language. Describe your fluency level in written English.

3.2) What spoken languages are you fluent in?

3.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.

3.4) Do you give constructive advice?

3.5) Do you receive advice well?

3.6) Are you good at sorting useful criticisms from useless ones?

3.7) How autonomous are you when developing ? Would you rather discuss intensively changes and not start coding until you know what you want to do or would you rather code a proof of concept to "see how it turn out", taking the risk of having it thrown away if it doesn't match what the project want.

4) Project

4.1) Did you select a project from our list? If that is the case, what project did you select? What do you want to especially concentrate on?

4.2) If you have invented your own project, please describe the project and the scope.

4.3) Why did you choose this project?

4.4) Include an estimated timeline for your work on the project. Don't forget to mention special things like "I booked holidays between A and B" and "I got an exam at ABC and won't be doing much then".

4.5) Include as much technical detail about your implementation as you can

4.6) What do you expect to gain from this project?

4.7) What would make you stay in the Wesnoth community after the conclusion of SOC?

5) Practical considerations

5.1) Are you familiar with any of the following tools or languages?

5.2) Which tools do you normally use for development? Why do you use them?

5.3) What programming languages are you fluent in?

5.5) Would you mind talking with your mentor on telephone / internet phone? We would like to have a backup way for communications for the case that somehow emails and IRC do fail. If you are willing to do so, please do list a phone number (including international code) so that we are able to contact you. You should probably only add this number in the application for you submit to google since the info in the wiki is available in public. We will not make any use of your number unless some case of "there is no way to contact you" does arise!

SummerofCode Orfest

Contents

Orfest - Rewriting network stack