Difference between revisions of "User:Hrvoje1212"
Hrvoje1212 (talk | contribs) |
Hrvoje1212 (talk | contribs) |
||
| Line 64: | Line 64: | ||
<h3>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 repository (during the evaluation period or earlier) please state so.</h3> | <h3>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 repository (during the evaluation period or earlier) please state so.</h3> | ||
<p>Not yet</p> | <p>Not yet</p> | ||
| + | |||
| + | <h2> <span class="mw-headline">3. Communication skills </span></h2> | ||
| + | |||
| + | <h3>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.</h3> | ||
| + | <p>Fluent english writting skills</p> | ||
| + | |||
| + | <h3>3.2) What spoken languages are you fluent in?</h3> | ||
| + | <p>English, Croatian</p> | ||
| + | |||
| + | <h3>3.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.</h3> | ||
| + | <p>I am allways ready to help other players</p> | ||
| + | |||
| + | <h3>3.4) Do you give constructive advice?</h3> | ||
| + | <p>I'm doing my best to get every person as close as possible to the solution he seeks for</p> | ||
| + | |||
| + | <h3>3.5) Do you receive advice well?</h3> | ||
| + | <p>I receive advices more than well becouse I'm allways looking forward to improove my skills and to see what other people think</p> | ||
| + | |||
| + | <h3>3.6) Are you good at sorting useful criticisms from useless ones?</h3> | ||
| + | <p>I can distinguish useless critiques easily</p> | ||
| + | |||
| + | <h3>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</h3> | ||
| + | <p>Before coding i like to discuss intensively changes, brainstorm other possible, mabye better, solution and ask many people for their opinion and feedback</p> | ||
Revision as of 23:45, 1 May 2013
Contents
- 1 Description
- 2 IRC
- 3 Questionnaire
- 3.1 1. Basics
- 3.1.1 1.1 Write a small introduction to yourself.
- 3.1.2 1.2 State your preferred email address.
- 3.1.3 1.3 If you have chosen a nick for IRC and Wesnoth forums, what is it?
- 3.1.4 1.4 Why do you want to participate in summer of code?
- 3.1.5 1.5 What are you studying, subject, level and school?
- 3.1.6 1.6 What country are you from, at what time are you most likely to be able to join IRC?
- 3.1.7 1.7 Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.
- 3.2 2. Experience
- 3.2.1 2.1) What programs/software have you worked on before?
- 3.2.2 2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)
- 3.2.3 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?
- 3.2.4 2.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
- 3.2.5 2.5) Gaming experience - Are you a gamer?
- 3.2.5.1 2.5.1) What type of gamer are you?
- 3.2.5.2 2.5.2) What type of games?
- 3.2.5.3 2.5.3) What type of opponents do you prefer?
- 3.2.5.4 2.5.4) Are you more interested in story or gameplay?
- 3.2.5.5 2.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.
- 3.2.6 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 repository (during the evaluation period or earlier) please state so.
- 3.3 3. Communication skills
- 3.3.1 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.3.2 3.2) What spoken languages are you fluent in?
- 3.3.3 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.3.4 3.4) Do you give constructive advice?
- 3.3.5 3.5) Do you receive advice well?
- 3.3.6 3.6) Are you good at sorting useful criticisms from useless ones?
- 3.3.7 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
- 3.1 1. Basics
Description
TODO: Copy this page and write "your name - proposal title" in this h4 section
TODO: Write a small (1-4 sentences) description of your proposal here.
TODO: Add more first-level sections to detail your proposal
IRC
Blesso
Questionnaire
1. Basics
1.1 Write a small introduction to yourself.
I'm 21 years old student from Zagreb, Croatia. With passion for coding and gaming I study Computer Science on University of Zagreb. I was active in competitive programming since high school and continously doing some interesting projects on the side. Big fan of Unix based operating systems, open source projects and lightweight tools. I'm a very quick learner and beside programming i love playing futsal, football, table tennis, and street workout.
1.2 State your preferred email address.
hrvoje1212 [at] gmail [dot] com
1.3 If you have chosen a nick for IRC and Wesnoth forums, what is it?
Blesso
1.4 Why do you want to participate in summer of code?
Summer of code is perfect opportunity for gaining invaluable experience in working on a big project, getting a better look inside all the problems and benefits that comes with it. Another reason is to meet other good people and learn as much as i can from their coding and thinking.
1.5 What are you studying, subject, level and school?
I'm studying computer science at Faculty of Electrical Engeneering and Computer Science in Zagreb. Currently I am on 2nd year.
1.6 What country are you from, at what time are you most likely to be able to join IRC?
I'm from Croatia, and able to join IRC in 10am-12pm GMT+1 period
1.7 Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.
I' don't have other commitments for this summer and i would take a 1 week vacation to go on the seaside.
2. Experience
2.1) What programs/software have you worked on before?
I've done some small individual projects, worked on a student project site with python/Django, made http server in Java, and few android applications
2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)
Yes I was in a team of 5 students competing in national application making contest developing android application. Then I was competing in code challenge with a team that had 2 more students.
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?
This is the first time for me to apply on gsoc.
2.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
No I am not.
2.5) Gaming experience - Are you a gamer?
2.5.1) What type of gamer are you?
In gaming I allways try to think one step ahead of the opponent and win with good strategy and tactics. I often try to think out of the box and predict another person moves.
2.5.2) What type of games?
I prefer PVP games where every person has equal chances of winning at the beginning and pure skill is what gets you to victory
2.5.3) What type of opponents do you prefer?
I love playing against better players becouse it makes me think better and when you achieve victory it is twice as good.
2.5.4) Are you more interested in story or gameplay?
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.
I started playing Wesnoth 2 years ago and played it every now and then when i get some free time. My prefered style is multiplayer although the campaigns are pretty much interesting
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 repository (during the evaluation period or earlier) please state so.
Not yet
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.
Fluent english writting skills
3.2) What spoken languages are you fluent in?
English, Croatian
3.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
I am allways ready to help other players
3.4) Do you give constructive advice?
I'm doing my best to get every person as close as possible to the solution he seeks for
3.5) Do you receive advice well?
I receive advices more than well becouse I'm allways looking forward to improove my skills and to see what other people think
3.6) Are you good at sorting useful criticisms from useless ones?
I can distinguish useless critiques easily
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
Before coding i like to discuss intensively changes, brainstorm other possible, mabye better, solution and ask many people for their opinion and feedback