SummerOfCodeProposal cjhopman
Basics
- Write a small introduction to yourself.
- My name is Chris Hopman, I'm a student of computer science and mathematics. I'm graduating from the University of Wisconsin - Madison in May and will be attending the cs PhD program here in the fall.
- State your preferred email address.
- cjhopman@gmail.com
- State your preferred email address.
- If you have chosen a nick for IRC and Wesnoth forums, what is it?
- My nick is cjhopman pretty much everywhere.
- If you have chosen a nick for IRC and Wesnoth forums, what is it?
- Why do you want to participate in summer of code?
- Why do you want to participate in summer of code?
1.5) What are you studying, subject, level and school?
1.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 Wesnoth. If you have gained commit access to our SVN (during the evaluation period or earlier) please state so.
2) Experience
2.1) What programs/software have you worked on before?
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) Open Source
2.4.1) 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.
We do not plan to favor Wesnoth players as such, but some particular projects require a good feeling for the game which is hard to get without having played intensively.
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) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
3.3) Do you give constructive advice?
3.4) Do you receive advice well?
3.5) Are you good at sorting useful criticisms from useless ones?
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? Subversion (used for all commits) C++ (language used for all the normal source code) Python (optional, mainly used for tools) build environments (eg cmake/autotools/scons)
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) What spoken languages are you fluent in?
5.5) At what hours are you awake and when will you be able to be in IRC (please specify in UTC)
5.6) 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.