SummerOfCodeProposal jabagawee - Revision history

Esr: Hide historical references to Subversion from the wiki search function

2013-03-21T01:03:44Z

Hide historical references to Subversion from the wiki search function

Jabagawee: entered in my application

2010-03-14T07:13:38Z

entered in my application

Show changes

Jabagawee: Started the skeleton for this page.

2010-03-14T06:11:20Z

Started the skeleton for this page.

Jabagawee: Started the skeleton for this page.

2010-03-14T06:09:07Z

Started the skeleton for this page.

New page

1) Basics
1.1) Write a small introduction to yourself.
1.2) State your preferred email address.
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?
1.5) What are you studying, subject, level and school?
1.6) What country are you from, at what time are you most likely to be able to join IRC?
1.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.

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) 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.
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?
Subversion (used for all commits)
C++ (language used for all the normal source code)
STL, Boost, Sdl (C++ libraries used by Wesnoth)
Python (optional, mainly used for tools)
build environments (eg cmake/autotools/scons)
WML (the wesnoth specific scenario language)
Lua (used in combination with WML to create scenarios)
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!

@@ Line 29: / Line 29: @@
 I have not chosen any sort of major or future career path, and I am merely studying in general education. However, computer science and its related fields are under heavy consideration.
-'''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.'''
+'''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 S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.'''
 I have not yet done any of the above items.
@@ Line 41: / Line 41: @@
 '''2.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)'''
-A lot of my development and projects have been done in collaboration with a close friend of mine, so I have plenty of experience working in a team environment, albeit a small team. I am familiar with subversion and gobby as tools for collaboration.
+A lot of my development and projects have been done in collaboration with a close friend of mine, so I have plenty of experience working in a team environment, albeit a small team. I am familiar with sub&shy;&shy;version and gobby as tools for collaboration.
 '''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?'''
@@ Line 146: / Line 146: @@
 '''5.1) Are you familiar with any of the following tools or languages?'''
-I regularly use Subversion and Python, and I have some familiarity with C++. I am not familiar with build environments.
+I regularly use Sub&shy;&shy;version and Python, and I have some familiarity with C++. I am not familiar with build environments.
 '''5.2) Which tools do you normally use for development? Why do you use them?'''
-Because my projects never get large enough to warrant the use of an IDE, I usually use vim to edit files. My projects are managed entirely through the shell (mkdir, cd, etc). I use subversion to keep track of all of my files, and I use gobby to collaborate on a file with others in real time.
+Because my projects never get large enough to warrant the use of an IDE, I usually use vim to edit files. My projects are managed entirely through the shell (mkdir, cd, etc). I use sub&shy;&shy;version to keep track of all of my files, and I use gobby to collaborate on a file with others in real time.
 '''5.3) What programming languages are you fluent in?'''

@@ Line 1: / Line 1: @@
-) Basics
+) Basics<br />
-.1) Write a small introduction to yourself.
+.1) Write a small introduction to yourself.<br />
-.2) State your preferred email address.
+.2) State your preferred email address.<br />
-.3) If you have chosen a nick for IRC and Wesnoth forums, what is it?
+.3) If you have chosen a nick for IRC and Wesnoth forums, what is it?<br />
-.4) Why do you want to participate in summer of code?
+.4) Why do you want to participate in summer of code?<br />
-.5) What are you studying, subject, level and school?
+.5) What are you studying, subject, level and school?<br />
-.6) What country are you from, at what time are you most likely to be able to join IRC?
+.6) What country are you from, at what time are you most likely to be able to join IRC?<br />
-.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.
+.7) Do you have other commitments for the summer period ? Do you plan to take any vacations ? If yes, when.<br />
+<br />
-) Experience
+) Experience<br />
-.1) What programs/software have you worked on before?
+.1) What programs/software have you worked on before?<br />
-.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)
+.2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)<br />
-.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) 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?<br />
-.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
+.4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.<br />
-.5) Gaming experience - Are you a gamer?
+.5) Gaming experience - Are you a gamer?<br />
-.5.1) What type of gamer are you?
+.5.1) What type of gamer are you?<br />
-.5.2) What type of games?
+.5.2) What type of games?<br />
-.5.3) What type of opponents do you prefer?
+.5.3) What type of opponents do you prefer?<br />
-.5.4) Are you more interested in story or gameplay?
+.5.4) Are you more interested in story or gameplay?<br />
-.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.
+.5.5) Have you played Wesnoth? If so, tell us roughly for how long and whether you lean towards single player or multiplayer.<br />
-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.
+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.<br />
-.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.
+.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.<br />
+<br />
-) Communication skills
+) Communication skills<br />
-.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.
+.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.<br />
-.2) What spoken languages are you fluent in?
+.2) What spoken languages are you fluent in?<br />
+<br />
-.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
+.3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.<br />
-.4) Do you give constructive advice?
+.4) Do you give constructive advice?<br />
-.5) Do you receive advice well?
+.5) Do you receive advice well?<br />
-.6) Are you good at sorting useful criticisms from useless ones?
+.6) Are you good at sorting useful criticisms from useless ones?<br />
-.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
+.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<br />
+<br />
-) Project
+) Project<br />
-.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?
+.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?<br />
-.2) If you have invented your own project, please describe the project and the scope.
+.2) If you have invented your own project, please describe the project and the scope.<br />
-.3) Why did you choose this project?
+.3) Why did you choose this project?<br />
-.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) 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".<br />
-.5) Include as much technical detail about your implementation as you can
+.5) Include as much technical detail about your implementation as you can<br />
-.6) What do you expect to gain from this project?
+.6) What do you expect to gain from this project?<br />
-.7) What would make you stay in the Wesnoth community after the conclusion of SOC?
+.7) What would make you stay in the Wesnoth community after the conclusion of SOC?<br />
+<br />
-) Practical considerations
+) Practical considerations<br />
-.1) Are you familiar with any of the following tools or languages?
+.1) Are you familiar with any of the following tools or languages?<br />
-Subversion (used for all commits)
+Subversion (used for all commits)<br />
-C++ (language used for all the normal source code)
+C++ (language used for all the normal source code)<br />
-STL, Boost, Sdl (C++ libraries used by Wesnoth)
+STL, Boost, Sdl (C++ libraries used by Wesnoth)<br />
-Python (optional, mainly used for tools)
+Python (optional, mainly used for tools)<br />
-build environments (eg cmake/autotools/scons)
+build environments (eg cmake/autotools/scons)<br />
-WML (the wesnoth specific scenario language)
+WML (the wesnoth specific scenario language)<br />
-Lua (used in combination with WML to create scenarios)
+Lua (used in combination with WML to create scenarios)<br />
-.2) Which tools do you normally use for development? Why do you use them?
+.2) Which tools do you normally use for development? Why do you use them?<br />
-.3) What programming languages are you fluent in?
+.3) What programming languages are you fluent in?<br />
 .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!