SoC2014 SDL2 stevedes

From The Battle for Wesnoth Wiki

This page is related to Summer of Code 2014
See the list of Summer of Code 2014 Ideas

This is a Summer of Code 2014 student page


INCOMPLETE! Work in progress!


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




1) Basics

1.1) Write a small introduction to yourself.

1.2) State your preferred email address.

stevedes [at] gmail [dot] com

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


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

For the experience of working on a real world project. An entry on my CV. College Credits.

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

Computer Science and Engineering, 3rd of 4 years. National Institute of Technology, Goa.

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

India. 4:30 to 13:30 UTC

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

No. But university starts on 21st July. Won't be available on 18th July as well. However, I can start project work as early as the 1st of March.

2) Experience

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

Nothing major. Made a number of small programs as school work. In my spare time, have also made some small video games.

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

Yes, as part of a school projects.

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?

Yes, not exactly a hardcore player, but I spend a lot of time playing games.

2.5.1) What type of gamer are you?

2.5.2) What type of games?

Games that force me to think, or the ones with great storylines. (HL2, Braid, Bioshock Infinite)

2.5.3) What type of opponents do you prefer?

2.5.4) Are you more interested in story or gameplay?

Both. But I think that even the best gameplay gets boring without a good story.

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

Yes. I first played the 1.6.4 release of wesnoth. I lean towards SP mostly due to connectivity problems.

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

Native English speaker.

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.

I can interact with most other players, except the really difficult ones.

3.4) Do you give constructive advice?

Yes, I try my best to do so.

3.5) Do you receive advice well?

Depends on the advice really, good, constructive advice is received well.

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

I believe so, to the best of my knowledge

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.

If I'm familiar with what I'm doing, then I usually use the former approach. On the other hand if I'm trying my hand at something "new", then I prefer to prototype.

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?

   Git (used for all commits) : Yes, familiar with basic git usage
   C++ (language used for all the normal source code) Yes: Proficient in C++
   STL, Boost, Sdl (C++ libraries used by Wesnoth) STL: Proficient, Boost: No, but willing to learn, SDL: Yes, experience with SDL1 and some SDL2
   Python (optional, mainly used for tools)Yes, proficient
   build environments (eg cmake/scons)No
   WML (the wesnoth specific scenario language)No
   Lua (used in combination with WML to create scenarios) No

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.4) 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!

This page was last edited on 1 March 2014, at 12:15.