Soc2012 vaulttech refactor the backend - Revision history

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

2013-03-21T03:18:07Z

Hide historical references to Subversion from the wiki search function

Vaulttech: corrected the bad "cronogram" word

2012-03-27T19:46:20Z

corrected the bad "cronogram" word

Vaulttech: /* Questionnaire */

2012-03-26T23:21:44Z

‎Questionnaire

Show changes

Vaulttech: /* Questionnaire */

2012-03-26T23:19:32Z

‎Questionnaire

Vaulttech: /* Questionnaire */

2012-03-26T23:01:53Z

‎Questionnaire

Vaulttech: /* Questionnaire */

2012-03-26T22:52:55Z

‎Questionnaire

Vaulttech: /* Questionnaire */

2012-03-26T22:48:26Z

‎Questionnaire

Vaulttech at 22:44, 26 March 2012

2012-03-26T22:44:24Z

Vaulttech: /* Questionnaire */

2012-03-26T21:39:25Z

‎Questionnaire

Crab: changed category

2012-03-26T21:39:22Z

changed category

@@ Line 92: / Line 92: @@
 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.
+* 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 S&shy;&shy;V&shy;&shy;N (during the evaluation period or earlier) please state so.
 I haven't.
@@ Line 164: / Line 164: @@
 * 5.1) Are you familiar with any of the following tools or languages?
-     Subversion (used for all commits)
+     Sub&shy;&shy;version (used for all commits)
      C++ (language used for all the normal source code)
      STL, Boost, Sdl (C++ libraries used by Wesnoth)
@@ Line 172: / Line 172: @@
      Lua (used in combination with WML to create scenarios)
-I'm familiar with these ones: Svn, C++, Stl, Python, Cmake (a little) and Lua (a little).
+I'm familiar with these ones: S&shy;&shy;v&shy;&shy;n, C++, Stl, Python, Cmake (a little) and Lua (a little).
 I have never touched the other ones (Boost, Sdl and WML).

@@ Line 10: / Line 10: @@
 * test, bugfix and document the changes - 2 month
-Initially, I can't give have a better cronogram.
+Initially, I can't give have a better calendar.
 =IRC=

@@ Line 140: / Line 140: @@
 .3) Why did you choose this project?
-I find myself very good in writing well-documented "beautiful" (elegant) code. I've also been working
+I find myself very good in writing well-documented "beautiful" (elegant) code -- though I'm not so good in creating code from scratch. Thus, I though I had the needed skills to this job.
 .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".
 .5) Include as much technical detail about your implementation as you can
 .6) What do you expect to gain from this project?
 .7) What would make you stay in the Wesnoth community after the conclusion of SOC?
 ) Practical considerations
@@ Line 162: / Line 171: @@
      WML (the wesnoth specific scenario language)
      Lua (used in combination with WML to create scenarios)
 .2) Which tools do you normally use for development? Why do you use them?
 .3) What programming languages are you fluent in?
 .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!
 In general, students should be as verbose as possible in their answers and feel free to elaborate.

@@ Line 131: / Line 131: @@
 .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?
 .2) If you have invented your own project, please describe the project and the scope.
 .3) Why did you choose this project?
 .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".

← Older revision		Revision as of 22:52, 26 March 2012
Line 124:		Line 124:
	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.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

		+	I'm moderated: I usually like to talk a little about the high-level stuff and then define strategies to follow. When these strategies are accomplished (or when I get into some define milestone), I talk again about what I could find interesting again.
		+
		+	If on one hand I can get really nervous on doing _no_ code, I can on the other hand get really confused when only doing code (and not talking about anything).

	4) Project		4) Project

@@ Line 99: / Line 99: @@
 .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.
 .2) What spoken languages are you fluent in?
 .3) Are you good at interacting with other players? Our developer community is friendly, but the player community can be a bit rough.
 .4) Do you give constructive advice?
 .5) Do you receive advice well?
 .6) Are you good at sorting useful criticisms from useless ones?
 .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

@@ Line 64: / Line 64: @@
 .4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
-The projects mentioned in question 2.1 are open-source, though they weren't big projects. Two of them were games
+The projects mentioned in question 2.1 are open-source, though they weren't big projects. Two of them were games (Musical Arena was a Guitar-Hero "Clone" and Sinos was a Pool game). The other one was the implementation of an algorithm proposed by my professor as his doctorate thesis, long ago. It was changed by a lot of people and I got the project as a mess. I couldn't change much of the code, but at least I made it compilable with a single "make", created a wikipedia article for it and put it in Googlecode.
 .5) Gaming experience - Are you a gamer?
 .5.1) What type of gamer are you?
 .5.2) What type of games?
 .5.3) What type of opponents do you prefer?
 .5.4) Are you more interested in story or gameplay?
 .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.
@@ Line 82: / Line 94: @@
 .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.
 ) Communication skills

@@ Line 51: / Line 51: @@
 .1) What programs/software have you worked on before?
-I've worked for some time in the [MClone|http://code.google.com/p/mclone/] project, related to what was long ago my professors doctorate.
+I've worked for some time in the MClone[http://code.google.com/p/mclone/] project, related to what was long ago my professors doctorate.
 .2) Have you developed software in a team environment before? (As opposed to hacking on something on your own)
 .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?
 .4) Are you already involved with any open source development projects? If yes, please describe the project and the scope of your involvement.
 .5) Gaming experience - Are you a gamer?

@@ Line 1: / Line 1: @@
 {{SoC2012Student}}
-[[Category:SoC_Ideas_Your_Own_Ideas2012]]
+[[Category:SoC Ideas Whiteboard Backend Refactoring 2012]]
 =Description=